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.
I've used a lot of time trying to get my custom Xen pv_ops dom0 kernel working with
virt-install and/or virt-manager on Fedora 10, and now it seems I got things
If you want to play with this you need:
1) New enough pv_ops dom0 kernel (2.6.29-rc8 or newer) so it has /sys/hypervisor support included
- Compile with CONFIG_HIGHPTE=n since it seems to be broken still
2) libvirt 0.6.1 and related packages from Fedora 10 updates-testing
In addition to those I'm using Xen 3.3.1-9 packages from rawhide/F11 rebuilt for F10.
With the older Fedora 10 libvirt packages libvirtd was crashing often for me, and
I had some other issues with virt-install console window not opening but stalling etc..
Today I was able to run the following on Fedora 10 32bit PAE pv_ops dom0:
- CentOS 5.3 32bit PAE PV domU
- Fedora 10 32bit PAE PV domU
- Use virt-install to install Fedora 10 32bit PAE PV domU (using custom kickstart
to force PAE kernel installation to avoid the anaconda BUG which installs
wrong non-PAE kernel as a default).
Fedora 11 (rawhide) installation most probably works too.
I'm using LVM volumes for domU disks (tap:aio is not yet supported by pv_ops
Network seems to work after running "ifdown eth0 && ifup eth0"
on the guest.. dunno why that's needed. That's something to figure out later:)
Graphical domU console works with virt-viewer and virt-install during installation.
- virt-manager complains about default network (virbr0) being inactive and
asks if I want to start it. If I click Yes, then I get error: "libvirtError: cannot create bridge 'virbr0': File exists"
virbr0 works just fine with virt-install. So dunno what's the problem with that..
have to look into that later.
Thanks to everyone involved for helping me with this!
Has anyone experienced network trouble with F11 xen paravirt guests?
I'm running centos 5.2 with a newer virttest kernel. During anaconda
install it seems like it just gives up trying to download packages. Hit
"retry" and on it goes.
Seems like it may be IPv6/DNS/arp related. Last traffic I see from the
guest is a DNS request followed by an arp request:
10:39:15.400256 IP 192.168.0.152.48599 > 192.168.0.8.domain: 39049+
AAAA? fedora.cora.nwra.com. (38)
10:39:15.401002 IP 192.168.0.8.domain > 192.168.0.152.48599: 39049*
10:39:15.401364 IP 192.168.0.152.51996 > 192.168.0.8.domain: 38381+ A?
10:39:15.402118 IP 192.168.0.8.domain > 192.168.0.152.51996: 38381*
10:39:18.315280 arp who-has 192.168.0.8 tell 192.168.0.152
10:39:18.315302 arp reply 192.168.0.8 is-at 00:06:5b:3f:72:c2
10:41:59.317998 IP 192.168.0.152.39309 > 192.168.0.8.domain: 30991+
AAAA? fedora.cora.nwra.com. (38)
10:41:59.318392 IP 192.168.0.8.domain > 192.168.0.152.39309: 30991*
10:41:59.318671 IP 192.168.0.152.55043 > 192.168.0.8.domain: 51670+ A?
10:41:59.319105 IP 192.168.0.8.domain > 192.168.0.152.55043: 51670*
10:42:01.056915 arp who-has 192.168.0.152 tell 192.168.0.8
10:42:01.057115 arp reply 192.168.0.152 is-at 40:00:00:00:00:03
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
I'm a German student, writing my thesis on "Virtualization with Xen.
Analysis and Comparision of Different Techniques such as
Paravirtualization, Full Virtualization, and Utilization of Hardware
Support Provided by the Processor".
I'd like to know how I can disable HAP/RVI/Nested Paging for
benchmarking purposes. I read somewhere
(http://markmail.org/message/bbnivuqx6vjz7jg4) that Xen developers
decided to disable the global grub parameter introducing a per domain
flag for HAP instead (hap=0/1).
I used virt-manager built in CentOS for setting up all domUs;
virt-manager uses libvirt so that no "old-style" configuration files are
stored in /etc/xen. I actually don't know how if libvirt-XML-files
already support something like <hap>0</hap>. How would you proceed to
modify an already existing domain using libvirt/virt-manager?
I really do apologize for my "newbie ignorance". Thanks in advance for
any useful help.
I'm using Fedora 10 on my Xen pv_ops testing box.
I rebuilt Xen 3.3.1-9 packages from F11/rawhide for Fedora 10 and installed them.
I also built custom 2.6.29-rc7 pv_ops dom0 kernel, which seems to boot OK
xend starts OK, and I can run 'xm info', 'xm list' etc.
But now I'm having problems using virt-install and/or virt-manager to
install new domains.
[root@dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l
ERROR Unsupported virtualization type 'xen'
Has Xen support been dropped from virt-install, or is this just some bug?
I've been browsing the web for I've been having the same issue you
describe in the email attached below... Have you made any progress?
I've been able to install F10 on RHEL 5.3 but only has an HVM. Now I'm
trying to switch it to paravirt and no luck. It just doesn't even start
booting. Creating an empty shell and telling it to use F10 initrd and
kernel yields the same result.
I should get more time to investigate this week but I was wondering if
you figured it out?
> On Fri, 13 Feb 2009, Mike McGrath wrote:
> > On Fri, 13 Feb 2009, Mark McLoughlin wrote:
> > On Thu, 2009-02-12 at 21:21 +0100, Olivier Renault wrote:
> > > There is no xen kernel within F10 so you will need to install it as
> > > a
> > > FV VM.
> > Yes, there is - the bare-metal kernel has pv_ops Xen support. You may
> > have been bitten by this bug, though:
> > https://bugzilla.redhat.com/470905
> > anaconda installs the wrong kernel for i686 xen guests.
> Its not even getting to stage 2 during install I'm afraid.
Mathieu Chouquet-Stringer mchouque(a)free.fr
The sun itself sees not till heaven clears.
-- William Shakespeare --
I have a VM installed in Fedora 10 with the virt-manager
great! I love the fact I can mount disks so guest and host can both see
But..I created it with 1-2GB ram (from my total 4), and it defaults to 1GB.
That works. If I increase it to 2 I start to see weird crashes in the host.
How can I migrate this system to having always 2GB please?
I am having trouble with Realtek 8139 NIC on ia64 HVM guest with Windows
2003 SP1 - I can not install a valid ia64 driver (none available), and vif=[
... model=ne2k_pci|pcnet|whatever ... ] does not seem tho change anything
... I feel desperate now. This had to work in order to make proof of concept
in my company (Hemofarm, STADA) for RHEL 5.3 as an Itanium virtualization
platform. Now I feel exhausted, hours of work are gone leaving me with only
one step left unfinished - network access for Windows guest ... please,
please, help ! This would lead at least to a more serious support agreement
with Red Hat ...
My temporary RHN subscription is 1170505.
We have a regional support center, this might also lead me to a solution ?
I am a bit confused about the configuration files for XEN user domains
in Fedora. Regarding to the Users’ Manual
for Xen v3.3 from xensource the configuration files should still be in
/etc/xen/ like they are on RHEL5. However, on F8 they are somewhere in
/var/lib/xen and have a new format (not XML?). Could someone please
provide a link to a changelog, release notes or any other "official"
documentation which describes this change? I could not really find an
answer on http://fedoraproject.org/wiki/Docs/Fedora8VirtQuickStart,
and I see that many users ask this questions in other boards or