Hello,
I have multiple proxmox server running VE 3.4. They all are at different locations and have different hardware. I noticet that they all have high load, between 2-4.
I also noticet that in every proxmox if I look #top, the proccess that consumes 100%. These are VM-s that run on Windows 7
VM conf:
VM itself sits in idle (5-10% CPU usage).
I have updated VirtIO drivers to the latest and all windows updates are installed.
I have checked that ballooning service is not enabled.
Host pveversion:
I have multiple proxmox server running VE 3.4. They all are at different locations and have different hardware. I noticet that they all have high load, between 2-4.
I also noticet that in every proxmox if I look #top, the proccess that consumes 100%. These are VM-s that run on Windows 7
Code:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5645 root 20 0 1686m 1.0g 1660 S 202 3.2 161851:47 kvm
Code:
# ps aux | grep 5645
root 5645 96.5 3.2 1726648 1066536 ? Sl 2016 161852:07 /usr/bin/kvm -id 107 -chardev socket,id=qmp,path=/var/run/qemu-server/107.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/107.vnc,x509,password -pidfile /var/run/qemu-server/107.pid -daemonize -name torm-vmsupport -smp 2,sockets=1,cores=2,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga std -no-hpet -cpu kvm64,hv_spinlocks=0xffff,hv_relaxed,+lahf_lm,+x2apic,+sep -m 1024 -k en-us -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:6af411fcbb5 -drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -drive file=/dev/pve/vm-107-disk-1,if=none,id=drive-virtio0,cache=writeback,aio=threads,detect-zeroes=on -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 -drive if=none,id=drive-ide0,media=cdrom,aio=native -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=201 -netdev type=tap,id=net0,ifname=tap107i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=96:CC:0D:A3:97:5C,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc driftfix=slew,base=localtime -global kvm-pit.lost_tick_policy=discardVM conf:
Code:
~# more /etc/pve/qemu-server/107.conf
bootdisk: virtio0
cores: 2
ide0: none,media=cdrom
ide2: none,media=cdrom
memory: 1024
name: torm-vmsupport
net0: virtio=96:CC:0D:A3:97:5C,bridge=vmbr0
onboot: 1
ostype: win7
sockets: 1
virtio0: vms:vm-107-disk-1,cache=writeback,size=62GVM itself sits in idle (5-10% CPU usage).
I have updated VirtIO drivers to the latest and all windows updates are installed.
I have checked that ballooning service is not enabled.
Host pveversion:
Code:
# pveversion -v
proxmox-ve-2.6.32: 3.4-172 (running kernel: 2.6.32-44-pve)
pve-manager: 3.4-13 (running version: 3.4-13/4c745357)
pve-kernel-2.6.32-44-pve: 2.6.32-172
pve-kernel-2.6.32-39-pve: 2.6.32-157
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-19
qemu-server: 3.4-7
pve-firmware: 1.1-5
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-34
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-24
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1