[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] live migration from 4.12 to 4.13 fails due to qemu-xen bug
I did not find anything in the Xen 4.13 release notes, so I'm asking here: This HVM domU fails to live migrate from staging-4.12 to staging-4.13: name='hvm' serial='pty' vcpus='4' memory='888' disk=[ 'vdev=xvda, format=raw, access=rw, target=/netshare/disk0.raw' ] vif=[ 'bridge=br0,mac=3c:27:63:58:ca:35' ] builder="hvm" device_model_version="qemu-xen" The receiving qemu fails like that: char device redirected to /dev/pts/3 (label serial0) xen_ram_alloc: do not alloc 37000000 bytes of ram at 0 when runstate is INMIGRATE xen_ram_alloc: do not alloc 800000 bytes of ram at 37000000 when runstate is INMIGRATE xen_ram_alloc: do not alloc 10000 bytes of ram at 37800000 when runstate is INMIGRATE xen_ram_alloc: do not alloc 40000 bytes of ram at 37840000 when runstate is INMIGRATE VNC server running on 127.0.0.1:5900 qemu-system-i386: Unknown savevm section type 111 qemu-system-i386: load of migration failed: Invalid argument Google does not seem to know this specific error. In fact, every upstream qemu-3.x fails to migrate to qemu-4.x. Does anyone know what incompatible change was done to qemu.git? Olaf Attachment:
pgpl7qmFIJ6nc.pgp _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |