Re: How to use xen-pciback

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 09, 2011 at 01:48:03PM +0200, Robin Axelsson wrote:
> On 2011-05-09 08:45, Pasi Kärkkäinen wrote:
>> On Fri, May 06, 2011 at 04:18:14PM +0200, Robin Axelsson wrote:
>>> On 2011-05-06 08:03, Pasi Kärkkäinen wrote:
>>>> On Thu, May 05, 2011 at 07:48:36PM +0200, Robin Axelsson wrote:
>>>>> Hi,
>>>>> I have compiled Jeremy's kernel on Fedora 14 and it turned out that
>>>>> xen-pciback is compiled into the kernel as a module. So I made a
>>>>> "xen-pciback.conf" file in /etc/modprobe.d. The problem is that I have
>>>>> to get modprobe to load before the drivers to the PCI devices I want to
>>>>> hide are loaded.
>>>>>
>>>>> So my question is how do I locate the drivers and find the points in the
>>>>> boot scripts where I can put the modprobe so that it is loaded before
>>>>> them? I tried lsmod and modinfo but they don't give much information. I
>>>>> only managed to find the driver for the Intel EXPI9400PT adapter e1000e.
>>>>>
>>>>> I want to hide the graphics adapter (Radeon 5450), Two USB2.0 ports, the
>>>>> Intel adapter, the USB3.0 controller and the Audio device, their
>>>>> assignments on machine are as follows:
>>>>>
>>>>> pci_0000_00_02_0   (GPU)
>>>>> pci_0000_00_12_0   (USB 2.0 should give 2 ports)
>>>>> pci_0000_00_14_2   (Audio device)
>>>>> pci_0000_00_0a_0   (Intel Adapter)
>>>>> pci_0000_00_09_0   (USB 3.0 Interface)
>>>>>
>>>>> but the question is where can I locate their drivers and how can I tap
>>>>> into the boot sequence so that the xen-pciback driver is loaded
>>>>> beforehand? The page
>>>>>
>>>>> http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module
>>>>>
>>>>> gives no information about this. It mentions something about "install
>>>>> skge ... " but it doesn't say where this line is to be put and how you
>>>>> figure out that skge is the driver to be disabled.
>>>>>
>>>> You probably should add the modules to be loaded from initrd image.
>>>>
>>>> Are you using mkinitrd? If yes, there's an option to preload modules..
>>>>
>>>> -- Pasi
>>> I issued the command
>>>
>>>    mkinitrd -v -f --preload xen-pciback /boot/initramfs-2.6.32.39.img
>>> 2.6.32.39
>>>
>>> and I noticed that the initramfs image file generated is considerably
>>> smaller than the initramfs imagefile generated by dracut. The dracut
>>> file is a bit over 80 MB whereas the new one is less than 8 MB.
>>>
>>> But the preload doesn't load the xen-pciback module. After the reboot
>>> when I list assignable PCI devices using xm, Xen returns nothing. If I
>>> issue 'modprobe xen-pciback' and then list the devices using xm I get
>>> one entry. What's wrong?
>>>
>> Hmm.. Is it possible that the other xen-related required modules
>> are not yet loaded at that point, so loading xen-pciback fails?
>>
>> You could always extract initramfs-2.6.32.39.img and read the 'init'
>> script in it and see what it's trying to do..
>>
>> -- Pasi
>>
>
> Perhaps you know how to extract the initramfs? I'm unable to find the  
> compression headers and I'm not sure what headers to look for. In the  
> first step I tried to locate the gzip header:
>

They're usually gzipped cpio archives.
So something like this should work:

mkdir temp && cd temp && zcat /boot/initramfs-version.img | cpio -i -d


-- Pasi


> # grep -a -b --only-matching $'\x8B'$'\x08' \boot\initramfs-`uname  -r`.img
> (offset1): (pattern)
> ...
> (offset<n>): (pattern)
> # dd if=/boot/intramfs-`uname -r`.img bs=1 skip=(offset1) | gunzip >  
> myimagefile
>
> but I'm unable to get to the cpio file. I tried once again grepping for  
> compression headers in myimagefile but I couldn't find anything. It  
> appears not to be compressed with zx, bzip2 or gzip. I could not use  
> cpio on the file directly either.
>
> Robin.
>
>
>>>>> I have set up the machine to init level 3 in the /etc/inittab (my
>>>>> install of F14 have no upstart targets). The xen-pciback module seems to
>>>>> be working. Something is wrong with the onboard sound chip. No drivers
>>>>> have ever successfully initiated it, neither in Windows nor Linux. So it
>>>>> is marked as an assignable device when looking it up with xm.
>>>>>
>>>>> Regards
>>>>>
>>>>> Robin.
>>>>>
>>>>> --
>>>>> xen mailing list
>>>>> xen@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> https://admin.fedoraproject.org/mailman/listinfo/xen
>>>> .
>>>>
>>> --
>>> xen mailing list
>>> xen@xxxxxxxxxxxxxxxxxxxxxxx
>>> https://admin.fedoraproject.org/mailman/listinfo/xen
>> .
>>
>
--
xen mailing list
xen@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/xen



[Index of Archives]     [Fedora General]     [Fedora Music]     [Linux Kernel]     [Fedora Desktop]     [Fedora Directory]     [PAM]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux