I have a virtual machine landscape consisting of a CentOS 5.3 Dom0 with
Xen 3.1.2, some PV CentOS DomU's with PCI passthrough (same versions),
and I'm trying to implement a F10 DomU with PCI passthrough. I set
everything up for the passthrough, and the F10 guest can't see any of
the devices with lspci. If I boot a CentOS PV machine with the same PCI
passthrough configuration, the devices show up with lspci. I've seen
some posts in various places about this issue, but no solutions. How do
I implement this?
I have built a new set of kernel packages based on fedora rawhide
kernels and the xen/dom0/hackery branch of Jeremy's git repository
( http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary ).
This batch (kernel-2.6.29-0.114.2.6.rc6.fc11) is available via the koji
build system at
These are really for development and debugging purposes only, as I am
still having problems getting them to boot, but others have reported more
success at getting kernels based on this git repository working, so you
might be lucky.
Note to install these packages on Fedora 10 you will need to have
rpm-4.6.0-1.fc10 installed (currently in updates-testing but it should be
available in updates soon) because of the change to SHA-256 file digest
hashing in recent Fedora 11 builds.
Kernel 2.6.31-0.203.rc8.git2.fc12.i686.PAE for F12/rawhide domU seems to work
now on my F11 host with xen-3.4.1-3 + libvirt from F11 updates-testing +
2.6.31-rc6 pv_ops dom0 kernel.
There's a minor issue with domU vfb graphical console keymap though..
The F11 host has 'fi' (Finnish) keymap, and the F12 domU/guest is also installed
with 'fi' keymap.
All the 'special' keys on the graphical console (virt-viewer) are broken..
I don't really know what the resulting keymap is, but it's pretty weird.
Not english, not finnish, not anything I know of..
List of the important characters that are broken:
* / - _ | ? \ ( )
Either you can't make them at all, or you have to press totally wrong
buttons to get them.. so the console is really painful or impossible to use.
Any ideas how to debug this? Or is non-US even supposed to work?
Got any release of Fedora-Xen that can support windows on
if I wanna to customized the existing feature, what direction should i go,
to install to or make windows 32bit be able to run stable on bare Fedora-xen
based bare metal machine?
Like kernel, driver over the windows side, any many more, rather than having
a enterprise solution
I still newbie, I would like to have expert advice and opinion to make it be
----- Forwarded message from Jeremy Fitzhardinge <jeremy(a)goop.org> -----
From: Jeremy Fitzhardinge <jeremy(a)goop.org>
To: Xen-devel <xen-devel(a)lists.xensource.com>
Date: Fri, 18 Sep 2009 18:19:41 -0700
Subject: [Xen-devel] Announcing xen/master: pvops git trees rearranged
Well, my current pvops/dom0 tree is finally (reasonably) stable. There
was a fairly nasty bug which ended up corrupting dom0 memory when doing
IO on behalf of domains, but that is finally fixed.
In honour of this, I've renamed the rebase/* branches to xen/* (moving
the old remaining xen/* branches to xen-old/*); xen/master is now the
preferred branch for fetching current dom0 work.
The kernel tree is fairly featureful:
* basic dom0 support
* ACPI power management
* S3 suspend/resume (at least for some people)
* microcode update
* MSI support
In other words, it has as much as it ever has.
There are a few notable missing features:
* pci front/back
* upstream Linux support
* your pet feature
Full coordinates are:
See http://wiki.xensource.com/xenwiki/XenParavirtOps for general
directions on configuration, compilation and use.
This is definitely a work-in-progress kernel. I'd appreciate all bug
*and* success reports so I can get some idea of how many people are
using this thing, and how often there are problems. Patches gratefully
Xen-devel mailing list
----- End forwarded message -----