Van: libvirt-users-bounces@xxxxxxxxxx
[mailto:libvirt-users-bounces@xxxxxxxxxx] Namens Firat KÜÇÜK Hello, virsh migrate --live --domain my-guest --verbose --persistent --copy-storage-all --desturi qemu+ssh://root@my-otherhost/system
<disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/opt/datastore/bulutkare-1118.img'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk>
I think virsh will do a bitewise copy of the content of the disk and creates a .qcow2 file without backing store on the target. (please check with qemu-img info on the destination file)
Your guest thinks something is wrong because the hypervisor still has the backingstore description in its xml. That’s why the guest go’s in to failsafe mode and remount’s the root file system as read-only.
I think you can fix this by creating an separate xml file without the backing store description and use the option --xml in the virsh migrate command…
after live migration completed, filesystem blocked write operations. root@my-guest:~/tmp# touch hello touch: cannot touch ‘hello’: Read-only file system
|
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users