VMs which existed before version upgrade cause problems
Build your own Cloud
Brought to you by:
bstebler,
jeanetteka
Menu
▾
▴
#127 VMs which existed before version upgrade cause problems
We just migrated from FC v1.0.2 to v1.0.4
Afterwards we have a strange effect with 2 static VMs, both existed prior to
the upgrade.
Currently it seems that only one of them can be running at a time on the secondary
VM-node, while the primary VM-node can run both simultaneously.
On the secondary VM-node, if one of the 2 VMs is already running, the
user will see an error like in the attached screenshot.
It seems that template-VMs are not affected, nor do they affect the problem
with the 2 static VMs.
Static VMs created after the upgrade seem to be not affected, nor do they
affect the problematic VMs.
But it seems that static VMs created from a profile which existed before are
also affected (the template was created after the upgrade).`
The 2 outputs below are from running `tail -f` on the 2 mentioned log-files in
the secondary VM-node.
tail -f libvirt/qemu/50a4c6cb-7e03-42cf-3f88-a9a68990726e.log
2012-11-15 16:33:54.578+0000: starting up
LC_ALL=C PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.4 HOME=/root USER=root QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -S -M pc-1.0 -cpu qemu32 -enable-kvm -m 1536 -smp 2,sockets=2,cores=1,threads=1 -name 50a4c6cb-7e03-42cf-3f88-a9a68990726e -uuid 50a4c6cb-7e03-42cf-3f88-a9a68990726e -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/50a4c6cb-7e03-42cf-3f88-a9a68990726e.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=0x5 -drive file=/var/virtualization/iso/50a4c3cc-0d6b-4095-8d70-b29f6b10cbae.iso,if=none,media=cdrom,id=drive-ide0-0-1,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive file=/var/virtualization/vm-persistent/0f83f084-8080-413e-b558-b678e504836e/50a4c6cb-024f-4365-be1a-a5982e18ea2d.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=17,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fa:2b:2a,bus=pci.0,addr=0x3 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5901,addr=0.0.0.0 -vga qxl -global qxl-vga.vram_size=67108864 -device AC97,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7
do_spice_init: starting 0.11.0
reds_init_socket: reds_init_socket: binding socket to 0.0.0.0:5901 failed
failed to initialize spice server2012-11-15 16:33:55.302+0000: shutting down
tail -f libvirt/libvirtd.log
2012-11-15 16:33:54.341+0000: 14325: info : virNetDevProbeVnetHdr:94 : Enabling IFF_VNET_HDR
2012-11-15 16:33:55.302+0000: 14325: error : qemuMonitorOpenUnix:266 : failed to connect to monitor socket: No such process
2012-11-15 16:33:55.302+0000: 14325: info : qemuConnectMonitor:1083 : Failed to connect monitor for 50a4c6cb-7e03-42cf-3f88-a9a68990726e
2012-11-15 16:33:55.302+0000: 14325: error : qemuProcessWaitForMonitor:1468 : internal error process exited while connecting to monitor: do_spice_init: starting 0.11.0
reds_init_socket: reds_init_socket: binding socket to 0.0.0.0:5901 failed
failed to initialize spice server
Correction:
----------------
The primary node can also run only one of the 2 VMs at a time.
I guess that the first VM already uses port 5901.
Can you please check this on the node after you started the first VM? Probably use 'netstat -tulpan'...
Process have to be designed