On Sat, Jul 2, 2011 at 2:02 AM, Ian Campbell Ian.Campbell@citrix.comwrote:
On Sat, 2011-07-02 at 05:15 +0100, Fajar A. Nugraha wrote:
Second part, F15's boot/config-2.6.38.6-26.rc1.fc15.x86_64 has these entries: CONFIG_XEN_PLATFORM_PCI=m CONFIG_XEN_BLKDEV_FRONTEND=m
So if you could add xen-platform-pci.ko and xen-blkfront.ko to the install initrd, you should be able to use PV drivers directly. Not sure what's the easiest way to do it though (maybe unpack initrd, add some files, and repack it).
Has somebody reported this as a bug against F15? Either the initrd tool (drakut?) should understand when xen-platform-pci is needed or it should be =y. It's a very small amount of code so building it in is not unreasonable.
Ian.
I'm filing one now.
On Sat, Jul 2, 2011 at 2:07 AM, Travis corasian@gmail.com wrote:
On Sat, Jul 2, 2011 at 2:02 AM, Ian Campbell Ian.Campbell@citrix.comwrote:
On Sat, 2011-07-02 at 05:15 +0100, Fajar A. Nugraha wrote:
Second part, F15's boot/config-2.6.38.6-26.rc1.fc15.x86_64 has these entries: CONFIG_XEN_PLATFORM_PCI=m CONFIG_XEN_BLKDEV_FRONTEND=m
So if you could add xen-platform-pci.ko and xen-blkfront.ko to the install initrd, you should be able to use PV drivers directly. Not sure what's the easiest way to do it though (maybe unpack initrd, add some files, and repack it).
Has somebody reported this as a bug against F15? Either the initrd tool (drakut?) should understand when xen-platform-pci is needed or it should be =y. It's a very small amount of code so building it in is not unreasonable.
Ian.
I'm filing one now.
https://bugzilla.redhat.com/show_bug.cgi?id=718382
-- "Eating and sleeping are the only activities that should be allowed to interrupt a man's enjoyment of his cigar." - Mark Twain
On Sat, Jul 02, 2011 at 03:05:59AM -0400, Travis wrote:
On Sat, Jul 2, 2011 at 2:07 AM, Travis corasian@gmail.com wrote:
On Sat, Jul 2, 2011 at 2:02 AM, Ian Campbell Ian.Campbell@citrix.comwrote:
On Sat, 2011-07-02 at 05:15 +0100, Fajar A. Nugraha wrote:
Second part, F15's boot/config-2.6.38.6-26.rc1.fc15.x86_64 has these entries: CONFIG_XEN_PLATFORM_PCI=m CONFIG_XEN_BLKDEV_FRONTEND=m
So if you could add xen-platform-pci.ko and xen-blkfront.ko to the install initrd, you should be able to use PV drivers directly. Not sure what's the easiest way to do it though (maybe unpack initrd, add some files, and repack it).
Has somebody reported this as a bug against F15? Either the initrd tool (drakut?) should understand when xen-platform-pci is needed or it should be =y. It's a very small amount of code so building it in is not unreasonable.
Ian.
I'm filing one now.
Anybody have some patches for it? They can be posted on the dracut mailing list? Did loading those two modules in the install initrd fix the installation?
On Jul 5, 2011 9:53 AM, "Konrad Rzeszutek Wilk" konrad.wilk@oracle.com wrote:
On Sat, Jul 02, 2011 at 03:05:59AM -0400, Travis wrote:
On Sat, Jul 2, 2011 at 2:07 AM, Travis corasian@gmail.com wrote:
On Sat, Jul 2, 2011 at 2:02 AM, Ian Campbell <Ian.Campbell@citrix.com
wrote:
On Sat, 2011-07-02 at 05:15 +0100, Fajar A. Nugraha wrote:
Second part, F15's boot/config-2.6.38.6-26.rc1.fc15.x86_64 has
these
entries: CONFIG_XEN_PLATFORM_PCI=m CONFIG_XEN_BLKDEV_FRONTEND=m
So if you could add xen-platform-pci.ko and xen-blkfront.ko to the install initrd, you should be able to use PV drivers directly. Not sure what's the easiest way to do it though (maybe unpack initrd,
add
some files, and repack it).
Has somebody reported this as a bug against F15? Either the initrd
tool
(drakut?) should understand when xen-platform-pci is needed or it
should
be =y. It's a very small amount of code so building it in is not unreasonable.
Ian.
I'm filing one now.
Anybody have some patches for it? They can be posted on the dracut mailing
list?
Did loading those two modules in the install initrd fix the installation?
The aforementioned 'xen_emul_unplug=never' kernel arg has worked well enough for me. I've pasted it into my kickstart files and my vms have been installing and running fine.
Anybody have some patches for it? They can be posted on the dracut mailing
list?
Did loading those two modules in the install initrd fix the installation?
The aforementioned 'xen_emul_unplug=never' kernel arg has worked well enough for me. I've pasted it into my kickstart files and my vms have been installing and running fine.
Ok, but with HVM drivers instead of the PV - at least during installation. Is the 'xen_emul_unplug=never' option also present in your VM when it is running?
On Wed, Jul 06, 2011 at 09:32:50AM -0400, Konrad Rzeszutek Wilk wrote:
Anybody have some patches for it? They can be posted on the dracut mailing
list?
Did loading those two modules in the install initrd fix the installation?
The aforementioned 'xen_emul_unplug=never' kernel arg has worked well enough for me. I've pasted it into my kickstart files and my vms have been installing and running fine.
Ok, but with HVM drivers instead of the PV - at least during installation. Is the 'xen_emul_unplug=never' option also present in your VM when it is running?
So I didn't even attempt to install it under HVM. I put this in my config file:
kernel = "/mnt/tftpboot/f15-x86_64/images/pxeboot/vmlinuz" ramdisk="//mnt/tftpboot/f15-x86_64/images/pxeboot/initrd.img" extra="console=hvc0 debug earlyprintk=xenboot askmethod vnc" memory = 1024 name = "Fedora" vcpus=2 vif = [ 'mac=00:0F:4B:00:00:63,bridge=switch' ] disk = [ 'phy:/dev/vg_guest_1/FC15,xvda,w' ] boot = "dnc" vnc=1 videoram=8 vnclisten="0.0.0.0" vncpasswd='' stdvga=0 serial='pty'
And was able to install it.
-
Konrad Rzeszutek Wilk -
Travis