VM running 3 times in cluster after failed migration

[adoII]

Hi,
I tried to live migrate a vm from one proxmox 2.1 host to another in a cluster

The migration failed because there was an old ssh key for the proxmox server in known_hosts

I have now the following processes on the servers, how can I clean up ?

Server 1:

san03:~# ps ax|grep 146
  22620 ?        Sl   748:09 /usr/bin/kvm -id 146 -chardev socket,id=monitor,path=/var/run/qemu-server/146.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/146.vnc,x509,password -pidfile /var/run/qemu-server/146.pid -daemonize -usbdevice tablet -name v-sql1.SAN01 -smp sockets=1,cores=2 -nodefaults -boot menu=on -vga cirrus -k de -drive file=/nexenta-new/images/146/vm-146-disk-2.qcow2,if=none,id=drive-virtio1,aio=native -device virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb -drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -drive file=/nexenta-new/images/146/vm-146-disk-1.qcow2,if=none,id=drive-virtio0,aio=native -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=101 -m 2048 -netdev type=tap,id=net0,ifname=tap146i0,script=/var/lib/qemu-server/pve-bridge -device virtio-net-pci,mac=32:F0:84:7E:C3:B3,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
 391713 ?        Ss     0:00 task UPID:san03:0005FA21:049412AA:4FE18F45:qmigrate:146:root@pam:
 391730 ?        S      0:00 /usr/bin/ssh -c blowfish -o BatchMode=yes root@213.164.159.135 qm start 146 --stateuri tcp --skiplock

Server 2 seems to run 2 more instances of vm 146 ...

oot@san02:/var/log# ps ax|grep 146
 137693 pts/0    S+     0:00 grep 146
 761124 ?        Ss     0:00 /usr/bin/perl -w /usr/sbin/qm start 146 --stateuri tcp --skiplock
 761125 ?        Ss     0:00 task UPID:san02:000B9D25:03672332:4FE18F47:qmstart:146:root@pam:
 761128 ?        S      0:00 /usr/bin/kvm -id 146 -chardev socket,id=monitor,path=/var/run/qemu-server/146.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/146.vnc,x509,password -pidfile /var/run/qemu-server/146.pid -daemonize -incoming tcp:localhost:60000 -usbdevice tablet -name v-sql1.SAN01 -smp sockets=1,cores=2 -nodefaults -boot menu=on -vga cirrus -k de -drive file=/nexenta-new/images/146/vm-146-disk-2.qcow2,if=none,id=drive-virtio1,aio=native -device virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb -drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -drive file=/nexenta-new/images/146/vm-146-disk-1.qcow2,if=none,id=drive-virtio0,aio=native -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=101 -m 2048 -netdev type=tap,id=net0,ifname=tap146i0,script=/var/lib/qemu-server/pve-bridge,vhost=on -device virtio-net-pci,mac=32:F0:84:7E:C3:B3,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
 761130 ?        R      0:11 /usr/bin/kvm -id 146 -chardev socket,id=monitor,path=/var/run/qemu-server/146.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/146.vnc,x509,password -pidfile /var/run/qemu-server/146.pid -daemonize -incoming tcp:localhost:60000 -usbdevice tablet -name ventic-sql1.SAN01 -smp sockets=1,cores=2 -nodefaults -boot menu=on -vga cirrus -k de -drive file=/nexenta-new/images/146/vm-146-disk-2.qcow2,if=none,id=drive-virtio1,aio=native -device virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb -drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -drive file=/nexenta-new/images/146/vm-146-disk-1.qcow2,if=none,id=drive-virtio0,aio=native -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=101 -m 2048 -netdev type=tap,id=net0,ifname=tap146i0,script=/var/lib/qemu-server/pve-bridge,vhost=on -device virtio-net-pci,mac=32:F0:84:7E:C3:B3,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300

 

[tom]

seems similar to this.
https://bugzilla.proxmox.com/show_bug.cgi?id=189

 

[dietmar]

I guess you need to 'kill' those tasks, and restart the VM.

 

[dietmar]

I filed a new bug for that: https://bugzilla.proxmox.com/show_bug.cgi?id=217