From: Kevin Wolf <kwolf@redhat.com>
To: Chris Webb <chris@arachsys.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] qemu-kvm guest which won't 'cont' (emulation failure?)
Date: Mon, 24 Oct 2011 12:42:12 +0200 [thread overview]
Message-ID: <4EA54104.7000001@redhat.com> (raw)
In-Reply-To: <20111024100037.GS9917@arachsys.com>
Am 24.10.2011 12:00, schrieb Chris Webb:
> I have a qemu-kvm guest (apparently a Ubuntu 11.04 x86-64 install) which has
> stopped and refuses to continue:
>
> (qemu) info status
> VM status: paused
> (qemu) cont
> (qemu) info status
> VM status: paused
>
> The host is running linux 2.6.39.2 with qemu-kvm 0.14.1 on 24-core Opteron
> 6176 box, and has nine other 2GB production guests on it running absolutely
> fine.
>
> It's been a while since I've seen one of these. When I last saw a cluster of
> them, they were emulation failures (big real mode instructions, maybe?). I
> also remember a message about abnormal exit in the dmesg previously, but I
> don't have that here. This time, there is no host kernel output at all, just
> the paused guest.
>
> I have qemu monitor access and can even strace the relevant qemu process if
> necessary: is it possible to use this to diagnose what's caused this guest
> to stop, e.g. the unsupported instruction if it's an emulation failure?
Another common cause for stopped VMs are I/O errors, for example writes
to a sparse image when the disk is full.
Kevin
next prev parent reply other threads:[~2011-10-24 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 10:00 [Qemu-devel] qemu-kvm guest which won't 'cont' (emulation failure?) Chris Webb
2011-10-24 10:42 ` Kevin Wolf [this message]
2011-10-24 10:58 ` Chris Webb
2011-10-24 11:18 ` Kevin Wolf
2011-10-24 11:29 ` Chris Webb
2011-10-24 11:36 ` Kevin Wolf
2011-10-24 12:05 ` Chris Webb
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=4EA54104.7000001@redhat.com \
--to=kwolf@redhat.com \
--cc=chris@arachsys.com \
--cc=kvm@vger.kernel.org \
--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).