Description of problem: after reboot the host, guest does not start anymore. Version-Release number of selected component (if applicable): lib64virt0-5.3.0-2.mga7 How reproducible: every reboot of host with guests. Steps to Reproduce: 1. virsh edit guestname <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/virtuell/guestname.qcow2'/> <backingStore type='file'> <format type='qcow2'/> <source file='/virtuell/guestname.snapshot.qcow2'/> </backingStore> <target dev='hda' bus='ide'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> 2. reboot host, guest does not start (autostart is on) backingStore source is now the normal image not the snapshot. Normal source is now snapshot, but snapshot doesn't exists it can't start. 3. virsh edit guestname <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/virtuell/guestname.snapshot.qcow2'/> <backingStore type='file'> <format type='qcow2'/> <source file='/virtuell/guestname.qcow2'/> </backingStore> <target dev='hda' bus='ide'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> 4. change this back and you can start the guest.
Libvirt has no registered maintainer, but tv has dealt with it most in the past; so assigning to you (rather than globally) provisionally.
Assignee: bugsquad => thierry.vignaud
detailed description. make backup of running machines descripted on libvirt.org https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit everything is fine so far. edit the machine xml with virsh edit and it looks like this: <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/virtuell/guestname.qcow2'/> <target dev='hda' bus='ide'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> but if you make a reload or restart of libvirtd then: <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/virtuell/guestname.snapshot.qcow2'/> <backingStore type='file'> <format type='qcow2'/> <source file='/virtuell/guestname.qcow2'/> </backingStore> <target dev='hda' bus='ide'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> The machine could never start anymore because the guestname.snapshot.qcow2 is no longer active after virsh blockcommit guestname vda --active --verbose --pivot which is right. The entry for the 1st source file is wrong. It must be the entry from the backingStore element guestname.qcow2
additional info in Mageia 6 everything works fine. Only Mageia 7 has this trouble and it is of course important. If you have many virtuell Machines you couldn't repair any of them via virsh edit machinename after restart. This could not be a solution for this problem. I can't upgrade to Mageia 7 at this time.
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Status: NEW => RESOLVEDResolution: (none) => OLD