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.
Bug 861104 - rhel 6.4 qemu-img re-base performance (on local/nfs storage) worse than rhel5.9 when snapshot to a new disk
Summary: rhel 6.4 qemu-img re-base performance (on local/nfs storage) worse than rhel5...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Kevin Wolf
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-27 14:08 UTC by Xiaomei Gao
Modified: 2016-01-15 15:18 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-15 15:18:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Quan Wenli 2012-09-28 06:01:44 UTC 
This is no regression in qcow2 rebase perfomrance compared with 6.3 release host, but significant degradation compared with rhel5.9 host.
Comment 3 Kevin Wolf 2012-09-28 11:25:17 UTC 
> # time qemu-img rebase -f qcow2 -t none -b base_new.qcow2 -F qcow2 sn3.qcow2

What exactly are you comparing? RHEL 5 doesn't even know the -t option, it always uses the equivalent of -t writeback. For an apples-to-apples comparison you need to use the same option on RHEL 6.

Another thing to try is running a RHEL 5 qemu-img on a RHEL 6 machine or vice versa, in order to check if the difference is in qemu-img or possibly in the kernel or other components.
Comment 4 Xiaomei Gao 2012-09-29 01:32:02 UTC 
(In reply to comment #3)
> > # time qemu-img rebase -f qcow2 -t none -b base_new.qcow2 -F qcow2 sn3.qcow2
> 
> What exactly are you comparing? RHEL 5 doesn't even know the -t option, it
> always uses the equivalent of -t writeback. For an apples-to-apples
> comparison you need to use the same option on RHEL 6.

Thanks for reminder. but -t writeback option on RHEL6 is also about 24 s.
 
> Another thing to try is running a RHEL 5 qemu-img on a RHEL 6 machine or
> vice versa, in order to check if the difference is in qemu-img or possibly
> in the kernel or other components.

Running a RHEL 5 qemu-img on a RHEL 6 machine and test result is 6.722 s, so the difference is in qemu-img.
Comment 5 Kevin Wolf 2012-10-12 14:50:33 UTC 
Okay, first part of the explanation is this on RHEL 5:

Formatting 'base.qcow2', fmt=qcow2, size=8388608 kB
Formatting 'sn1.qcow2', fmt=qcow2, backing_file=base.qcow2, backing_fmt=qcow2, size=8388608 kB
Formatting 'sn2.qcow2', fmt=qcow2, backing_file=sn1.qcow2, backing_fmt=qcow2, size=8388608 kB
Formatting 'sn3.qcow2', fmt=qcow2, backing_file=sn2.qcow2, backing_fmt=qcow2, size=8388608 kB

It doesn't actually creaet 20G images there, but only 8G images, like base.qcow2. But even when I make it always 8G there's still some difference between RHEL 5 and upstream qemu (ever since rebase was introduced) that I need to figure out...
Comment 12 Steve Whitehouse 2015-12-11 13:34:29 UTC 
Is there an NFS component to this bug? I couldn't figure out whether there was or not from the above.
Comment 13 Chao Yang 2015-12-14 01:00:14 UTC 
Yanhui,

Could you please try to provide the info that Steve needs?
Comment 14 Yanhui Ma 2015-12-15 09:27:25 UTC 
(In reply to Steve Whitehouse from comment #12)
> Is there an NFS component to this bug? I couldn't figure out whether there
> was or not from the above.
Hi, steve
From description of problem in comment 0, this issue existed on both local storage and nfs storage.
Note You need to log in before you can comment on or make changes to this bug.