Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The following error occurs when run blockcopy command. It can't be reproduced in libvirt-0.9.10-21.el6.x86_64.
error: unsupported flags (0x8) in function qemuDomainBlockRebase
Version-Release number of selected component (if applicable):
kernel- 2.6.32-276.el6.x86_64
libvirt-0.9.13-2.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.295.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Create domain
# virsh create qed-rhel6.3.xml
Domain qed-rhel6.3 created from qed-rhel6.3.xml
2.virsh blockcopy qed-rhel6.3 vda /var/lib/libvirt/images/copy_target --bandwidth 1
error: unsupported flags (0x8) in function qemuDomainBlockRebase
Actual results:
The following error occurs
error: unsupported flags (0x8) in function qemuDomainBlockRebase
Expected results:
virsh blockcopy command can run successfully.
Additional info:
Same issue as bug 837787 - we compiled out the RHEL-specific patches from RHEL 6.3 in the hopes that upstream qemu will settle on a final block copy setup; if that is too slow in happening, we can re-instate the RHEL-specific patches.
*** This bug has been marked as a duplicate of bug 837787 ***
Description of problem:
it reported error when run the command "virsh blockcopy testhd vda /var/lib/libvirt/images/bak"
Version-Release number of selected component (if applicable):
libvirt-0.10.1-1.el6.x86_64
qemu-kvm-0.12.1.2-2.305.el6.x86_64
kernel-2.6.32-298.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. prepare a guest xml and create it
2. dumpxml
...
<disk type='file' device='disk'>
<driver name='qemu' type='raw' cache='none'/>
<source file='/var/lib/libvirt/images/testhd.img'>
<seclabel relabel='no'/>
</source>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</disk>
...
3.
# virsh blockcopy testhd vda /var/lib/libvirt/images/bak
error: unsupported flags (0x8) in function qemuDomainBlockRebase
4.
# virsh blockcopy testhd vda /var/lib/libvirt/images/bak --finish --wait
error: unsupported flags (0x8) in function qemuDomainBlockRebase
How do we soleve this problem ,reopen a new bug or other ways?
the duplicate bug 837787 is verified, but the problem still exisit as in comment #5
also tested in latest qemu :
qemu-kvm-rhev-0.12.1.2-2.312.el6.x86_64
qemu 1.2 missed Paolo's drive-mirror patches; he's hoping to queue them up shortly for qemu.git in time for 1.3, so there's still a chance that upstream libvirt will have patches for block-copy rather than having to have lots of RHEL-specific patches. Unfortunately, that means we are still playing a waiting game (although I _am_ maintaining a rebased patch series on my local tree to deal with things even if upstream doesn't move fast enough). Whatever happens, you can expect the RHEL build of 0.10.2 later this month to fix the regression.