From: Keir Fraser <keir.fraser@eu.citrix.com>
To: John Levon <levon@movementarian.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: SHUTDOWN_crash and vcpu deferrals
Date: Fri, 20 Feb 2009 21:35:16 +0000 [thread overview]
Message-ID: <C5C4D294.3310%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20090220210155.GA5872@movementarian.org>
On 20/02/2009 21:01, "John Levon" <levon@movementarian.org> wrote:
> If an HVM guest is waiting for an ioemu assist, when qemu isn't running, and
> domain_shutdown(SHUTDOWN_crash) is called, then the domain isn't crashed
> properly:
>
> Nothing will ever end the deferral. I added code to bust through the
> deferral if SHUTDOWN_crash was the reason, and it seemed to help, but
> I'm not sure it's the right fix.
Hm. If qemu is down you're kind of screwed anyway. Even a non-crashed guest
will likely hang. If you care about that eventuality (i.e., you believe qemu
problems are possible/likely and need to detect them, defend against them,
or whatever), would it be better to have tools try to detect it through
keepalives or something, and basically tackle that class of problem head on?
If you want the hack, I think what you're doing is probably about right. I'd
have to go back over that code again to be exactly sure though, since it's a
bit subtle.
Personally I think a dead qemu is pretty bad, and bugs leading to such
should simply be found and fixed (oh for a perfect world :-). That bad
things happen to a guest, like SHUTDOWN_crash hanging, after qemu is dead...
I'd just live with that -- a worse thing has *already* happened to that
guest's virtualisation environment.
-- Keir
next prev parent reply other threads:[~2009-02-20 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 21:01 SHUTDOWN_crash and vcpu deferrals John Levon
2009-02-20 21:35 ` Keir Fraser [this message]
2009-02-20 22:03 ` John Levon
2009-02-21 9:01 ` Keir Fraser
2009-02-23 16:51 ` Ian Jackson
2009-02-23 16:54 ` John Levon
2009-02-23 16:58 ` Ian Jackson
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=C5C4D294.3310%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=levon@movementarian.org \
--cc=xen-devel@lists.xensource.com \
/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.