From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: boris.ostrovsky@oracle.com, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] xen/manage: Poweroff forcefully if user-space is not yet up.
Date: Mon, 7 Apr 2014 13:25:52 -0400 [thread overview]
Message-ID: <20140407172552.GA3718@phenom.dumpdata.com> (raw)
In-Reply-To: <5342DE24.8080804@citrix.com>
On Mon, Apr 07, 2014 at 06:19:32PM +0100, David Vrabel wrote:
> On 04/04/14 19:53, Konrad Rzeszutek Wilk wrote:
> > The user can launch the guest in this sequence:
> >
> > xl create -p /vm.cfg [launch, but pause it]
> > xl shutdown latest [sets control/shutdown=poweroff]
> > xl unpause latest
> > xl console latest [and see that the guest has completely
> > ignored the shutdown request]
> >
> > In reality the guest hasn't ignored it. It registers a watch
> > and gets a notification that there is value. It then calls
> > the shutdown_handler which ends up calling orderly_shutdown.
> >
> > Unfortunately that is so early in the bootup that there
> > are no user-space. Which means that the orderly_shutdown fails.
> > But since the force flag was set to false it continues on without
> > reporting.
> >
> > What we really want to is to use the force when we are in the
> > SYSTEM_BOOTING state and not use the 'force' when SYSTEM_RUNNING.
> >
> > However, if we are in the running state - and the shutdown command
> > has been given before the user-space has been setup, there is nothing
> > we can do. Worst yet, we stop ignoring the 'xl shutdown' requests!
> >
> > As such, the other part of this patch is to only stop ignoring
> > the 'xl shutdown' when we are truly in the power off sequence.
> >
> > That means the user can do multiple 'xl shutdown' and we will try
> > to act on them instead of ignoring them.
>
> Applied to devel/for-linus-3.15
>
> > Fixes-Bug: http://bugs.xenproject.org/xen/bug/6
> > Reported-by: Alex Bligh <alex@alex.org.uk>
> > Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > [v2: Add switch statement]
> > [v3: Add a reboot notifier]
>
> Can you put this version information after the --- in future?
Aye.
>
> Thanks.
>
> David
next prev parent reply other threads:[~2014-04-07 17:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 18:53 [PATCH] Bug-fixes for 3.15 related to 'xl shutdown' and hanging the initial domain reboot Konrad Rzeszutek Wilk
2014-04-04 18:53 ` [PATCH 1/2] xen/xenbus: Avoid synchronous wait on XenBus stalling shutdown/restart Konrad Rzeszutek Wilk
2014-04-04 20:35 ` Boris Ostrovsky
2014-04-04 20:50 ` Konrad Rzeszutek Wilk
2014-04-04 20:50 ` Konrad Rzeszutek Wilk
2014-04-04 20:35 ` Boris Ostrovsky
2014-04-07 17:17 ` David Vrabel
2014-04-07 17:17 ` David Vrabel
2014-04-04 18:53 ` Konrad Rzeszutek Wilk
2014-04-04 18:53 ` [PATCH 2/2] xen/manage: Poweroff forcefully if user-space is not yet up Konrad Rzeszutek Wilk
2014-04-04 18:53 ` Konrad Rzeszutek Wilk
2014-04-07 17:19 ` David Vrabel
2014-04-07 17:25 ` Konrad Rzeszutek Wilk [this message]
2014-04-07 17:25 ` Konrad Rzeszutek Wilk
2014-04-07 17:19 ` David Vrabel
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=20140407172552.GA3718@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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.