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:
KVM QE compared the list of cmd line and devices difference between rhel6.4 and rhel7.0. Found lot of storage migration related commands are different. From KVM QE POV, RHEL7 storage migration related commands should much closer RHEL not upstream.
Version-Release number of selected component (if applicable):
Host Kernel
#uname -r
3.7.0-0.30.el7.x86_64
qemu-kvm version
qemu-kvm-1.3.0-3.el7.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Storage vmotion related commands
RHEL6.4
block-stream(copy data from a backing file into a block device)
block-job-cancel(stop an active block streaming operation)
block-job-set-speed
blockdev-snapshot-sync
__com.redhat_drive-mirror
__com.redhat_drive-reopen
__com.redhat_block-commit
RHEL7.0
block_stream(copy data from a backing file into a block device)
block_job_cancel(stop an active block streaming operation)
block_job_set_speed
no blockdev-snapshot-sync command on rhel7.0
no __com.redhat_drive-mirror on rhel7.0
no __com.redhat_drive-reopen on rhel7.0
no __com.redhat_block-commit on rhel7.0
Added three commands on rhel7.0, do we support? How to use?
block_job_pause
block_job_resume
block_job_complete
Expected results:
RHEL7 storage migration related commands should much closer RHEL not upstream
Additional info:
The commands that were introduced in RHEL are a little different from the ones upstream, but we are not going to forward-port the RHEL6 changes. There are improvements in the upstream versions and those are the versions that libvirt uses, too.
The new commands in RHEL7 are:
- snapshot_blkdev, drive_mirror, block_commit for HMP
- blockdev-snapshot-sync, drive-mirror, block-commit for QMP
- block_job_complete (HMP) and block-job-complete (QMP) replace __com.redhat_drive-reopen
Description of problem: KVM QE compared the list of cmd line and devices difference between rhel6.4 and rhel7.0. Found lot of storage migration related commands are different. From KVM QE POV, RHEL7 storage migration related commands should much closer RHEL not upstream. Version-Release number of selected component (if applicable): Host Kernel #uname -r 3.7.0-0.30.el7.x86_64 qemu-kvm version qemu-kvm-1.3.0-3.el7.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Storage vmotion related commands RHEL6.4 block-stream(copy data from a backing file into a block device) block-job-cancel(stop an active block streaming operation) block-job-set-speed blockdev-snapshot-sync __com.redhat_drive-mirror __com.redhat_drive-reopen __com.redhat_block-commit RHEL7.0 block_stream(copy data from a backing file into a block device) block_job_cancel(stop an active block streaming operation) block_job_set_speed no blockdev-snapshot-sync command on rhel7.0 no __com.redhat_drive-mirror on rhel7.0 no __com.redhat_drive-reopen on rhel7.0 no __com.redhat_block-commit on rhel7.0 Added three commands on rhel7.0, do we support? How to use? block_job_pause block_job_resume block_job_complete Expected results: RHEL7 storage migration related commands should much closer RHEL not upstream Additional info: