Bug 692770
| Summary: | windows installation is slow | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Suqin Huang <shuang> |
| Component: | kvm | Assignee: | Kevin Wolf <kwolf> |
| Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.7 | CC: | gcosta, juzhang, michen, mkenneth, virt-maint, xwei |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-28 14:54:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 580948 | ||
|
Description
Suqin Huang
2011-04-01 05:16:54 UTC
Do you notice this slowness only on this kind of guest ? Is the guest also slow on other parts of the installation other than file-copy ? My first hunch is that we have a qcow2 slowness problem here. (In reply to comment #1) > Do you notice this slowness only on this kind of guest ? > Is the guest also slow on other parts of the installation other than file-copy > ? > My first hunch is that we have a qcow2 slowness problem here. Hi Glauber, I tried several times, when installing with qcow2, it's much slower than raw format. if with memory overcommitment (boot guest with max(host mem)): raw image can finish installation within 120 mins qcow2 image even cannot finished file expanding(approx 80% when 120 mins past) not memory overcommitment : raw image can finish installation within 40 mins (mostly 20+ mins) qcow2 image mostly can finish installtion within 60 mins cmd to start installation (just image format differs : qcow2/raw): qemu-kvm -name '08r2-ins' -monitor stdio \ -serial unix:'/tmp/serial \ -drive file='/win2008r2-64-virtio.qcow2',index=0,if=virtio,media=disk,cache=none,boot=on,format=qcow2 -net nic,vlan=0,model=virtio,macaddr='9a:6b:1e:67:cf:66' \ -net tap,vlan=0,ifname='t08r2',script='/qemu-ifup-switch',downscript='no' \ \ -m 12003 \ \ -smp 16,cores=1,threads=1,sockets=16 \ -drive file='/2008_r2_with_sp1_x64.iso',media=cdrom,index=1 \ -drive file='/winutils.iso',media=cdrom,index=2 \ -drive file='/virtio-win.iso.el5',media=cdrom,index=3 \ -cpu qemu64,+sse2 -soundhw ac97 \ -fda '/answer.vfd' \ -vnc :0 -rtc-td-hack -M rhel5.6.0 -boot d -usbdevice tablet host info: free -m total used free shared buffers cached Mem: 12003 343 11660 0 3 117 -/+ buffers/cache: 222 11781 Swap: 14015 160 13855 cpu info (16 processors in total) processor : 15 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Intel(R) Xeon(R) CPU E5620 @ 2.40GHz stepping : 2 cpu MHz : 2394.069 cache size : 12288 KB physical id : 0 siblings : 8 core id : 10 cpu cores : 4 apicid : 21 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx pdpe1gb rdtscp lm constant_tsc ida nonstop_tsc arat pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm bogomips : 4787.94 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: [8] Best Regards, Xiaoqing. > (In reply to comment #2) > > (In reply to comment #1) > > > Do you notice this slowness only on this kind of guest ? > > > Is the guest also slow on other parts of the installation other than file-copy > > > ? > > > My first hunch is that we have a qcow2 slowness problem here. > > > > > > Hi Glauber, > > > > I tried several times, > > when installing with qcow2, it's much slower than raw format. > > > > > > if with memory overcommitment (boot guest with max(host mem)): > > raw image can finish installation within 120 mins > > qcow2 image even cannot finished file expanding(approx 80% when 120 mins past) > > Does it swap to disk? Or is KSM around and makes some room? > If it swaps to disk, then the speed sounds OK to me. > > > > > not memory overcommitment : > > raw image can finish installation within 40 mins (mostly 20+ mins) > > So, is that a regression from 5.6? no, can reproduce on rhel5.6 2.6.18-238.el5 kvm-83-224.el5 > > > qcow2 image mostly can finish installtion within 60 mins > > > > > > cmd to start installation (just image format differs : qcow2/raw): > > qemu-kvm -name '08r2-ins' -monitor stdio \ > > -serial unix:'/tmp/serial \ > > -drive > > file='/win2008r2-64-virtio.qcow2',index=0,if=virtio,media=disk,cache=none,boot=on,format=qcow2 > > -net nic,vlan=0,model=virtio,macaddr='9a:6b:1e:67:cf:66' \ > > -net tap,vlan=0,ifname='t08r2',script='/qemu-ifup-switch',downscript='no' \ > > \ > > -m 12003 \ > > \ > > -smp 16,cores=1,threads=1,sockets=16 \ > > Can you try with less vCPUs? Say, 2? yes, also slow when install with 2 cpu & 4G mem Intel e5620 (16cpu & 12Gmem) 1 hour only expend 60% others, can not reproduce on AMD Phenom(tm) 9600B finish installation within 40 mins Known problem, qcow2 is slow on RHEL 5 during cluster allocation. We won't be able to make further optimisations for RHEL 5, it would require very invasive changes. |