No pcifront in F10?
by Jim Lutz
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?
12 years, 11 months
Dom0 kernels
by M A Young
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
http://koji.fedoraproject.org/koji/taskinfo?taskID=1149500
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.
Michael Young
13 years, 6 months
Success with Fedora 10 Xen pv_ops 2.6.29-rc8 dom0
by Pasi Kärkkäinen
Hello!
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
working.
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
dom0 kernel).
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.
Issues:
- 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!
-- Pasi
14 years, 2 months
Xenner, Ok, who has used it and can somebody provide a syntax example / real example?
by Lester M.
Xenner, yes xenner...
Ok, who has used it and can somebody provide a syntax example / real
example?
Did the google / yahoo / <insert default search engine here> search, I would
like to see an example, as well as hear of everyone's experiences using
xenner, while we wait for a more stable native dom0 / upstream support for
xen.
Any takers? :-)
14 years, 2 months
Re: [Fedora-xen] Dom0 kernels
by Caz Yokoyama
Hello Michael,
Have you ever observed garbled xdm screen like the pictures in
http://www.caztech.com/xen/OnFedora11/*.jpg? I installed your binary rpms on
Fedora 11 x86_64. Everything seems fine except for X server. I copied
console log of xen and x server log the in the same directory of pictures.
How do you debug this problem if you have this problem? I am glad to provide
you more information if you want.
Thank you.
-Caz Yokoyama, caz at caztech dot com. 503-804-1028(m).
Date: Thu, 16 Jul 2009 23:50:07 +0100 (BST)
From: M A Young <m.a.young(a)durham.ac.uk>
Subject: Re: [Fedora-xen] Dom0 kernels
To: fedora-xen(a)redhat.com, fedora-virt(a)redhat.com
Message-ID: <alpine.LFD.2.00.0907162345140.4505(a)vega1.dur.ac.uk>
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
And another update (kernel-2.6.31-0.1.2.43.rc3..xendom0.fc12) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=1477549 and the
repository http://fedorapeople.org/~myoung/dom0/ . There have been some acpi
and xenbus patches, but i686 still doesn't work for me.
Michael Young
14 years, 2 months
xenbr0 failure when changing motherboard
by Evan Lavelle
I've just asked this on the xen list, but I suspect it may be an
aliasing problem on Fedora 8, so I though I'd ask here.
I have a production system (ie. I can't upgrade it) which has an F8 Dom0
with various DomU's (the Dom0 is kernel 2.6.21-2952, with Xen
3.0-x86_64). I needed to change the motherboard, so I just moved the
drive to a new motherboard.
Amazingly, everything works, apart from one problem. I had to change the
guest configs to use virbr0 rather than zenbr0 (in the vif line in the
old-style config file).
The problem with virbr0 is that I've now got a local subnet; the domU's
can see out, but I can't see into the DomU's from the network. The
previous (xenbr0) setup was that the DomU's got an IP address from an
external hardware router, and everything was on the same 196.168.1 subnet.
Now, I could presumably fix this through a libvirt setup, but I want to
change as little as possible, and the DomU's don't currently use libvirt
configuration files. So, if possible, I'd like to go back to the xenbr0
setup.
When I try to boot with a xenbr0 setup, I get:
> Error: Device 0 (vif) could not be connected. Could not find bridge device xenbr0.
What I think has happened is that the existing fc8-xen on my hard drive
is confused about the network hardware on the new motherboard (a Dell
R200 server). When the new board originally booted up, networking was
disabled, but I fixed this by aliasing eth0 to eth3. The (old) driver
seemed to have identified the new NICs at eth3 and eth4, rather than
eth0/1. Anyway, that fixed the network on Dom0, but it seems to be
giving Xen a headache when it boots any DomU's.
I know that F8 had problems in the network-bridge script related to
aliasing, but network-bridge runs without producing errors, so I'm not
convinced that that's the problem here.
Any thoughts?
Thanks -
Evan
14 years, 2 months
Configuring Xen on FC10
by Samir Selman
Hi,
I am working at Stanford on a research project and I have installed Fedora
Core 10. Can someone help me on what are the steps to configure Xen on FC10.
Thanks
14 years, 2 months
kernel compiling problem
by naveed iqbal
AOA Everyone,
I am try to compile the linux kernel 2.6.18 with xen-3.4 evrything going fine but when i am trying to run the mkinitrd command to create the .img file then the error comes there is no pata_serverworks module.Please guide me as soon as possible how to resolve this problem.
Regards,
Naveed Iqbal
14 years, 2 months
