Mark, 

The output of the v-9-VM is actually your console Proxy. S is your SSVM.
Just so you know. 

The eth0 is the link-local interface. You should have that regardless, and
like you said it won't affect your routing. You won't be able to use that
interface to connect to unless your management server is on the same VLAN
as the hypervisor, or you do it directly from the hypervisor directly.

The ssvm-check should be there as part of the template. Make sure that you
have the right systemVM template (4.0 not 3.0.2) out in your Secondary
Storage, and I would also destroy this CPVM and let it rebuild. It should
recreate on it's own, (do this with the SSVM as well) and make sure they
recreate with the necessary files.

Thanks,
Matt Mullins


On 12/19/12 2:59 PM, "Hooper, Mark E (Mark)"
<mark.hoo...@alcatel-lucent.com> wrote:

>Folks,
>Need your opinion on where to look to fix my problem.  I just did a fresh
>install of cloudstack 4.0.0, manager/nfs server on  system and 3 hosts
>all on Ubuntu 12.04.  I have the hosts all setup with 2 vlans and
>connected to public (vlan 20 - 192.168.20.x) and private (vlan
>10-192.168.10.x) bridges.    I have got it to the point where my SSVM and
>CPVM startup but thats where everything goes to hell.
>
>From the below output of "brctl show" you can see that one of the system
>vms has an additional nic (turns out to me the ssvm).  I have also added
>the ifconfig output below from the ssvm.
>
>root@compute-2:~# brctl show
>bridge name    bridge id        STP enabled    interfaces
>cloud0        8000.fe00a9fe0149    no
>                            vnet0
>                            vnet3
>cloudbr0        8000.00164153f812    no        eth0.10
>                            vnet1
>                            vnet4
>                            vnet6
>cloudbr1        8000.00164153f812    no        eth0.20
>                            vnet2
>                            vnet5
>virbr0        8000.000000000000    yes
>
>root@v-9-VM:/usr/local/cloud# ifconfig
>eth0      Link encap:Ethernet  HWaddr 0e:00:a9:fe:02:89
>          inet addr:169.254.2.137  Bcast:169.254.255.255  Mask:255.255.0.0
>          inet6 addr: fe80::c00:a9ff:fefe:289/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:283 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:151 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:27768 (27.1 KiB)  TX bytes:20809 (20.3 KiB)
>
>eth1      Link encap:Ethernet  HWaddr 06:61:8a:00:00:03
>          inet addr:192.168.10.52  Bcast:192.168.10.255
>Mask:255.255.255.0
>          inet6 addr: fe80::461:8aff:fe00:3/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:41 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:2740 (2.6 KiB)  TX bytes:1276 (1.2 KiB)
>
>eth2      Link encap:Ethernet  HWaddr 06:01:9e:00:00:2f
>          inet addr:192.168.20.120  Bcast:192.168.20.255
>Mask:255.255.255.0
>          inet6 addr: fe80::401:9eff:fe00:2f/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:44 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:3096 (3.0 KiB)  TX bytes:1438 (1.4 KiB)
>
>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:16436  Metric:1
>          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)
>
>root@v-9-VM:/usr/local/cloud#
>
>So I have tested that the extra nic doesn't affect routing or anything
>and in fact the ssvm can DNS resolve and ping on both private and public
>nics no problem.  Where things get really weird is when I try to find the
>check-ssvm.sh script to run it.  Well is it no where to be found !!!  I
>also check to see if the cloud service is running and obviously it isn't
>this is due to NOTHING being in /usr/local/cloud/
>
>root@compute-2:~# ssh -i
>/usr/lib/cloud/common/scripts/vm/systemvm/id_rsa.cloud -p 3922
>root@169.254.2.137
>Linux v-9-VM 2.6.32-5-686-bigmem #1 SMP Mon Jan 16 16:42:05 UTC 2012 i686
>
>The programs included with the Debian GNU/Linux system are free software;
>the exact distribution terms for each program are described in the
>individual files in /usr/share/doc/*/copyright.
>
>Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>permitted by applicable law.
>Last login: Wed Dec 19 22:47:30 2012 from 169.254.0.1
>Linux v-9-VM 2.6.32-5-686-bigmem #1 SMP Mon Jan 16 16:42:05 UTC 2012 i686
>
>The programs included with the Debian GNU/Linux system are free software;
>the exact distribution terms for each program are described in the
>individual files in /usr/share/doc/*/copyright.
>
>Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>permitted by applicable law.
>root@v-9-VM:~# cd /usr/local/cloud
>root@v-9-VM:/usr/local/cloud# ls -la
>total 8
>drwxr-sr-x  2 root staff 4096 Feb  6  2012 .
>drwxrwsr-x 11 root staff 4096 Feb  6  2012 ..
>root@v-9-VM:~# service cloud status
>cloud.com service is not running
>root@v-9-VM:~# service cloud restart
>Stopping cloud.com service (type=consoleproxy): Success
>
>/etc/init.d/cloud: line 106: /usr/local/cloud/systemvm/user_request: No
>such file or directory
>Starting cloud.com service (type=consoleproxy) Failed
>
>/etc/init.d/cloud: line 94: /usr/local/cloud/systemvm/user_request: No
>such file or directory
>root@v-9-VM:~#
>
>
>So at this point i believe my System VM template is garbage so I rerun
>"cloud-install-sys-tmplt -m /mnt/secondary -u
>http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz
>2 -h kvm -F" from the installation documents.  Nuke both CPVM and SSVM
>then rerun the exact same tests and again my system VMs are borked.
>Because I know someone is going to ask for it here is my agent.properties
>from compute-2 where the system vms seem to like being spawned on.
>
>root@compute-2:~# cat /etc/cloud/agent/agent.properties
>#Storage
>#Wed Dec 19 15:28:43 CST 2012
>guest.network.device=cloudbr1
>workers=5
>private.network.device=cloudbr0
>port=8250
>resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
>pod=1
>zone=1
>guid=778949c4-472f-3cec-b166-21324d686eae
>cluster=1
>public.network.device=cloudbr1
>local.storage.uuid=ecb48df9-9e54-404f-a26a-9a7ecb614328
>domr.scripts.dir=scripts/network/domr/kvm
>LibvirtComputingResource.id=4
>host=192.168.10.2
>
>
>
>Regards
>Mark Hooper
>
>
>

Reply via email to