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.
Created attachment 493731[details]
block-rhel6.1-snp1-windows2k8r2sp1-iometer
Description of problem:
According to comment #36 in bug 621834,keep tracking virtio-win on wirte i/o 's performance in rhel6.2.
Version-Release number of selected component (if applicable):
Kernel-2.6.32-125.el6.x86_64
qemu-kvm-0.12.1.2-2.152.el6.x86_64
Guest = windows 2k8 r2 sp1
virtio-win-prewhql-0.1-8
How reproducible:
always
Steps to Reproduce:
1.run iometer benmark with attached configuration file.
2.
3.
Actual results:
Expected results:
Additional info:
Hi, Vadim
Could we set the bug to verified status and open new bug in 6.6 to track the issue described in comment #11, or what better suggestions to handle the bug?
Thanks
Xiaomei
(In reply to Xiaomei Gao from comment #13)
> Hi, Vadim
>
> Could we set the bug to verified status and open new bug in 6.6 to track
> the issue described in comment #11,
Hi Xiaomei,
Yes, it will be perfect.
Best regards,
Vadim.
> or what better suggestions to handle the
> bug?
>
> Thanks
> Xiaomei