Can you post the agent log output (in debug) after this change?
________________________________ From: ned dogg <neddog...@gmail.com> Sent: Wednesday, September 14, 2016 11:43 AM To: dev@cloudstack.apache.org Subject: Re: System VM's are getting stuck in starting mode Thanks for explanation Simon. I plugged an interface eth0 into your cloudbr0 but no luck. brctl show bridge name bridge id STP enabled interfaces cloud0 8000.000000000000 no cloudbr0 8000.40a8f06672e2 no eth0 cloudbr1 8000.000000000000 no lxcbr0 8000.000000000000 no virbr0 8000.000000000000 yes Any clue? On Wed, Sep 14, 2016 at 4:12 PM, Simon Weller <swel...@ena.com> wrote: > The CloudStack agent walks all the bridges and then tries to find the > underlying interface being used. If it can't identify the interface, then > it fails to start. > > The issue you seem to have is that you have bridges setup without any > actual physical interfaces attached to them. So your bridges have no > network connectivity. > > > When you add a host from the CloudStack Management GUI, it will try and do > this work for you. Since you already have some bridges setup and you don't > have the ip on eth0, the setup script probably didn't touch any of your > config. > > > Take a look at the agent setup instructions here for how to do this > manually: > > > http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.6/ > hypervisor/kvm.html > > > Search for "Configure in Ubuntu". > > > In this example, they are using vlan sub-interfaces to provide > connectivity to two difference bridges, from a single physical interface. > You could just use regular interfaces if you have them available (e.g. eth0 > and eth1). You could also just use a single bridge (cloudbr0) and then plug > both the guest and public networks into that. That would require vlans > though, on at least one of the networks (you could use native for > management). > > > You could also wipe the host and install Ubuntu (or Centos) so you have a > vanilla OS and try the setup again. I'm not very experienced with Ubuntu, > as we use Centos, so there may be some nuance you have to take into > consideration. I'll let others chime in on that. > > > Does that make sense? > > > - Si > > > ________________________________ > From: ned dogg <neddog...@gmail.com> > Sent: Wednesday, September 14, 2016 9:54 AM > To: dev@cloudstack.apache.org > Subject: Re: System VM's are getting stuck in starting mode > > Sorry, Simon I don't understand. Please can you be more explicite. > > On Wed, Sep 14, 2016 at 3:46 PM, Simon Weller <swel...@ena.com> wrote: > > > So it doesn't appear you have any interfaces plugged into your cloudbr0 > or > > cloudbr1 bridges. Please note that the agent expects to find particular > > interface name formats: eth*, bond*, team*, vlan*, em*, p*p*, ens*, eno*, > > enp*, or enx*. Try adding your actual interface to the bridge. > > > > > > ________________________________ > > From: ned dogg <neddog...@gmail.com> > > Sent: Wednesday, September 14, 2016 9:38 AM > > To: dev@cloudstack.apache.org > > Subject: Re: System VM's are getting stuck in starting mode > > > > *brctl* *show* > > bridge name bridge id STP enabled interfaces > > cloud0 8000.000000000000 no > > cloudbr0 8000.000000000000 no > > cloudbr1 8000.000000000000 no > > lxcbr0 8000.000000000000 no > > virbr0 8000.000000000000 yes > > > > *ifconfig* > > cloud0 Link encap:Ethernet HWaddr 1e:ad:ae:e9:ac:36 > > inet addr:169.254.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 > > inet6 addr: fe80::1cad:aeff:fee9:ac36/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:153 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 B) TX bytes:24346 (24.3 KB) > > > > cloudbr0 Link encap:Ethernet HWaddr 4a:ee:2d:0e:74:a4 > > inet6 addr: fe80::48ee:2dff:fe0e:74a4/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 B) TX bytes:5708 (5.7 KB) > > > > cloudbr1 Link encap:Ethernet HWaddr 2e:dd:5d:be:b7:d8 > > inet6 addr: fe80::2cdd:5dff:febe:b7d8/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 B) TX bytes:5480 (5.4 KB) > > > > eth0 Link encap:Ethernet HWaddr 40:a8:f0:66:72:e2 > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > Interrupt:20 Memory:f7d00000-f7d20000 > > > > eth0:avahi Link encap:Ethernet HWaddr 40:a8:f0:66:72:e2 > > inet addr:169.254.10.237 Bcast:169.254.255.255 > Mask:255.255.0.0 > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > Interrupt:20 Memory:f7d00000-f7d20000 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:65536 Metric:1 > > RX packets:14165 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:14165 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:8078857 (8.0 MB) TX bytes:8078857 (8.0 MB) > > > > lxcbr0 Link encap:Ethernet HWaddr 72:8b:a5:4b:66:28 > > inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0 > > inet6 addr: fe80::708b:a5ff:fe4b:6628/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:112 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 B) TX bytes:18691 (18.6 KB) > > > > virbr0 Link encap:Ethernet HWaddr ea:d0:ee:b5:ff:05 > > inet addr:192.168.122.1 Bcast:192.168.122.255 > > Mask:255.255.255.0 > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > wlan0 Link encap:Ethernet HWaddr d8:eb:97:e9:af:2f > > inet addr:192.168.100.12 Bcast:192.168.100.255 > > Mask:255.255.255.0 > > inet6 addr: fe80::daeb:97ff:fee9:af2f/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:14277 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:15749 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:6382785 (6.3 MB) TX bytes:8834906 (8.8 MB) > > > > > > > > On Wed, Sep 14, 2016 at 3:27 PM, Simon Weller <swel...@ena.com> wrote: > > > > > Can you post ifconfig and brctl show? > > > > > > > > > > > > > > > ________________________________ > > > From: ned dogg <neddog...@gmail.com> > > > Sent: Wednesday, September 14, 2016 4:54 AM > > > To: dev@cloudstack.apache.org > > > Subject: Re: System VM's are getting stuck in starting mode > > > > > > Thanks for the reply Simon. > > > > > > > > > *vi /etc/network/interfaces* > > > # This file describes the network interfaces available on your system > > > # and how to activate them. For more information, see interfaces(5). > > > > > > # The loopback network interface > > > auto lo > > > iface lo inet loopback > > > > > > # Public network > > > auto cloudbr0 > > > iface cloudbr0 inet manual > > > bridge_ports none > > > bridge_fd 5 > > > bridge_stp off > > > bridge_maxwait 1 > > > > > > # Private network > > > auto cloudbr1 > > > iface cloudbr1 inet manual > > > bridge_ports none > > > bridge_fd 5 > > > bridge_stp off > > > bridge_maxwait 1 > > > > > > # Source interfaces > > > # Please check /etc/network/interfaces.d before changing this file > > > # as interfaces may have been defined in /etc/network/interfaces.d > > > # NOTE: the primary ethernet device is defined in > > > # /etc/network/interfaces.d/eth0 > > > # See LP: #1262951 > > > source /etc/network/interfaces.d/*.cfg > > > > > > *vi /etc/network/interfaces.d/eth0.cfg* > > > # The primary network interface > > > auto eth0 > > > iface eth0 inet dhcp > > > > > > On Tue, Sep 13, 2016 at 8:08 PM, Simon Weller <swel...@ena.com> wrote: > > > > > > > This looks interesting to me: > > > > > > > > 1. > > > > looking for pif for bridge virbr0 > > > > 2. > > > > 2016-09-13 19:22:09,833 DEBUG [kvm.resource. > LibvirtComputingResource] > > > > (main:null) failing to get physical interface from bridge virbr0, did > > not > > > > find an eth*, bond*, team*, vlan*, em*, p*p*, ens*, eno*, enp*, or > enx* > > > in > > > > /sys/devices/virtual/net/virbr0/brif > > > > 3. > > > > 2016-09-13 19:22:09,833 DEBUG [kvm.resource. > LibvirtComputingResource] > > > > (main:null) looking for pif for bridge lxcbr0 > > > > 4. > > > > 2016-09-13 19:22:09,833 DEBUG [kvm.resource. > LibvirtComputingResource] > > > > (main:null) failing to get physical interface from bridge > > > > > > > > > > > > Can you post your interfaces and bridges please? > > > > > > > > > > > > - Si > > > > > > > > > > > > ________________________________ > > > > From: ned dogg <neddog...@gmail.com> > > > > Sent: Tuesday, September 13, 2016 1:27 PM > > > > To: dev@cloudstack.apache.org > > > > Subject: Re: System VM's are getting stuck in starting mode > > > > > > > > Hi Simon, > > > > > > > > Thanks for the reply. I changed the logging level to dedug as per > your > > > > recommendation. Please find enclosed the link of my > > cloudstack-management > > > > and cloudstack-agent respectively: > > > > http://pastebin.com/gG1LRm0X > > [http://pastebin.com/i/facebook.png]<http://pastebin.com/gG1LRm0X> > > > > cloudstack-management logs - Pastebin.com<http://pastebin.com/gG1LRm0X> > > pastebin.com > > > > > > > > > > http://pastebin.com/zJ7CHhLD > > > > > > > > On Mon, Sep 12, 2016 at 2:22 PM, Tutkowski, Mike < > > > > mike.tutkow...@netapp.com> > > > > wrote: > > > > > > > > > Thanks > > > > > > > > > > Yeah, I wasn't sure if you just experienced it on reboot or if > > > sometimes > > > > > when setting up your cloud you encountered this issue, as well > (like > > > > 9144). > > > > > ________________________________________ > > > > > From: ned dogg <neddog...@gmail.com> > > > > > Sent: Monday, September 12, 2016 6:08 AM > > > > > To: dev@cloudstack.apache.org > > > > > Subject: Re: System VM's are getting stuck in starting mode > > > > > > > > > > Hi Mike and thank you for the reply. Sorry but this issue is not > > > similar > > > > > to mine, I already gave you the one which looks similar : > > > > > https://issues.apache.org/jira/browse/CLOUDSTACK-7936 > > > > > > > > > > On Sun, Sep 11, 2016 at 5:28 AM, Tutkowski, Mike < > > > > > mike.tutkow...@netapp.com> > > > > > wrote: > > > > > > > > > > > Is your issue similar to this one? > > > > > > > > > > > > https://issues.apache.org/jira/browse/CLOUDSTACK-9144 > > > > > > ________________________________________ > > > > > > From: ned dogg <neddog...@gmail.com> > > > > > > Sent: Saturday, September 10, 2016 1:24 PM > > > > > > To: dev@cloudstack.apache.org > > > > > > Subject: System VM's are getting stuck in starting mode > > > > > > > > > > > > Hi Everybody, > > > > > > > > > > > > I'm a newbie on cloudstack. I started playing with this > technology. > > > For > > > > > > that I install both the management -server and the agent. I was > > able > > > to > > > > > > install and start them properly but I unable to create any > > instance. > > > > > When I > > > > > > click on instance the menu then I click on add instance and > next, > > I > > > > have > > > > > > no templates that is presented to me. Thus I stuck at this > level. I > > > > don't > > > > > > know what to do. > > > > > > > > > > > > I think that this issue is because my System VM get stuck an the > > > > starting > > > > > > mode. After some googling, I discovered that this is a know issue > > > > > > https://issues.apache.org/jira/browse/CLOUDSTACK-7936. But this > > > issue > > > > is > > > > > > for cloudstack 4.4.1 but I'm using cloudstack 4.6. I was asking > > > myself > > > > if > > > > > > this issue is also common on cloudstack 4.6? > > > > > > > > > > > > Please any help will be welcoming. > > > > > > Thanks. > > > > > > > > > > > > > > > > > > > > >
