From: Phil Daws <uxbod@splatnix.net>
To: kvm@vger.kernel.org
Cc: Andrew Jones <drjones@redhat.com>
Subject: Re: KVM guest 100% cpu lock up
Date: Wed, 27 Mar 2013 09:03:52 +0000 (GMT) [thread overview]
Message-ID: <457807553.717243.1364375032367.JavaMail.root@innovot.com> (raw)
In-Reply-To: <601353539.385347.1363623011017.JavaMail.root@innovot.com>
This problem still persists :( I have read a few articles about setting the clocksource to acpi_pm and the guest was stable for a couple of days, then low and behold the CPU on the guest started to climb too 100% and completely froze. Only way to recover it was hard reset on the guest machine :( Any thoughts ?
----- Original Message -----
From: "Phil Daws" <uxbod@splatnix.net>
To: "Andrew Jones" <drjones@redhat.com>
Cc: kvm@vger.kernel.org
Sent: Monday, 18 March, 2013 4:10:11 PM
Subject: Re: KVM guest 100% cpu lock up
----- Original Message -----
From: "Andrew Jones" <drjones@redhat.com>
To: "Phil Daws" <uxbod@splatnix.net>
Cc: kvm@vger.kernel.org
Sent: Monday, 18 March, 2013 4:08:48 PM
Subject: Re: KVM guest 100% cpu lock up
----- Original Message -----
> Hello,
>
> I am having an intermittent issue where one of my KVM guests is
> locking up and when checking the process its running @ 100% cpu.
> The host is CentOS 6.4 running the kernel
> kernel-2.6.32-358.0.1.el6.x86_64.
>
> Would it be worth attempting to compile a 3.2 kernel and use the
> latest qemu-kvm package instead ?
>
Can you please supply the full qemu command line?
thanks,
drew
> Thanks.
> --
qemu 5919 22.5 22.3 2705424 1798484 ? Sl 15:23 4:44 /usr/libexec/qemu-kvm -name vs2 -S -M rhel6.4.0 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -uuid 38fb2902-06a5-0781-f14a-f17bf96668f1 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vs2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/images/vs2.img,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=22,id=hostnet0,v
host=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=54:52:00:02:01:04,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -devi
ce usb-tablet,id=input0 -vnc 127.0.0.1:2 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-03-27 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1888560585.384583.1363621365951.JavaMail.root@innovot.com>
2013-03-18 15:45 ` KVM guest 100% cpu lock up Phil Daws
2013-03-18 16:08 ` Andrew Jones
2013-03-18 16:10 ` Phil Daws
2013-03-27 9:03 ` Phil Daws [this message]
2013-04-01 8:52 ` Phil Daws
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457807553.717243.1364375032367.JavaMail.root@innovot.com \
--to=uxbod@splatnix.net \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.