Hi,
Not yet …
I’ ll do that .
Is it a chance that it will be different with 2012R2 ?
Regards,
J.P.
De : Felipe Franciosi [mailto:address@hidden
Envoyé : lundi 22 février 2016 23:02
À : Jean-Pierre Ribeauville; Daniel P. Berrange
Cc : address@hidden
Objet : Re: [Qemu-devel] %cpu used by qemu-kvm processes
I noticed your VM is called WS2008r2. Do you still see this high cpu utilisation with WS2012r2?
As I'm using a RHEV platform , most of these options are automatically adjusted by ovirt ( I presume) .
qemu 120443 1 1 Feb16 ? 00:59:57 /usr/libexec/qemu-kvm -name VM_RHEL7-1 -S -machine rhel6.5.0,accel=kvm,usb=off -cpu SandyBridge -m 4096 -realtime
mlock=off -smp 2,maxcpus=16,sockets=16,cores=1,threads=1 -uuid ad1a8b0e-f8b6-4038-be3d-275f38e66eb3 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7.1-1.el7,serial=4C4C4544-0044-3710-8057-B6C04F4D3632,uuid=ad1a8b0e-f8b6-4038-be3d-275f38e66eb3
-no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-VM_RHEL7-1/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2016-02-16T15:13:59,driftfix=slew -global kvm-pit.lost_tick_policy=discard
-no-hpet -no-shutdown -boot menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x6 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial=
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/00000002-0002-0002-0002-0000000002c5/3988b428-7ca9-4348-9604-89a74e5954a2/images/9d1986c5-2306-47c4-a968-f5d892120b4e/4d0e24fe-4321-4088-a6d2-d4b1093e3df8,if=none,id=drive-virtio-disk0,format=raw,serial=9d1986c5-2306-47c4-a968-f5d892120b4e,cache=none,werror=stop,rerror=stop,aio=native
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=37 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:5c:db:00,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/ad1a8b0e-f8b6-4038-be3d-275f38e66eb3.com.redhat.rhevm.vdsm,server,nowait
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/ad1a8b0e-f8b6-4038-be3d-275f38e66eb3.org.qemu.guest_agent.0,server,nowait -device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev socket,id=charchannel2,path=//var/lib/libvirt/qemu/VM_RHEL7-1_omnivision_1.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=omnivision_1.agent
-chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -device usb-tablet,id=input0 -vnc 10.147.60.186:5,password -k fr -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg
timestamp=on
address@hidden Unix_Agents_And_Servers]#
qemu 47377 1 10 Feb15 ? 09:48:47 /usr/libexec/qemu-kvm -name W2008R2-2 -S -machine rhel6.5.0,accel=kvm,usb=off -cpu SandyBridge,hv_relaxed
-m 2048 -realtime mlock=off -smp 1,maxcpus=16,sockets=16,cores=1,threads=1 -uuid b59a0b76-a04f-4bd8-ac8d-093ac558341f -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7.1-1.el7,serial=4C4C4544-0044-3710-8057-B6C04F4D3632,uuid=b59a0b76-a04f-4bd8-ac8d-093ac558341f
-no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-W2008R2-2/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2016-02-15T12:26:10,clock=vm,driftfix=slew -global kvm-pit.lost_tick_policy=discard
-no-hpet -no-shutdown -boot menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial=
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/00000002-0002-0002-0002-0000000002c5/aa48bdee-af68-4935-9e80-15886531b659/images/7bcde760-a0b5-4a1e-9e47-18ca562e59ab/bd6e4baa-d089-4d60-b8c9-34db10671883,if=none,id=drive-virtio-disk0,format=raw,serial=7bcde760-a0b5-4a1e-9e47-18ca562e59ab,cache=none,werror=stop,rerror=stop,aio=native
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:5c:db:03,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/b59a0b76-a04f-4bd8-ac8d-093ac558341f.com.redhat.rhevm.vdsm,server,nowait
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/b59a0b76-a04f-4bd8-ac8d-093ac558341f.org.qemu.guest_agent.0,server,nowait -device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev socket,id=charchannel2,path=//var/lib/libvirt/qemu/W2008R2-2_omnivision_1.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=omnivision_1.agent
-chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -device usb-tablet,id=input0 -vnc 10.147.60.186:4,password -k fr -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -incoming tcp:[::]:49152 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7
-msg timestamp=on
-----Message d'origine-----
De : Daniel P. Berrange [mailto:address@hidden]
Envoyé : vendredi 19 février 2016 13:01
À : Jean-Pierre Ribeauville
Cc : address@hidden
Objet : Re: [Qemu-devel] %cpu used by qemu-kvm processes
On Fri, Feb 19, 2016 at 11:58:38AM +0000, Jean-Pierre Ribeauville wrote:
> My Guest users ask me why , from Host point of view , there is a big difference interm of CPU % used by qemu-kvmcontrolling processs :
> Result of "top" on the host :
> 8680 qemu 20 0 4939588 4.092g 9668 S 12.6 8.7 927:46.78 qemu-kvm
> 47377 qemu 20 0 2903560 2.121g 9676 S 11.6 4.5 587:08.42 qemu-kvm
> 120443 qemu 20 0 4832180 1.312g 9628 S 1.7 2.8 59:43.79 qemu-kvm
> 43224 qemu 20 0 4825724 2.235g 9664 S 1.0 4.8 105:27.18 qemu-kvm
> 44894 qemu 20 0 4864728 1.450g 9648 S 1.0 3.1 41:30.73 qemu-kvm
> 45000 qemu 20 0 4862676 1.508g 9648 S 0.3 3.2 39:41.45 qemu-kvm
> These guests are just booted , nothing special running on it as shown by "top" ran on the Linux Guest :
> %Cpu(s): 0.0 us, 0.2 sy, 0.0 ni, 99.8 id, 0.0 wa, 0.0 hi, 0.0
> Or on the Windows Guest
> C:\Users\Administrator>wmic cpu get loadpercentage LoadPercentage
> Any idea to help me to answer them ?
At the very least please show the command line arguments used to boot the windows guests, and the arguments used with the Linux guests. The choice of hardware
config can have a significant impact on performance of different guests
|