Am 10.02.2015 um 10:49 schrieb Paolo Bonzini:
On 10/02/2015 10:26, Peter Lieven wrote:
Hi,
while migrating vServers from 2.1.0 to 2.2.0 I see the following
assertion that seems to have
been introduced between 2.1.0 and 2.2.0 trigger on the destination. This
happens in a serious
amount of cases. In most cases it works flawlessly on the second attempt
to migrate the vServer
(same source and same destination).
Any hints how to debug the root cause?
How can anyone help without knowing anything about your configuration? :)
My hope was that anyone has observed this post 2.2.0 already and there
is a fix available ;-)
Can you indicate what info would be helpful debugging this?
Cmdline is:
/usr/bin/qemu-2.2.0 -enable-kvm -M pc-i440fx-2.1 -nodefaults -netdev type=tap,id=guest19,script=no,downscript=no,ifname=tap19,vnet_hdr -device virtio-net-pci,netdev=guest19,mac=52:54:00:80:00:55 -netdev
type=tap,id=guest20,script=no,downscript=no,ifname=tap20,vnet_hdr -device virtio-net-pci,netdev=guest20,mac=52:54:00:80:00:6f -netdev type=tap,id=guest21,script=no,downscript=no,ifname=tap21,vnet_hdr -device
virtio-net-pci,netdev=guest21,mac=52:54:00:80:00:75 -serial null -parallel null -m 496 -monitor tcp:0:4011,server,nowait -vnc :11 -qmp tcp:0:3011,server,nowait -name 'gw-5000123' -boot order=nc,menu=on -drive
index=2,media=cdrom,if=ide,cache=unsafe,aio=native,readonly=on -k de -incoming tcp:0:5011 -pidfile /var/run/qemu/vm-115.pid -mem-path /hugepages -mem-prealloc -rtc base=utc -usb -usbdevice tablet -no-hpet -vga vmware -cpu qemu64
Linux guest kernels observed so far:
3.2.0
3.13
Thanks,
Peter
