Atsushi-san,
I tried to re compile the kernel but I ran into problems. In other words, I
could not make it work. So I reverted back to the idea of loading the kernel
xen0 in the domU instead of compiling a new version of xenU.
I think I was able to pass the pci and usb to the domU by doing the
following:
1) dom0: install a guest with xenguest-install.py.
2) dom0: Start the guest and log in the guest.
3) domU: Then install kernel-xen0 "yum install xen kernel-xen0".
4) domU: Still in the guest, create a initrd file "mkinitrd --with=xennet
--preload=xenblk /boot/initrd-2.6.17-1.2187_FC5xen0-test.img
2.6.17-1.2187_FC5xen0" as explained in
http://wiki.xensource.com/xenwiki/Fedora5Xen0DomU.
Once this file is created, modify the guest /etc/grub.conf xen0 initrd entry
with the file that was newly created.
5) dom0: Modify /etc/modprobe.conf in dom0 as described in
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module
option 2)
6) dom0: The configuration file of the domU uses the option
bootloader="/usr/bin/pygrub" (no kernel parameter, no ramdisk parameter) and
specifies the parameter "pci = [ <add the lsusb or lspci values> ]".
7) domU: Reload the dom0 and select the xen0 kernel. The usb and pci should
be seen in the domU
I have not tested the devices but at least they are now showing up in the
guest domain when I do a lspci or lsusb. Also, I made a lot of changes
trying to make this work so hopefully, the steps above are complete and
accurate.
Best regards,
Pascal
From: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
To: Pascal Parrot <pascal_parrot@xxxxxxxxxxx>, fedora-xen@xxxxxxxxxx
Subject: Re: Problem assigning a usb or pci port to a domU
Date: Wed, 11 Oct 2006 15:26:46 +0900
Hi, Pascal
Our method needs kernel recompilation.
I want to ask you your environment.
1)Do You plan to do it w/ xenguest-install.py?
(We are not succeeded yet since pciback.hide is not passed to xen0)
or
2)Do You plan to do from compile?
(We are just using the original xen's
buildconfigs/linux-defconfig_xenU_x86_32)
and Set
CONFIG_PCI=y
CONFIG_XEN_PCIDEV_FRONTEND=y
for DomU
and
CONFIG_XEN_PCIDEV_BACKEND_PASS=y
for Dom0
For more detail, see the original Xen file of
linux-sparse/drivers/xen/pciback/Makefile.
Thanks
Atsushi SAKAI
> Yoshi-san, Thank you for the link.
>
>
> The link suggests to build from the source and set the parameters
CONFIG_PCI and CONFIG_XEN_PCIDEV_FRONTEND to "y". These parameters are set
to "y" in xen0 and the xen documentation says that it is possible to use
xen0 in the domains and it might be easier to do than to build from the
source. quote "The ``0'' suffixed privileged versions can be used to boot
the system, as well as in driver domains and unprivileged domains."
>
> How can I make my domU use the xen0 kernel?
>
>
> I downloaded xen0 in the domU but the domain will not boot from it and
it gives me an error (Error: (22, 'Invalid argument')). When I use
the"kernel" parameter in the configuration file of the domU, it does not
seem to have any effect. I am still prompted for the kernel to use (grub).
>
> Pascal
--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
