cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Garbus (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4826) System VMs fail to start
Date Tue, 08 Oct 2013 07:23:42 GMT


Dave Garbus commented on CLOUDSTACK-4826:

The SystemVMs are using systemvm.iso to boot, which is old. This is what came with the cloudstack-common
RPM for 4.2, which I fetched from the repository listed in the docs.

s-116-VM console:
root@systemvm:~# cat /etc/cloudstack-release
Cloudstack Release 3.0 Mon Feb  6 15:10:04 PST 2012

On the hypervisor:
# cat /var/log/libvirt/qemu/s-116-VM.log
2013-10-08 07:17:49.321+0000: starting up
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none
/usr/libexec/qemu-kvm -name s-116-VM -S -M rhel6.4.0 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1
-uuid bd83fb1b-16b9-4e50-918d-b6f04eb8beef -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/s-116-VM.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive file=/mnt/6f28c6b4-e5bb-3d6a-827e-173360dd1483/1401e82b-7da5-4824-a0c1-f72cb14bc135,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2
-drive file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none
-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:01:58,bus=pci.0,addr=0x3 -netdev
tap,fd=26,id=hostnet1,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=06:cd:da:00:00:35,bus=pci.0,addr=0x4
-netdev tap,fd=28,id=hostnet2,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet2,id=net2,mac=06:d2:be:00:00:38,bus=pci.0,addr=0x5
-netdev tap,fd=30,id=hostnet3,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet3,id=net3,mac=06:c4:26:00:00:0a,bus=pci.0,addr=0x6
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/s-116-VM.agent,server,nowait
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=s-116-VM.vport
-device usb-tablet,id=input0 -vnc,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9
Domain id=5 is tainted: high-privileges
char device redirected to /dev/pts/1

> System VMs fail to start
> ------------------------
>                 Key: CLOUDSTACK-4826
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.2.0
>         Environment: CentOS 6.4
> qemu-kvm-
> Cloudstack installed from RPM repo listed in docs
>            Reporter: Dave Garbus
>            Priority: Critical
> After upgrading from 4.1.1 to 4.2, system VMs did not restart properly when running cloudstack-sysvmadm.
Since we do not rely heavily on them at this point, I removed them figuring they would simply
be recreated (this has worked in the past).
> When CloudStack attempts to recreate the VMs, provisioning fails:
> agent.log (IPs are obscured):
> ========================
> Timed out: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/ -n
s-111-VM -p
.  Output is:
> I gained access to the VM using the root password, and this is what I found:
> root@systemvm:~# cat /etc/cloudstack-release
> Cloudstack Release 3.0 Mon Feb  6 15:10:04 PST 2012
> root@systemvm:~# uname -a
> Linux systemvm 2.6.32-5-686-bigmem #1 SMP Mon Jan 16 16:42:05 UTC 2012 i686 GNU/Linux
> root@systemvm:~# /etc/init.d/cloud-
> cloud-early-config  cloud-passwd-srvr
> root@systemvm:~# /etc/init.d/cloud-early-config start
> Executing cloud-early-config...Executing cloud-early-config...Detected that we are running
inside kvm guest.../dev/vport0p1 not loaded, perhaps guest kernel is too old....root@systemvm:~#
> I have the system vm template systemvmtemplate-2013-06-12-master-kvm.qcow2.bz2, which
is the latest (to my knowledge), on my secondary storage NFS mount, however, the SSVM is not
able to be started, so I'm not sure this helps.
> Please let me know if more information is needed.

This message was sent by Atlassian JIRA

View raw message