xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/3] xen/pv-on-hvm kexec: add quirk for Xen 3.4 and shutdown watches.
Date: Wed, 10 Oct 2012 20:09:56 +0200	[thread overview]
Message-ID: <20121010180956.GA2130@aepfle.de> (raw)
In-Reply-To: <1349890849-17471-2-git-send-email-konrad.wilk@oracle.com>

On Wed, Oct 10, Konrad Rzeszutek Wilk wrote:

> The commit 254d1a3f02ebc10ccc6e4903394d8d3f484f715e, titled
> "xen/pv-on-hvm kexec: shutdown watches from old kernel" assumes that the
> XenBus backend can deal with reading of values from:
>  "control/platform-feature-xs_reset_watches":
> 
>     ... a patch for xenstored is required so that it
>     accepts the XS_RESET_WATCHES request from a client (see changeset
>     23839:42a45baf037d in xen-unstable.hg). Without the patch for xenstored
>     the registration of watches will fail and some features of a PVonHVM
>     guest are not available. The guest is still able to boot, but repeated
>     kexec boots will fail."
> 
> Sadly this is not true when using a Xen 3.4 hypervisor and booting a PVHVM
> guest. We end up hanging at:

This is sad.
So far I have not seen reports like that with a sles11sp1 or sles11sp2
guest. Thats either because noone uses Xen 3.4+sles11 (or recent
openSuSE) HVM guests, or because it happens to work with that
combination.

If the patch solves the issue:

Acked-by: Olaf Hering <olaf@aepfle.de>

Olaf

  reply	other threads:[~2012-10-10 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 17:40 [PATCH v1] Various bug-fixes for v3.6 Konrad Rzeszutek Wilk
2012-10-10 17:40 ` [PATCH 1/3] xen/pv-on-hvm kexec: add quirk for Xen 3.4 and shutdown watches Konrad Rzeszutek Wilk
2012-10-10 18:09   ` Olaf Hering [this message]
2012-10-15 16:05   ` [Xen-devel] " Ian Campbell
2012-10-15 16:14     ` Ian Campbell
2012-10-15 16:09       ` Konrad Rzeszutek Wilk
2012-10-10 17:40 ` [PATCH 2/3] xen/bootup: allow {read|write}_cr8 pvops call Konrad Rzeszutek Wilk
2012-10-10 17:40 ` [PATCH 3/3] xen/bootup: allow read_tscp call for Xen PV guests Konrad Rzeszutek Wilk

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=20121010180956.GA2130@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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 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).