Re: SystemVm failling from possible libvirtd issue
The error you are seeing in you agent.log seems for me like an "old friend". Take a look into this: https://github.com/apache/cloudstack/issues/5491#issue-1003559121 You can check it quiet fast. Connect to one of the hosts and try to mount the nfs-share manually to an temp-folder. suggest to use the -v option of mount. if it fails you could try to pass the option manually. Should be all in the linked issue above Am Do., 7. Okt. 2021 um 22:33 Uhr schrieb Peter Stine < petrus.st...@gmail.com>: > It appears that it has the capability to use nfs4 (It's using Ceph > Octopus), but it is not clear whether it is using nfs3 or nfs4. I *think* > it is using nfs4 > > On 2021/10/07 16:14:36, "vas...@gmx.de" wrote: > > reading the agent.log you have trouble mounting the storage properly. > > Does your nfs-server for providing secondary storage provide nfs4 ? > > > > > > > > Am Do., 7. Okt. 2021 um 15:33 Uhr schrieb Peter Stine < > > petrus.st...@gmail.com>: > > > > > Hey everyone, > > > > > > I had to rework my network and reinstall cloudstack. While I am getting > > > the hosts to appear, they will not start any system VMs. They keep > failing > > > and iterating. It looks like there is an error in libvirtd (I am also > using > > > systemd for my networking), but I can't quite seem to figure out what > is > > > causing this issue. > > > I am using KVM as my hypervisor base and am running everything on > Ubuntu > > > 20.04. (The controller is in a VM if that makes a difference.) > > > > > > The main part that I have not seen in my error before is this: > 2021-10-07 > > > 08:59:37,558 WARN [kvm.resource.LibvirtConnection] > > > (agentRequest-Handler-4:null) (logid:e381c0f1) Can not find a > connection > > > for Instance s-1539-VM. Assuming the default connection. > > > 2021-10-07 08:59:37,727 WARN [kvm.resource.LibvirtKvmAgentHook] > > > (agentRequest-Handler-4:null) (logid:e381c0f1) Groovy script > > > '/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' is not > > > available. Transformations will not be applied. > > > 2021-10-07 08:59:37,727 WARN [kvm.resource.LibvirtKvmAgentHook] > > > (agentRequest-Handler-4:null) (logid:e381c0f1) Groovy scripting engine > is > > > not initialized. Data transformation skipped. > > > > > > > > > It also appears that libvirt is trying to connect to my primary storage > > > (which is Ceph), but cannot access the cloudstack key. I haven't seen > this > > > error before and cannot find a solution for it. Storage is showing up > in > > > the cloudstack management interface. > > > > > > Oct 07 09:31:25 gd-cs01-clst01-compute01 libvirtd[47830]: > > > 2021-10-07T09:31:25.780-0400 7f2836766700 -1 auth: unable to find a > keyring > > > on > > > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > > Oct 07 09:31:25 gd-cs01-clst01-compute01 libvirtd[47830]: > > > 2021-10-07T09:31:25.780-0400 7f2836766700 -1 auth: unable to find a > keyring > > > on > > > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > > Oct 07 09:31:31 gd-cs01-clst01-compute01 libvirtd[47830]: Failed to > > > connect socket to '/var/run/libvirt/virtlxcd-sock': No such file or > > > directory > > > Oct 07 09:31:31 gd-cs01-clst01-compute01 libvirtd[47830]: End of file > > > while reading data: Input/output error > > > Oct 07 09:31:33 gd-cs01-clst01-compute01 libvirtd[47830]: Failed to > > > connect socket to '/var/run/libvirt/virtlxcd-sock': No such file or > > > directory > > > Oct 07 09:31:33 gd-cs01-clst01-compute01 libvirtd[47830]: End of file > > > while reading data: Input/output error > > > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > > > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a > keyring > > > on > > > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > > > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a > keyring > > > on > > > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > > > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a > keyring > > > on > > > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > > > 2021-10-07T09:32:26.066-0400 7f280dffb700 -1 auth: unable to find a > keyring > > > on > > > > /etc/ceph/.client.cloudstack.keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/> > > > > > > > > > Here is the log from the agent; > > > https://gist.github.com/PeterS-gd/2d930b3317ea7b25ddf950e0e1cb167c > > > > > > Here is the log from the management server: > > > https://gist.github.com/PeterS-gd/75c0f507c96803a053df37caf3b25181 > > > > > >
Re: SystemVm failling from possible libvirtd issue
It appears that it has the capability to use nfs4 (It's using Ceph Octopus), but it is not clear whether it is using nfs3 or nfs4. I *think* it is using nfs4 On 2021/10/07 16:14:36, "vas...@gmx.de" wrote: > reading the agent.log you have trouble mounting the storage properly. > Does your nfs-server for providing secondary storage provide nfs4 ? > > > > Am Do., 7. Okt. 2021 um 15:33 Uhr schrieb Peter Stine < > petrus.st...@gmail.com>: > > > Hey everyone, > > > > I had to rework my network and reinstall cloudstack. While I am getting > > the hosts to appear, they will not start any system VMs. They keep failing > > and iterating. It looks like there is an error in libvirtd (I am also using > > systemd for my networking), but I can't quite seem to figure out what is > > causing this issue. > > I am using KVM as my hypervisor base and am running everything on Ubuntu > > 20.04. (The controller is in a VM if that makes a difference.) > > > > The main part that I have not seen in my error before is this: 2021-10-07 > > 08:59:37,558 WARN [kvm.resource.LibvirtConnection] > > (agentRequest-Handler-4:null) (logid:e381c0f1) Can not find a connection > > for Instance s-1539-VM. Assuming the default connection. > > 2021-10-07 08:59:37,727 WARN [kvm.resource.LibvirtKvmAgentHook] > > (agentRequest-Handler-4:null) (logid:e381c0f1) Groovy script > > '/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' is not > > available. Transformations will not be applied. > > 2021-10-07 08:59:37,727 WARN [kvm.resource.LibvirtKvmAgentHook] > > (agentRequest-Handler-4:null) (logid:e381c0f1) Groovy scripting engine is > > not initialized. Data transformation skipped. > > > > > > It also appears that libvirt is trying to connect to my primary storage > > (which is Ceph), but cannot access the cloudstack key. I haven't seen this > > error before and cannot find a solution for it. Storage is showing up in > > the cloudstack management interface. > > > > Oct 07 09:31:25 gd-cs01-clst01-compute01 libvirtd[47830]: > > 2021-10-07T09:31:25.780-0400 7f2836766700 -1 auth: unable to find a keyring > > on > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > Oct 07 09:31:25 gd-cs01-clst01-compute01 libvirtd[47830]: > > 2021-10-07T09:31:25.780-0400 7f2836766700 -1 auth: unable to find a keyring > > on > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > Oct 07 09:31:31 gd-cs01-clst01-compute01 libvirtd[47830]: Failed to > > connect socket to '/var/run/libvirt/virtlxcd-sock': No such file or > > directory > > Oct 07 09:31:31 gd-cs01-clst01-compute01 libvirtd[47830]: End of file > > while reading data: Input/output error > > Oct 07 09:31:33 gd-cs01-clst01-compute01 libvirtd[47830]: Failed to > > connect socket to '/var/run/libvirt/virtlxcd-sock': No such file or > > directory > > Oct 07 09:31:33 gd-cs01-clst01-compute01 libvirtd[47830]: End of file > > while reading data: Input/output error > > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring > > on > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring > > on > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring > > on > > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > > 2021-10-07T09:32:26.066-0400 7f280dffb700 -1 auth: unable to find a keyring > > on > > /etc/ceph/.client.cloudstack.keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/> > > > > > > Here is the log from the agent; > > https://gist.github.com/PeterS-gd/2d930b3317ea7b25ddf950e0e1cb167c > > > > Here is the log from the management server: > > https://gist.github.com/PeterS-gd/75c0f507c96803a053df37caf3b25181 > > >
Re: kvm ovs vm with trunk
On KVM, Cloudstack relies on the underlying Linux OS to do the base network configuration. Linux "port groups" are called "bonds" and virtual switches are called "bridges". In the Linux OS you set up the bond0 for all of the ports that will be part of the port group, with whatever parameters you wish to have for how the port balancing will work, and then the bond0.X / brX VLAN and bridge for the management network (where X is the vlan number of the management network). Then Cloudstack will handle the rest, creating additional VLANs and bridges on the base bond as needed. For directions on how to set up the bond0.X / brX pairs, consult your Linux distribution's documentation. (It is *radically* different between CentOS and Ubuntu, with CentOS using multiple configuration files under /etc/sysconfig/network-scripts and Ubuntu using /etc/netplan/* YAML files). Basically, a "bond" in Linux takes the place of an actual physical network port in all of the configuration for the networking. VLANs work the same with a "bond" in Linux as they work with actual physical network ports in Linux. As with an actual physical network port in Linux, the base bond is basically VLAN 0. All other VLANs must be configured on top of it as a sub-interface e.g. bond0.100 is VLAN 100 on the bond0 network interface. Hi, In vSphere it is possible to create port group with vlan range 1-4094, can we done the same on kvm with L2 network (on openvswitch or bridge)? Can we use in cloudstack vm with vlan trunk? Regards, Piotr
Re: SystemVm failling from possible libvirtd issue
reading the agent.log you have trouble mounting the storage properly. Does your nfs-server for providing secondary storage provide nfs4 ? Am Do., 7. Okt. 2021 um 15:33 Uhr schrieb Peter Stine < petrus.st...@gmail.com>: > Hey everyone, > > I had to rework my network and reinstall cloudstack. While I am getting > the hosts to appear, they will not start any system VMs. They keep failing > and iterating. It looks like there is an error in libvirtd (I am also using > systemd for my networking), but I can't quite seem to figure out what is > causing this issue. > I am using KVM as my hypervisor base and am running everything on Ubuntu > 20.04. (The controller is in a VM if that makes a difference.) > > The main part that I have not seen in my error before is this: 2021-10-07 > 08:59:37,558 WARN [kvm.resource.LibvirtConnection] > (agentRequest-Handler-4:null) (logid:e381c0f1) Can not find a connection > for Instance s-1539-VM. Assuming the default connection. > 2021-10-07 08:59:37,727 WARN [kvm.resource.LibvirtKvmAgentHook] > (agentRequest-Handler-4:null) (logid:e381c0f1) Groovy script > '/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' is not > available. Transformations will not be applied. > 2021-10-07 08:59:37,727 WARN [kvm.resource.LibvirtKvmAgentHook] > (agentRequest-Handler-4:null) (logid:e381c0f1) Groovy scripting engine is > not initialized. Data transformation skipped. > > > It also appears that libvirt is trying to connect to my primary storage > (which is Ceph), but cannot access the cloudstack key. I haven't seen this > error before and cannot find a solution for it. Storage is showing up in > the cloudstack management interface. > > Oct 07 09:31:25 gd-cs01-clst01-compute01 libvirtd[47830]: > 2021-10-07T09:31:25.780-0400 7f2836766700 -1 auth: unable to find a keyring > on > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > Oct 07 09:31:25 gd-cs01-clst01-compute01 libvirtd[47830]: > 2021-10-07T09:31:25.780-0400 7f2836766700 -1 auth: unable to find a keyring > on > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > Oct 07 09:31:31 gd-cs01-clst01-compute01 libvirtd[47830]: Failed to > connect socket to '/var/run/libvirt/virtlxcd-sock': No such file or > directory > Oct 07 09:31:31 gd-cs01-clst01-compute01 libvirtd[47830]: End of file > while reading data: Input/output error > Oct 07 09:31:33 gd-cs01-clst01-compute01 libvirtd[47830]: Failed to > connect socket to '/var/run/libvirt/virtlxcd-sock': No such file or > directory > Oct 07 09:31:33 gd-cs01-clst01-compute01 libvirtd[47830]: End of file > while reading data: Input/output error > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring > on > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring > on > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring > on > /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> > Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: > 2021-10-07T09:32:26.066-0400 7f280dffb700 -1 auth: unable to find a keyring > on > /etc/ceph/.client.cloudstack.keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/> > > > Here is the log from the agent; > https://gist.github.com/PeterS-gd/2d930b3317ea7b25ddf950e0e1cb167c > > Here is the log from the management server: > https://gist.github.com/PeterS-gd/75c0f507c96803a053df37caf3b25181 >
RE: Multiple Network labels - custom
Hi, Thank you for the provided information, I will test. Regards, Cristian -Original Message- From: vas...@gmx.de Sent: Thursday, October 7, 2021 6:37 PM To: users@cloudstack.apache.org Subject: Re: Multiple Network labels - custom it should work , as i am am using this for providing some "special" networks myself in my environment. maybe for a better understanding you can take a look at the following https://www.shapeblue.com/understanding-cloudstacks-physical-networking-architecture/ and there the section "advanced network traffic". there you'll find a diagramm of a scenario, where they provide an mpls network for guest traffic. what i had done to achieve this is (it works but i don't know if this is all best practice): WARNING: When introducing another physical network for e.g guest traffic, the "default" network offerings won't work anymore. CS has no default-allocation to an specified network - At least this is my experience. You will need to implement tags and create "custome" default network offerings for further usage! - create a new physical network in the zone - add traffic type "guest" - set the networklabel for matching purpose with the nics on the host - define tags for ALL physical networks (at least i needed to. if i am correct if you start tagging, you will have to implement it for all physical networks) - create 2 network offerings each using one of the tags of the physical networks - traffic type guest Then you can create networks, using the new network offerings, which will use the "tagged" physical network --> use the the matching nics on your hosts Am Do., 7. Okt. 2021 um 16:38 Uhr schrieb Cristian Ciobanu : > Hi, > >In a much simpler way. > >I have 2 networks, 1 shared and 1 isolated, the problem i have > here, both are using the same guest traffic label, because of this, > I'm not able to use these on different labels/nics, both are using the > same traffic type. Even if I add an additional physical network i will > have only one type of guest traffic... > >I would like to specify a custom traffic type ( guest x) and use > for specific network, shared or isolated. > > I'm not sure if I can replicate this by using tags, will this work? > > > Regards > Cristian > > On Thu, Oct 7, 2021, 15:22 vas...@gmx.de wrote: > >> just my thoughts. >> >> if i am understanding your intention correctly, you want to use a >> dedicated physical network on the hosts for "customized" guest >> traffic, correct? >> >> You will need to add a "new" physical network to the zone with the >> networklabel, assaign the traffic type "guest" and start to use tags >> for the physical networks. >> Afterwards you would need to implement a dedicated network service >> offering for this network - by using a tag to associate the network >> offering to the physical network. >> >> Your idea would currently not work cause the "physical network" in a >> zone is a 1:1 representation of the physical network on the hosts. >> afterwards you have some like a 1:m (one CS physical network - many >> various traffic types possible) but not n:1 (many physical networks : >> one traffic type - even "worse" you would have different "flavours" >> of one traffic type). >> >> Maybe another way to display the relation (physical Network on host - >> phyical network in a zone - traffic type): >> Currently used in CS: 1 - 1 - m >> >> Not supported in in CS: 1 - n - m >> >> what i understand you are looking for: 2 - 1 - 1 (while the traffic >> type guest would be segmentet into "default" and "custome") >> >> Hope that someone can imagine what i mean :-D >> >> >> >> >> Am Do., 7. Okt. 2021 um 08:37 Uhr schrieb : >> >> > Hello, >> > >> > >> > >> > Is there a way to use multiple network labels for the same >> > network type? >> > for example; I have Guest traffic with network label "vSwitch1, but >> > I >> also >> > want to have a vSwitch0 or anything else. If this is not possible, >> > is there a way to create custom networks traffic types using the >> > same type of network offering but create under a different network. >> > >> > label? >> > >> > >> > >> >I want to have 2 traffic types for Guest, (Guest And >> > GuestCustom) using the same network offering but create the under >> > the different network >> label. >> > The idea is to have the possibility to create/duplicate same type >> > of traffic but deploy under different network label (vSwitchX). >> > >> > >> > >> > >> > >> > >> > >> > Regards, >> > >> > Cristian >> > >> > >> >
Re: Multiple Network labels - custom
it should work , as i am am using this for providing some "special" networks myself in my environment. maybe for a better understanding you can take a look at the following https://www.shapeblue.com/understanding-cloudstacks-physical-networking-architecture/ and there the section "advanced network traffic". there you'll find a diagramm of a scenario, where they provide an mpls network for guest traffic. what i had done to achieve this is (it works but i don't know if this is all best practice): WARNING: When introducing another physical network for e.g guest traffic, the "default" network offerings won't work anymore. CS has no default-allocation to an specified network - At least this is my experience. You will need to implement tags and create "custome" default network offerings for further usage! - create a new physical network in the zone - add traffic type "guest" - set the networklabel for matching purpose with the nics on the host - define tags for ALL physical networks (at least i needed to. if i am correct if you start tagging, you will have to implement it for all physical networks) - create 2 network offerings each using one of the tags of the physical networks - traffic type guest Then you can create networks, using the new network offerings, which will use the "tagged" physical network --> use the the matching nics on your hosts Am Do., 7. Okt. 2021 um 16:38 Uhr schrieb Cristian Ciobanu : > Hi, > >In a much simpler way. > >I have 2 networks, 1 shared and 1 isolated, the problem i have here, > both are using the same guest traffic label, because of this, I'm not able > to use these on different labels/nics, both are using the same traffic > type. Even if I add an additional physical network i will have only one > type of guest traffic... > >I would like to specify a custom traffic type ( guest x) and use for > specific network, shared or isolated. > > I'm not sure if I can replicate this by using tags, will this work? > > > Regards > Cristian > > On Thu, Oct 7, 2021, 15:22 vas...@gmx.de wrote: > >> just my thoughts. >> >> if i am understanding your intention correctly, you want to use a >> dedicated >> physical network on the hosts for "customized" guest traffic, correct? >> >> You will need to add a "new" physical network to the zone with the >> networklabel, assaign the traffic type "guest" and start to use tags for >> the physical networks. >> Afterwards you would need to implement a dedicated network service >> offering >> for this network - by using a tag to associate the network offering to the >> physical network. >> >> Your idea would currently not work cause the "physical network" in a zone >> is a 1:1 representation of the physical network on the hosts. afterwards >> you have some like >> a 1:m (one CS physical network - many various traffic types possible) but >> not n:1 (many physical networks : one traffic type - even "worse" you >> would >> have different "flavours" of one traffic type). >> >> Maybe another way to display the relation (physical Network on host - >> phyical network in a zone - traffic type): >> Currently used in CS: 1 - 1 - m >> >> Not supported in in CS: 1 - n - m >> >> what i understand you are looking for: 2 - 1 - 1 (while the traffic type >> guest would be segmentet into "default" and "custome") >> >> Hope that someone can imagine what i mean :-D >> >> >> >> >> Am Do., 7. Okt. 2021 um 08:37 Uhr schrieb : >> >> > Hello, >> > >> > >> > >> > Is there a way to use multiple network labels for the same network >> > type? >> > for example; I have Guest traffic with network label "vSwitch1, but I >> also >> > want to have a vSwitch0 or anything else. If this is not possible, is >> > there >> > a way to create custom networks traffic types using the same type of >> > network >> > offering but create under a different network. >> > >> > label? >> > >> > >> > >> >I want to have 2 traffic types for Guest, (Guest And GuestCustom) >> > using >> > the same network offering but create the under the different network >> label. >> > The idea is to have the possibility to create/duplicate same type of >> > traffic >> > but deploy under different network label (vSwitchX). >> > >> > >> > >> > >> > >> > >> > >> > Regards, >> > >> > Cristian >> > >> > >> >
SystemVm failling from possible libvirtd issue
Hey everyone, I had to rework my network and reinstall cloudstack. While I am getting the hosts to appear, they will not start any system VMs. They keep failing and iterating. It looks like there is an error in libvirtd (I am also using systemd for my networking), but I can't quite seem to figure out what is causing this issue. I am using KVM as my hypervisor base and am running everything on Ubuntu 20.04. (The controller is in a VM if that makes a difference.) The main part that I have not seen in my error before is this: 2021-10-07 08:59:37,558 WARN [kvm.resource.LibvirtConnection] (agentRequest-Handler-4:null) (logid:e381c0f1) Can not find a connection for Instance s-1539-VM. Assuming the default connection. 2021-10-07 08:59:37,727 WARN [kvm.resource.LibvirtKvmAgentHook] (agentRequest-Handler-4:null) (logid:e381c0f1) Groovy script '/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' is not available. Transformations will not be applied. 2021-10-07 08:59:37,727 WARN [kvm.resource.LibvirtKvmAgentHook] (agentRequest-Handler-4:null) (logid:e381c0f1) Groovy scripting engine is not initialized. Data transformation skipped. It also appears that libvirt is trying to connect to my primary storage (which is Ceph), but cannot access the cloudstack key. I haven't seen this error before and cannot find a solution for it. Storage is showing up in the cloudstack management interface. Oct 07 09:31:25 gd-cs01-clst01-compute01 libvirtd[47830]: 2021-10-07T09:31:25.780-0400 7f2836766700 -1 auth: unable to find a keyring on /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> Oct 07 09:31:25 gd-cs01-clst01-compute01 libvirtd[47830]: 2021-10-07T09:31:25.780-0400 7f2836766700 -1 auth: unable to find a keyring on /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> Oct 07 09:31:31 gd-cs01-clst01-compute01 libvirtd[47830]: Failed to connect socket to '/var/run/libvirt/virtlxcd-sock': No such file or directory Oct 07 09:31:31 gd-cs01-clst01-compute01 libvirtd[47830]: End of file while reading data: Input/output error Oct 07 09:31:33 gd-cs01-clst01-compute01 libvirtd[47830]: Failed to connect socket to '/var/run/libvirt/virtlxcd-sock': No such file or directory Oct 07 09:31:33 gd-cs01-clst01-compute01 libvirtd[47830]: End of file while reading data: Input/output error Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring on /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring on /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: 2021-10-07T09:32:26.062-0400 7f2835764700 -1 auth: unable to find a keyring on /etc/ceph/..keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/etc/ceph/keyring.> Oct 07 09:32:26 gd-cs01-clst01-compute01 libvirtd[47830]: 2021-10-07T09:32:26.066-0400 7f280dffb700 -1 auth: unable to find a keyring on /etc/ceph/.client.cloudstack.keyring,/etc/ceph/.keyring,/etc/ceph/keyring,/> Here is the log from the agent; https://gist.github.com/PeterS-gd/2d930b3317ea7b25ddf950e0e1cb167c Here is the log from the management server: https://gist.github.com/PeterS-gd/75c0f507c96803a053df37caf3b25181
Re: Multiple Network labels - custom
Hi, In a much simpler way. I have 2 networks, 1 shared and 1 isolated, the problem i have here, both are using the same guest traffic label, because of this, I'm not able to use these on different labels/nics, both are using the same traffic type. Even if I add an additional physical network i will have only one type of guest traffic... I would like to specify a custom traffic type ( guest x) and use for specific network, shared or isolated. I'm not sure if I can replicate this by using tags, will this work? Regards Cristian On Thu, Oct 7, 2021, 15:22 vas...@gmx.de wrote: > just my thoughts. > > if i am understanding your intention correctly, you want to use a dedicated > physical network on the hosts for "customized" guest traffic, correct? > > You will need to add a "new" physical network to the zone with the > networklabel, assaign the traffic type "guest" and start to use tags for > the physical networks. > Afterwards you would need to implement a dedicated network service offering > for this network - by using a tag to associate the network offering to the > physical network. > > Your idea would currently not work cause the "physical network" in a zone > is a 1:1 representation of the physical network on the hosts. afterwards > you have some like > a 1:m (one CS physical network - many various traffic types possible) but > not n:1 (many physical networks : one traffic type - even "worse" you would > have different "flavours" of one traffic type). > > Maybe another way to display the relation (physical Network on host - > phyical network in a zone - traffic type): > Currently used in CS: 1 - 1 - m > > Not supported in in CS: 1 - n - m > > what i understand you are looking for: 2 - 1 - 1 (while the traffic type > guest would be segmentet into "default" and "custome") > > Hope that someone can imagine what i mean :-D > > > > > Am Do., 7. Okt. 2021 um 08:37 Uhr schrieb : > > > Hello, > > > > > > > > Is there a way to use multiple network labels for the same network > > type? > > for example; I have Guest traffic with network label "vSwitch1, but I > also > > want to have a vSwitch0 or anything else. If this is not possible, is > > there > > a way to create custom networks traffic types using the same type of > > network > > offering but create under a different network. > > > > label? > > > > > > > >I want to have 2 traffic types for Guest, (Guest And GuestCustom) > > using > > the same network offering but create the under the different network > label. > > The idea is to have the possibility to create/duplicate same type of > > traffic > > but deploy under different network label (vSwitchX). > > > > > > > > > > > > > > > > Regards, > > > > Cristian > > > > >
Re: Multiple Network labels - custom
just my thoughts. if i am understanding your intention correctly, you want to use a dedicated physical network on the hosts for "customized" guest traffic, correct? You will need to add a "new" physical network to the zone with the networklabel, assaign the traffic type "guest" and start to use tags for the physical networks. Afterwards you would need to implement a dedicated network service offering for this network - by using a tag to associate the network offering to the physical network. Your idea would currently not work cause the "physical network" in a zone is a 1:1 representation of the physical network on the hosts. afterwards you have some like a 1:m (one CS physical network - many various traffic types possible) but not n:1 (many physical networks : one traffic type - even "worse" you would have different "flavours" of one traffic type). Maybe another way to display the relation (physical Network on host - phyical network in a zone - traffic type): Currently used in CS: 1 - 1 - m Not supported in in CS: 1 - n - m what i understand you are looking for: 2 - 1 - 1 (while the traffic type guest would be segmentet into "default" and "custome") Hope that someone can imagine what i mean :-D Am Do., 7. Okt. 2021 um 08:37 Uhr schrieb : > Hello, > > > > Is there a way to use multiple network labels for the same network > type? > for example; I have Guest traffic with network label "vSwitch1, but I also > want to have a vSwitch0 or anything else. If this is not possible, is > there > a way to create custom networks traffic types using the same type of > network > offering but create under a different network. > > label? > > > >I want to have 2 traffic types for Guest, (Guest And GuestCustom) > using > the same network offering but create the under the different network label. > The idea is to have the possibility to create/duplicate same type of > traffic > but deploy under different network label (vSwitchX). > > > > > > > > Regards, > > Cristian > >
Re: kvm ovs vm with trunk
Hi Piotr, As far as I know, vlan trunk is supported only by OVS on kvm. Unfortunately, this feature is not supported in cloudstack. -Wei On Thu, 7 Oct 2021 at 09:21, Piotr Pisz wrote: > Hi, > > In vSphere it is possible to create port group with vlan range 1-4094, can > we done the same on kvm with L2 network (on openvswitch or bridge)? > Can we use in cloudstack vm with vlan trunk? > > Regards, > Piotr > > >
kvm ovs vm with trunk
Hi, In vSphere it is possible to create port group with vlan range 1-4094, can we done the same on kvm with L2 network (on openvswitch or bridge)? Can we use in cloudstack vm with vlan trunk? Regards, Piotr
