All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: Success with recent Xen pv_ops dom0 kernel (2.6.29-rc8)
Date: Wed, 25 Mar 2009 11:04:38 -0700	[thread overview]
Message-ID: <49CA7236.4080909@goop.org> (raw)
In-Reply-To: <20090325153405.GC24960@edu.joroinen.fi>

Pasi Kärkkäinen wrote:
> Things that are still broken:
> - dom0 VGA text console doesn't work, only serial console works
>   

OK, Gerd identified a mapping problem that probably explains the lack of 
VGA.  I haven't had a chance to cook up a fix for it yet.

> - CONFIG_HIGHPTE=y crashes the dom0 kernel sooner or later, so I'm running CONFIG_HIGHPTE=n
>   

It's possible this is related.  Well, it would be nice ;)

> Otherwise my setup consists of:
> - Fedora 10 distribution on dom0, latest updates installed
> - libvirt 0.6.1 and related packages from f10 updates-testing (earlier versions had a lot of problems)
> - F11/rawhide Xen 3.3.1-9 packages rebuilt for F10
> - New enough pv_ops dom0 kernel so it has /sys/hypervisor support for libvirt/virt-install/virt-manager
>
> Missing features:
> - blktap (tap:aio). Any plans for this? 
> - PV domU PCI-passthrough? 
>   

Yes, both are planned.  blktap is on a fairly short list (waiting for 
blktap2 to land, rather than waste time on blktap1).

I think a lot of the tricky bits PCI passthrough are already done in the 
form of the rest of the dom0 pci changes, but I haven't looked at 
pciback in detail yet.

    J

      parent reply	other threads:[~2009-03-25 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 15:34 Success with recent Xen pv_ops dom0 kernel (2.6.29-rc8) Pasi Kärkkäinen
2009-03-25 15:37 ` Pasi Kärkkäinen
2009-03-25 17:27 ` Boris Derzhavets
2009-03-25 18:04 ` Jeremy Fitzhardinge [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=49CA7236.4080909@goop.org \
    --to=jeremy@goop.org \
    --cc=pasik@iki.fi \
    --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.