From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: PVHVM drivers in upstream linux kernel
Date: Tue, 2 Dec 2014 12:04:56 -0500 [thread overview]
Message-ID: <20141202170456.GB31436@laptop.dumpdata.com> (raw)
In-Reply-To: <1417533208.24320.55.camel@citrix.com>
On Tue, Dec 02, 2014 at 03:13:28PM +0000, Ian Campbell wrote:
> On Tue, 2014-12-02 at 10:11 -0500, Konrad Rzeszutek Wilk wrote:
> > > [0] The default i386 Debian installer falls into this camp, but you can
> > > use the special PV Xen variant to install as PVHVM too so it's not so
> > > critical.
> >
> > And the Fedora 21 LiveISO (32-bit) does too.
>
> Interesting, I thought Fedora had switched to requiring PAE as a minimum
> baseline everywhere
It did, except for the GNOME based LiveCD. And oddly enough it will install
an PAE kernel (since the CPU is capable of it) . But of course it won't
bundle the Xen drivers in the initramfs, so when the new OS boots it
keels over as it unplugs the emulated ones.
>
> Ian.
>
next prev parent reply other threads:[~2014-12-02 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 9:39 PVHVM drivers in upstream linux kernel Juergen Gross
2014-12-02 10:54 ` David Vrabel
2014-12-02 11:02 ` Juergen Gross
2014-12-02 11:05 ` Ian Campbell
2014-12-02 11:33 ` Juergen Gross
2014-12-02 11:36 ` Ian Campbell
2014-12-02 11:39 ` Juergen Gross
2014-12-02 11:59 ` David Vrabel
2014-12-02 13:00 ` Juergen Gross
2014-12-02 14:09 ` David Vrabel
2014-12-02 14:35 ` Juergen Gross
2014-12-02 15:11 ` Konrad Rzeszutek Wilk
2014-12-02 15:13 ` Ian Campbell
2014-12-02 17:04 ` Konrad Rzeszutek Wilk [this message]
2014-12-02 15:10 ` 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=20141202170456.GB31436@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.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.