Hello, After migrating the VM the CPU consumed by VM is showing as 99. ID USER NAME STAT CPU MEM HOSTNAME TIME 155 oneadmin koushik_ runn 99 600M 192.168.2.5 00 00:53:38 156 oneadmin koushik_ runn 1 600M 192.168.2.4 00 00:30:26
When I tried to access the migrated VM ( on host 192.168.2.5) using Virt-Viewer I got a screen with message Connected to VNC Server and it remained in the same state( similar to hanged state). vncviewer too didnt work.. Here is the qemu log info for migrated VM LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 600 -smp 1,sockets=1,cores=1,threads=1 -name one-155 -uuid fcdee899-98c5-7e42-69d0-2084d8556791 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/one-155.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot c -device lsi,id=scsi0,bus=pci.0,addr=0x4 -drive file=/srv/cloud/one/var//155/images/disk.0,if=none,id=drive-scsi0-0-0,boot=on,format=qcow2 -device scsi-disk,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0 -device rtl8139,vlan=0,id=net0,mac=02:00:c0:a8:02:08,bus=pci.0,addr=0x3 -net tap,fd=56,vlan=0,name=hostnet0 -usb -vnc 0.0.0.0:69 -vga cirrus -incoming exec:cat -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 cat: -: Permission denied load of migration failed lsi_scsi: error: Unimplemented message 0x0d lsi_scsi: error: Unimplemented message 0x0d lsi_scsi: error: Unimplemented message 0x0d lsi_scsi: error: Unimplemented message 0x0d lsi_scsi: error: Unimplemented message 0x0d lsi_scsi: error: Unimplemented message 0x0d lsi_scsi: error: Unimplemented message 0x0d lsi_scsi: error: Unimplemented message 0x0d lsi_scsi: error: Unimplemented message 0x0d On Mon, Jun 6, 2011 at 1:33 PM, Koushik Annapureddy <koushik1...@gmail.com>wrote: > Hello Steffen, > > There is no firewall between front end , node1 and node2. Since I am > trying to ping from frontend. > > 1) Does ping work when you migrate back ? > > When I tried to migrate back the VM from node2 to node1 .. It got stuck in > SAVE_MIGRATE state and from the virsh list (node1) its empty.. while in > node2 (virsh list) its showing vm as running. > > 2) 2) Can you deploy a VM directly to node2 ? > (You may have to disable node1 so that subsequent onevm create > go directly to node2) > > I tried to deploy another VM directly on node2 ( by disabling node1) and > the deployed VM got stuck in BOOT mode in node2. > > > > On Mon, Jun 6, 2011 at 1:19 PM, Steffen Neumann <sneum...@ipb-halle.de>wrote: > >> Hi, >> >> On Mon, 2011-06-06 at 11:59 +0300, Koushik Annapureddy wrote: >> > Can any one help in debugging this problem. >> >> First idea is bridge setup, or maybe firewall rules. >> >> 1) Does ping work when you migrate back ? >> >> 2) Can you deploy a VM directly to node2 ? >> (You may have to disable node1 so that subsequent onevm create >> go directly to node2) >> >> Yours, >> Steffen >> >> -- >> IPB Halle AG Massenspektrometrie & Bioinformatik >> Dr. Steffen Neumann http://www.IPB-Halle.DE >> Weinberg 3 http://msbi.bic-gh.de >> 06120 Halle Tel. +49 (0) 345 5582 - 1470 >> +49 (0) 345 5582 - 0 >> sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409 >> >> >> > > > -- > Thanks > Koushik Annapureddy > -- Thanks Koushik Annapureddy
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org