From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Michael Abd-El-Malek <mabdelmalek@cmu.edu>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: Vanilla Linux 64-bit paravirt guest support
Date: Thu, 10 Apr 2008 09:01:26 -0500 [thread overview]
Message-ID: <47FE1DB6.6050707@goop.org> (raw)
In-Reply-To: <47FD942C.5040503@cmu.edu>
Michael Abd-El-Malek wrote:
> Is 64-bit domU support available anywhere at the moment? For example,
> what is the status of the git://git.et.redhat.com/xen-pvops-64.git
> tree? I pulled that tree and tried building 64-bit Xen domU support
> (since this tree allows you to configure the kernel with that
> capability, unlike the vanilla Linux tree). But compilation failed in
> enlighten.c because xen_smp_ops isn't defined in x86_64.
Redhat have some patches which they're shipping in Fedora 9. Once F9 is
out the door, I'm hoping they'll polish them into an upstreamable form.
I don't know whether that git tree represents what's in F9, or if that's
somewhere else; at the very least I'd expect you'd be able to pull the
patches out of the srpm.
>>> On a related note: is it possible to compile the PV network/block
>>> drivers for a HVM Linux guest with the newest kernels? Compilation
>>> failed and a previous message on the list says that you can't do
>>> that. The reason I'd want to do this is to let me run a 64-bit
>>> recent Linux kernel with PV drivers.
>>
>> No, we don't support that for the moment, though it would be a useful
>> thing to have.
>
> Is there a reason this wouldn't work, or is it just "scripting
> changes" that need to be done?
In order to simplify the initial upstreaming work, I removed the support
for pv-in-hvm, since it adds a moderate amount of extra complexity.
We'd need to put that back in - it shouldn't be too hard, but it hasn't
been a priority so far.
J
next prev parent reply other threads:[~2008-04-10 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 4:20 Vanilla Linux 64-bit paravirt guest support Michael Abd-El-Malek
2008-04-08 21:29 ` Jeremy Fitzhardinge
2008-04-10 4:14 ` Michael Abd-El-Malek
2008-04-10 14:01 ` Jeremy Fitzhardinge [this message]
2008-04-10 14:11 ` Mark McLoughlin
2008-04-10 14:25 ` Jeremy Fitzhardinge
2008-04-10 14:40 ` Mark McLoughlin
2008-04-10 15:04 ` Jeremy Fitzhardinge
2008-04-19 15:11 ` Bastian Blank
2008-04-10 14:32 ` Michael Abd-El-Malek
2008-04-10 14:49 ` Mark McLoughlin
2008-04-10 14:57 ` Jeremy Fitzhardinge
2008-04-10 15:06 ` Fix a typo in p2m.c Huang2, Wei
2008-04-10 15:14 ` Vanilla Linux 64-bit paravirt guest support Michael Abd-El-Malek
2008-04-10 15:40 ` Jeremy Fitzhardinge
2008-05-06 16:22 ` Mark McLoughlin
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=47FE1DB6.6050707@goop.org \
--to=jeremy@goop.org \
--cc=ehabkost@redhat.com \
--cc=mabdelmalek@cmu.edu \
--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.