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, 7 months
Dom0 to rawhide?
by W. Michael Petullo
I have been using Michael Young's Xen Dom0 kernels. With kernel 2.6.34
in Rawhide, what is keeping Xen 4.0 and a DomU kernel from being pushed
to Rawhide? My understanding was that kernel 2.6.33 would provide the
pvops features required to make a Dom0 kernel palatable to Fedora. Did
this feature not make this release?
http://fedoraproject.org/wiki/Features/XenPvopsDom0 has not been updated
in a while, but I suspect that a Xen Dom0 kernel will not be in Fedora 13.
--
Mike
:wq
12 years, 9 months
kernel-2.6.32.10-1.2.92.xendom0.fc12.x86_64 X broken on MacBook
by W. Michael Petullo
I just tried kernel-2.6.32.10-1.2.92.xendom0.fc12.x86_64 from Mike
Young's repository on my MacBook and found that the video driver does
not seem to work. Lspci reports:
02:00.0 VGA compatible controller: nVidia Corporation GeForce 9400M (rev b1)
The system boots fine until X is supposed to start. Once this happens,
the console freezes. Otherwise, the system continues to operate and
respond to network traffic.
The last thing I seen in Xorg.0.log is "(II) NOUVEAU(0): Opened GPU
channel 2." In a *working* configuration, the next message logged is
"(II) NOUVEAU(0): [DRI2] Setup complete."
There seems to be some related work here:
http://lists.xensource.com/archives/html/xen-devel/2010-02/msg01105.html
I have seen that other people are having some video problems and wanted
to add my own (on the mailing list until we are in Rawhide / Bugzilla).
--
Mike
:wq
13 years, 2 months
Fedora 12 Xen guests (domU) and hosts (dom0)
by Pasi Kärkkäinen
Hello,
I thought of writing some information about running Fedora 12 Xen guests
and also Fedora 12 Xen hosts/dom0.
Fedora 12 includes the upstream Linux pv_ops Xen domU support in the default kernel.
By using virt-install or virt-manager you can install Fedora 12 Xen PV
(paravirtual) guests directly from network, for example on RHEL 5.4,
CentOS 5.4, or Fedora Xen dom0/host.
If you want to run Fedora 12 Xen dom0 (host), there are some extra steps
needed. Fedora 12 ships with Xen hypervisor and management tools
(Xen 3.4.1, and Xen 3.4.2 in the F12 updates), but the required Xen dom0
capable host kernel is not included in Fedora atm/yet.
General information about Xen dom0 status in Fedora:
http://fedoraproject.org/wiki/Features/XenPvopsDom0
There are a couple of different ways to get and install a Xen dom0
capable kernel to Fedora 12 host:
- By using pre-packaged pv_ops xendom0 kernel rpms by M A Young. his repository:
http://fedorapeople.org/~myoung/dom0/
- Compiling and installing Xen dom0 capable kernel yourself/manually.
There are many options to choose from, full list of the available Xen
dom0 capable kernels is here:
http://wiki.xensource.com/xenwiki/XenDom0Kernels
The recommended dom0 kernel is the pv_ops kernel, which is in the
process of being cleaned up for upstream/mainline Linux inclusion.
More information about pv_ops dom0 kernel, including the status
reports:
http://wiki.xensource.com/xenwiki/XenParavirtOps
Xen developers are interested of both the success and failure reports
when using the Xen pv_ops dom0 kernel.
Tips for running Xen with Fedora 12:
- Make sure you install all the latest Fedora 12 updates, since they
have an updated Xen version (3.4.2), and also fix a bug in
python-virtinst tool to make Xen guest console keymaps work properly:
https://bugzilla.redhat.com/show_bug.cgi?id=533707
- Recent versions of Xen pv_ops dom0 kernel renamed some xen
backend driver modules to have "xen-" prefix in them, for
example evtchn module became xen-evtchn. Fedora Xen 3.4.2 init
scripts take care of this, and load the correct modules, but
Xen 3.4.1 doesn't do this automatically, causing xend fail to
start in dom0/host before the modules are loaded manually.
- There are some upcoming apic-related changes coming in pv_ops
dom0 kernel, which will require a patch to Xen hypervisor.
This patch is not yet included in the Fedora Xen rpms.
The patch will be added to Fedora Xen rpms when the upstream
pv_ops kernel starts to require/use it.
- pv_ops dom0 kernel currently lacks blktap2 support, so using
tap:aio: backend disk image files is not yet possible.
Xen file: backend image files work though.
At the moment it's recommended to use LVM volumes for guest
disks (Xen phy: backend).
- virt-manager seems to work OK on Fedora 12 Xen dom0.
- If you experience problems related to Fedora 12 guests (domU)
kernel crashing (especially related to save/restore/migration),
install the latest Fedora updates to the guest. There has been
a lot of Xen guest related fixes in the upstream Linux recently.
These fixes will appear in Fedora when the kernel gets updated
to include the latest stable upstream fixes.
Hopefully that helps :)
-- Pasi
13 years, 2 months
blktap driver for xen-dom0
by 서지혜
I installed xen 3.4.1 & M.young's xendom0 kernel on fedora 12 beta.
Everying works smoothly for me except that I can't use "tap:aio" for PV
guest.
It seems that blktap driver is not installed (not supported) on dom0 kernel.
I think performance of guest OS is better when is mounted by blktap. Is
there anyway I can use this option?
13 years, 2 months
Non-PAE Dom0 kernel for running Ethos
by W. Michael Petullo
I am trying trying to run a research OS named Ethos as a DomU
paravirtualized guest. Ethos does not yet support 64-bit or PAE, so I
need to build a non-PAE Dom0 kernel. I am having trouble doing this. Here
is what I tried:
1. Edit Michael Young's kernel.spec as follows:
# kernel-PAE is only built on i686.
%ifarch i686
%define with_pae 0
%define with_up 1
%else
%define with_pae 0
%endif
2. Build an RPM using "rpmbuild -ba --target i686 --with xen --without
debuginfo kernel.spec."
When try to boot my Dom0 kernel, Xen complains:
(XEN) elf_xen_note_check: ERROR: Will only load images build for the
generic loader or Linux images
Do I need to recompile Xen to go non-PAE?
See also https://bugzilla.redhat.com/show_bug.cgi?id=543190, unable to
build custom i686 non-pae kernel.
--
Mike
:wq
13 years, 2 months
no xen/xen.h in -devel
by Jerry Amundson
could/should kernel-PAE-devel have xen/?
no love trying to build a kernel module against it...
make -C /lib/modules/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE/build
SUBDIRS=/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd modules
make[2]: Entering directory
`/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE'
CC [M] /home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_buildtag.o
CC [M] /home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_bitmap.o
CC [M] /home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_proc.o
In file included from include/linux/scatterlist.h:8,
from include/linux/dma-mapping.h:7,
from include/linux/dmaengine.h:26,
from include/linux/skbuff.h:30,
from include/linux/if_ether.h:124,
from include/linux/netdevice.h:29,
from include/net/sock.h:50,
from include/linux/connector.h:80,
from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/linux/drbd.h:29,
from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_buildtag.c:2:
/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE/arch/x86/include/asm/io.h:10:21:
error: xen/xen.h: No such file or directory
In file included from include/linux/scatterlist.h:8,
from include/linux/dma-mapping.h:7,
from include/linux/dmaengine.h:26,
from include/linux/skbuff.h:30,
from include/linux/if_ether.h:124,
from include/linux/netdevice.h:29,
from include/net/sock.h:50,
from include/linux/connector.h:80,
from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/linux/drbd.h:29,
from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_bitmap.c:28:
/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE/arch/x86/include/asm/io.h:10:21:
error: xen/xen.h: No such file or directory
In file included from include/linux/scatterlist.h:8,
from include/linux/dma-mapping.h:7,
from include/linux/dmaengine.h:26,
from include/linux/skbuff.h:30,
from include/linux/if_ether.h:124,
from include/linux/netdevice.h:29,
from include/net/sock.h:50,
from include/linux/connector.h:80,
from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/linux/drbd.h:29,
from /home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_proc.c:35:
/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE/arch/x86/include/asm/io.h:10:21:
error: xen/xen.h: No such file or directory
make[3]: *** [/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_buildtag.o]
Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: *** [/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_proc.o] Error 1
make[3]: *** [/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_bitmap.o] Error 1
make[2]: *** [_module_/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd] Error 2
make[2]: Leaving directory
`/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE'
make[1]: *** [kbuild] Error 2
make[1]: Leaving directory `/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd'
make: *** [module] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.e3hCch (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.e3hCch (%build)
13 years, 2 months
