|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v1] libxl: fix migration of PV and PVH domUs with and without qemu
On Wed, Apr 10, 2019 at 12:33:38PM +0200, Olaf Hering wrote: > If a domU has a qemu-xen instance attached, it is required to call qemus > "xen-save-devices-state" method. Without it, the receiving side of a PV or > PVH migration may be unable to lock the image: > > xen be: qdisk-51712: xen be: qdisk-51712: error: Failed to get "write" lock > error: Failed to get "write" lock > xen be: qdisk-51712: xen be: qdisk-51712: initialise() failed > initialise() failed I haven't managed to reproduce this, but this bug will go away with QEMU 4.0. The backend in QEMU 4.0 will not lock the disk image anymore. Maybe we could simply apply a patch to our qemu-xen trees which avoid the lock on disk images for the pv disks? That would avoid a convoluted patch to libxl. The lock appeared in QEMU 2.10 (qemu-xen-4.10), and won't exist for pv guest with QEMU 4.0 (qemu-xen-4.13). -- Anthony PERARD _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |