Bug 795610 - rhel6.1 qemu-kvm host, rhel5.x guest running very slow.
Summary: rhel6.1 qemu-kvm host, rhel5.x guest running very slow.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Amos Kong
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-21 03:41 UTC by davidyangyi
Modified: 2015-05-25 00:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-25 08:40:24 UTC
Target Upstream Version:


Attachments (Terms of Use)
template deployment.0 (1.15 KB, text/plain)
2012-02-21 03:41 UTC, davidyangyi
no flags Details

Description davidyangyi 2012-02-21 03:41:14 UTC
Created attachment 564559 [details]
template deployment.0

Description of problem:
I use rhel6.1 as qemu-kvm host. using opennebula2.2

I set up rhel5.3/5.5/5.6 guests.
But the rhel5.x guests are running very slow.

While I set up another rhel6.1 guest, it is running fast as normal.

Version-Release number of selected component (if applicable):
Host: Red Hat Enterprise Linux Server release 6.1 (Santiago)

Guest: Red Hat Enterprise Linux Server release 5.6 (Tikanga)

How reproducible:


Steps to Reproduce:
1. use virt-manager to install a rhel5.x.img with desktop
2. copy rhel5.x.img to disk.0
3. use deployment.0 to deploy
4. virsh create deployment.0
  
Actual results:

Expected results:
in virt-manager, open the one-7 domain, you can see login very slow and openning a term very slow too

Additional info:

Comment 2 Dor Laor 2012-03-15 10:17:46 UTC
Can you please provide more details - what's slow (time to boot? time to open xterm), can you measure network IO / block IO ?

Please upgrade to newer host/guest as well rhel6.2/rhel5.8.
Try using virtio devices in the guests.
Maybe your original image has issues? Please try to install a fresh image.

Comment 3 Amos Kong 2012-05-03 05:51:24 UTC
Hi davidyangyi, 

Any update of comment #2 ?

Comment 5 Ronen Hod 2012-06-25 08:40:24 UTC
Closing, no replies from the reporter, and otherwise, we are not aware of such issue.


Note You need to log in before you can comment on or make changes to this bug.