From: Serge Hallyn <1307473@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1307473] Re: guest hang due to missing clock interrupt
Date: Mon, 14 Jul 2014 13:07:24 -0000 [thread overview]
Message-ID: <20140714130724.GD1132@ubuntumail> (raw)
In-Reply-To: 20140714074139.31498.46313.malone@chaenomeles.canonical.com
Quoting Ondergetekende (1307473@bugs.launchpad.net):
> We've resolved our issues by disabling KSM on the affected nodes. All of
> the non-affected nodes didn't have KSM enabled (due to a packaging bug
> elsewhere). After disabling KSM, our problems went away gradually in ~3
> days.
>
> This means we're no longer affected by this issue (and given the other
> reports, probably never were).
And which specific kernel are you on?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
Status in QEMU:
New
Status in “linux” package in Ubuntu:
Confirmed
Status in “qemu” package in Ubuntu:
Confirmed
Bug description:
I noticed on 2 different systems that after upgrade from precise to latest trusty VMs are crashing:
- in case of Windows VMs I'm getting BSOD with error message: "A clock interrupt was not received on a secondary processor within the allocated time interval."
- On linux VMs I'm noticing "hrtimer: interrupt took 2992229 ns" messages
- On some proprietary virtual appliances I'm noticing crashes an due to missing timer interrupts
QEMU version is:
QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3)
Full command line:
qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc-
i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
-smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a-
4aa1-6bb2-ef06-a6666b4d020a -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
-no-shutdown -boot strict=on -device piix3-usb-
uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-
disk0,id=virtio-disk0,bootindex=1 -drive
file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en-
us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,if=none,id=drive-
ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive
=drive-ide0-0-0,id=ide0-0-0 -drive file=/home/damarion/iso/virtio-
win-0.1-74.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
-netdev tap,fd=24,id=hostnet0 -device
e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device isa-
serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0
-vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1307473/+subscriptions
next prev parent reply other threads:[~2014-07-14 13:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140414120717.17314.11606.malonedeb@chaenomeles.canonical.com>
2014-05-05 20:49 ` [Qemu-devel] [Bug 1307473] Re: guest hang due to missing clock interrupt Damjan Marion
2014-05-09 23:26 ` Launchpad Bug Tracker
2014-05-16 13:51 ` Krzysztof Cybulski
2014-06-24 8:00 ` urusha
2014-06-24 8:02 ` urusha
2014-06-24 8:05 ` urusha
2014-06-25 16:29 ` Serge Hallyn
2014-06-25 16:30 ` [Qemu-devel] [Bug 1307473] Missing required logs Brad Figg
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] Re: guest hang due to missing clock interrupt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] BootDmesg.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] CurrentDmesg.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] Dependencies.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] IwConfig.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] Lspci.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] Lsusb.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] ProcCpuinfo.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] ProcEnviron.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] ProcInterrupts.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] ProcModules.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] UdevDb.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] UdevLog.txt Ilya Almametov
2014-07-01 6:23 ` [Qemu-devel] [Bug 1307473] WifiSyslog.txt Ilya Almametov
2014-07-01 6:41 ` [Qemu-devel] [Bug 1307473] Re: guest hang due to missing clock interrupt Ilya Almametov
2014-07-03 5:55 ` urusha
2014-07-03 6:17 ` Ilya Almametov
2014-07-03 14:05 ` Serge Hallyn
2014-07-08 10:44 ` Ondergetekende
2014-07-08 10:50 ` Ondergetekende
2014-07-08 12:07 ` John Johansen
2014-07-09 8:49 ` Ondergetekende
2014-07-09 17:28 ` Dr. David Alan Gilbert
2014-07-11 15:23 ` Mike Lowe
2014-07-11 16:57 ` Mike Lowe
2014-07-14 7:41 ` Ondergetekende
2014-07-14 13:07 ` Serge Hallyn [this message]
2014-07-15 17:59 ` Mike Lowe
2014-07-17 7:04 ` Jan Müller
2014-07-17 12:53 ` Paolo Bonzini
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=20140714130724.GD1132@ubuntumail \
--to=1307473@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).