mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Xen-devel] Re: Status of Xen in vanilla?
Date: Mon, 24 Nov 2008 21:13:40 +0200	[thread overview]
Message-ID: <20081124191340.GC15052@edu.joroinen.fi> (raw)
In-Reply-To: <4919D4B1.7080703@goop.org>

On Tue, Nov 11, 2008 at 10:53:37AM -0800, Jeremy Fitzhardinge wrote:
> Maximilian Wilhelm wrote:
> >Hi!
> >
> >I'm wondering about the status of Xen support in the vanilla kernel.
> >I know that DomU support is inside the kernel an evolving, but I did
> >not find an up-to-date hint about the status of Dom0 support.
> >
> >A while ago I read that it should be included in 2.6.28, but I do not
> >find any current pointer about the status of this.
> >  
> 
> .28 was a bit optimistic; .29 seems reasonable.  The current dom0 kernel 
> patches can boot up to a fully functional dom0 usersmode, and you can 
> start xend to see that domain 0 is running.  I *think* in theory you can 
> create a deviceless domain, but I haven't tried it.  I'm currently 
> working on blktap support.
> 
> I really need to put together a proper status update.  Now that dom0 
> usermode is working, its a much better base for other people start 
> contributing.
> 

This reminded me of updating http://wiki.xensource.com/xenwiki/XenParavirtOps

Now it says "Features added in 2.6.27".

Maybe you can go through the page, and update/add missing stuff.. 

-- Pasi

      reply	other threads:[~2008-11-24 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 11:38 Maximilian Wilhelm
2008-11-11 18:53 ` Jeremy Fitzhardinge
2008-11-24 19:13   ` Pasi Kärkkäinen [this message]

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=20081124191340.GC15052@edu.joroinen.fi \
    --to=pasik@iki.fi \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®