I just installed a second kvm node with 3x2TB in a raid5 config. I'm using solusvm and I have one vps installed on the node and my loads are: 129.26 122.12 91.94. I know the vps isn't doing anything, it's the node. When I remove all vps from the node the cpu loads are normal around 1.50.
When I run top -c I get:
24337 root 20 0 1450m 571m 4584 S 17.0 0.4 5:15.75 /usr/libexec/qemu-kvm -global virtio-blk-pci.scsi=off -nodefconfig -nodefaults -nographic -machine accel=kvm:tcg -cpu host,+kvmclock -m 500 -no-reboot -kernel /var/tmp/.guestfs-0/kernel.24325 -initrd /var/tmp/.guestfs-0/initrd.24325 -device virtio-scsi-pc
22022 root 20 0 1449m 526m 4584 S 16.6 0.4 9:17.96 /usr/libexec/qemu-kvm -global virtio-blk-pci.scsi=off -nodefconfig -nodefaults -nographic -machine accel=kvm:tcg -cpu host,+kvmclock -m 500 -no-reboot -kernel /var/tmp/.guestfs-0/kernel.22010 -initrd /var/tmp/.guestfs-0/initrd.22010 -device virtio-scsi-pc
These are the two processes that are killing the CPU.
When I create a vps it starts with an iso mounted but when i try to install a template it doesn't start so I manually start it using:
virsh create /home/kvm/kvmID/kvmID.xml
The vps starts but only shows the iso mounted and not the installed template. I synced my templates with the new kvm node and transferred all my templates and isos to it. I can't get the new node to work, the old one works totally fine though. I installed them the same way, so my conclusion is that it's the raid5 config. Any thoughts?
http://ift.tt/1dvHQ0Z
0 comments:
Post a Comment