From: Chris Webb <chris@arachsys.com>
To: Kevin Wolf <kwolf@redhat.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 11:58:27 +0100 [thread overview]
Message-ID: <20111024105826.GT9917@arachsys.com> (raw)
In-Reply-To: <4EA54104.7000001@redhat.com>
Kevin Wolf <kwolf@redhat.com> writes:
> Am 24.10.2011 12:00, schrieb Chris Webb:
> > 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.
This guest are backed by LVM LVs so I don't think they can return EFULL, but I
could imagine read errors, so I've just done a trivial test to make sure I can
read them end-to-end:
0015# dd if=/dev/mapper/guest\:e549f8e1-4c0e-4dea-826a-e4b877282c07\:ide\:0\:0 of=/dev/null bs=1M
3136+0 records in
3136+0 records out
3288334336 bytes (3.3 GB) copied, 20.898 s, 157 MB/s
0015# dd if=/dev/mapper/guest\:e549f8e1-4c0e-4dea-826a-e4b877282c07\:ide\:0\:1 of=/dev/null bs=1M
276+0 records in
276+0 records out
289406976 bytes (289 MB) copied, 1.85218 s, 156 MB/s
Is there any way to ask qemu why a guest has stopped, so I can distinguish IO
problems from emulation problems from anything else?
Cheers,
Chris.
next prev parent reply other threads:[~2011-10-24 10:58 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
2011-10-24 10:58 ` Chris Webb [this message]
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=20111024105826.GT9917@arachsys.com \
--to=chris@arachsys.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--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).