Created attachment 1671347 [details] libvirtd log of step4, VM xml, disk dest xml Description of problem: As subject Version-Release number of selected component (if applicable): libvirt-6.0.0-13.virtcov.el8.x86_64 qemu-kvm-4.2.0-15.module+el8.2.0+6029+618ef2ec.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start a VM 2. Prepare a scsi disk for host. 3. Prepare a xml of scsi pr disk dest with luks format # cat pr.xml <disk type="block" device="lun"> <driver name="qemu" type="raw"/> <source dev="/dev/sdc"> <reservations managed="yes"/> </source> <target dev="sda" bus="scsi"/> </disk> 4. Do blockcopy # virsh blockcopy new sda --xml pr.xml --pivot --transient-job --verbose --wait error: internal error: unable to execute QEMU command 'blockdev-add': No persistent reservation manager with id 'pr-helper0' Actual results: As step4 Expected results: pr-helper0 should be created for this blockcopy Additional info:
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.
Authorized
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Hi, This bug can still be reproduced now. So I've reopened it. Do we have plan/requirement to implement it? If not, please help to close it as WONTFIX again. Thanks. Test Version: libvirt-8.9.0-2.el9.x86_64 qemu-kvm-7.1.0-5.el9.x86_64 qemu-pr-helper-7.1.0-5.el9.x86_64 Test Steps: 1. Prepare a running guest. # virsh domstate test running 2. Prepare a target disk xml. # cat disk.xml <disk type="block" device="lun"> <driver name="qemu" type="raw"/> <source dev="/dev/sdb"> <reservations managed="yes"/> </source> <target dev="sda" bus="scsi"/> </disk> 3. Do blockcopy. # virsh blockcopy test vda --xml disk.xml --transient-job error: internal error: unable to execute QEMU command 'blockdev-add': No persistent reservation manager with id 'pr-helper0'
Hi Peter, Please help look at this bug. It is not update since reported.
(In reply to Han Han from comment #11) > Hi Peter, > Please help look at this bug. It is not update since reported. It's on the backlog as it's low priority.