From: David Vrabel <dvrabel@cantab.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xensource.com,
Mukesh Rathor <mukesh.rathor@oracle.com>,
JBeulich@suse.com
Subject: Re: Xen 4.1 + Linux compiled with PVH == BOOM
Date: Tue, 24 Dec 2013 12:31:17 +0000 [thread overview]
Message-ID: <52B97E95.9060900@cantab.net> (raw)
In-Reply-To: <20131220175735.GA619@phenom.dumpdata.com>
On 20/12/2013 17:57, Konrad Rzeszutek Wilk wrote:
> Hey,
>
> This is with Linux and
>
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/pvh.v11
>
> I get Xen 4.1 (only) hypervisor to blow up with a Linux kernel that has been
> compiled with PVH.
>
> I think the same problem would show up if I tried to launch a PV guest
> compiled as PVH under Xen 4.1 as well - as the ELF parsing code is shared
> with the toolstack.
If a kernel with both PVH and PV support enabled cannot boot in PV mode
with a non-PVH aware hypervisor/toolstack then the kernel is broken.
Hypervisor/tool-side fixes aren't the correct fix here. Xen 4.1 and
even older are still widely deployed.
David
next prev parent reply other threads:[~2013-12-24 12:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 17:57 Xen 4.1 + Linux compiled with PVH == BOOM Konrad Rzeszutek Wilk
2013-12-21 1:47 ` Mukesh Rathor
2013-12-21 11:09 ` Ian Campbell
2013-12-21 16:17 ` Konrad Rzeszutek Wilk
2013-12-23 9:37 ` Jan Beulich
2013-12-23 11:49 ` Jan Beulich
2013-12-24 1:56 ` Konrad Rzeszutek Wilk
2014-01-07 8:23 ` Jan Beulich
2014-01-07 11:31 ` Ian Campbell
2014-01-07 11:50 ` Jan Beulich
2014-01-07 13:39 ` Ian Campbell
2013-12-24 12:31 ` David Vrabel [this message]
2013-12-24 12:55 ` Andrew Cooper
2013-12-24 13:05 ` David Vrabel
2013-12-30 19:56 ` Konrad Rzeszutek Wilk
2014-01-02 19:30 ` Konrad Rzeszutek Wilk
2014-01-02 21:23 ` Konrad Rzeszutek Wilk
2014-01-03 12:40 ` Roger Pau Monné
2014-01-03 14:35 ` Konrad Rzeszutek Wilk
2014-01-03 0:27 ` Mukesh Rathor
2014-01-06 11:01 ` Ian Campbell
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=52B97E95.9060900@cantab.net \
--to=dvrabel@cantab.net \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=mukesh.rathor@oracle.com \
--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.