Am Mon, 7 May 2018 10:54:49 +0200 schrieb Olaf Hering <[email protected]>:
> I think the bug is that something locked 0xc9 ... With qemu-2.10-20171218T100938.ba87166e14 the receiving side shows the same 'qemu-system-i386: Failed to get "write" lock', but this error is somehow noticed by the sender and the migration is aborted. The guest remains running on the sending side. With qemu-2.11-20180214T144105.7c1beb52ed the receiving side shows 'xen be: qdisk-768: xen be: qdisk-768: error: Failed to get "write" lock', but the sender thinks the migration was successful. The guest is moved to the receiver, but can only be destroyed due to the read-only blockdevice. No locking issue with qemu-2.9-20170907T112512.4cd42653f5. Olaf
pgpqzKlpkPMBw.pgp
Description: Digitale Signatur von OpenPGP
