Xen users - Aug 2011 - "update-grub" adds line to "multiboot"

Hello Xen folks,

I use Debian Squeeze. I want to passthrough PCI devices.
With the old stable Debian (grub legacy) i did not have problems.

I edit /etc/default/grub like:
    quote:
    GRUB_CMDLINE_XEN_DEFAULT="quiet xen-pciback.permissive
xen-pciback.hide=(00:14.2)(01:05.1)"


I run "update-grub". Now i look at /boot/grub/grub.cfg:


    ### BEGIN /etc/grub.d/20_linux_xen ###
    menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
4.0-amd64'' --class debian --class gnu-linux --class gnu --class os
--class xen {
    insmod part_msdos
    insmod ext2
    set root=''(hd0,msdos1)''
    search --no-floppy --fs-uuid --set 5a097ed6-415b-45ff-bba7-d628c92b1f7a
    echo ''Loading Linux 2.6.32-5-xen-amd64 ...''
    multiboot /xen-4.0-amd64.gz placeholder quiet xen-pciback.permissive
xen-pciback.hide=(00:14.2)(01:05.1)
    module /vmlinuz-2.6.32-5-xen-amd64 placeholder
root=/dev/mapper/vg_dom0-lv_root ro quiet
    echo ''Loading initial ramdisk ...''
    module /initrd.img-2.6.32-5-xen-amd64
    }


The "pciback" command is at the "multiboot" line. This does
not work? It does not seize the device after a reboot.

If i use:
    quote:
    GRUB_CMDLINE_LINUX_DEFAULT="quiet xen-pciback.permissive
xen-pciback.hide=(00:14.2)(01:05.1)"


The result is:
    ### BEGIN /etc/grub.d/20_linux_xen ###
    menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
4.0-amd64'' --class debian --class gnu-linux --class gnu --class os
--class xen {
    insmod part_msdos
    insmod ext2
    set root=''(hd0,msdos1)''
    search --no-floppy --fs-uuid --set 5a097ed6-415b-45ff-bba7-d628c92b1f7a
    echo ''Loading Linux 2.6.32-5-xen-amd64 ...''
    multiboot /xen-4.0-amd64.gz placeholder
    module /vmlinuz-2.6.32-5-xen-amd64 placeholder
root=/dev/mapper/vg_dom0-lv_root ro quiet xen-pciback.permissive
xen-pciback.hide=(00:14.2)(01:05.1)
    echo ''Loading initial ramdisk ...''
    module /initrd.img-2.6.32-5-xen-amd64
    }



Now the "pciback" command is at the "module" line and the
device is actually seized. The problem is that is added to all linux kernels and
not only the Xen kernel.
  

-- 
Best regards,
 MisterE                          mailto:MisterE2002@zonnet.nl


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, Aug 30, 2011 at 2:54 PM, MisterE <MisterE2002@zonnet.nl>
wrote:
> Hello Xen folks,
>
> I use Debian Squeeze. I want to passthrough PCI devices.
> With the old stable Debian (grub legacy) i did not have problems.
>
> I edit /etc/default/grub like:
>    quote:
>    GRUB_CMDLINE_XEN_DEFAULT="quiet xen-pciback.permissive
xen-pciback.hide=(00:14.2)(01:05.1)"
>
>
> I run "update-grub". Now i look at /boot/grub/grub.cfg:
>
>
>    ### BEGIN /etc/grub.d/20_linux_xen ###
>    menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and
XEN 4.0-amd64'' --class debian --class gnu-linux --class gnu --class os
--class xen {
>    insmod part_msdos
>    insmod ext2
>    set root=''(hd0,msdos1)''
>    search --no-floppy --fs-uuid --set 5a097ed6-415b-45ff-bba7-d628c92b1f7a
>    echo ''Loading Linux 2.6.32-5-xen-amd64 ...''
>    multiboot /xen-4.0-amd64.gz placeholder quiet xen-pciback.permissive
xen-pciback.hide=(00:14.2)(01:05.1)
>    module /vmlinuz-2.6.32-5-xen-amd64 placeholder
root=/dev/mapper/vg_dom0-lv_root ro quiet
>    echo ''Loading initial ramdisk ...''
>    module /initrd.img-2.6.32-5-xen-amd64
>    }
>
>
> The "pciback" command is at the "multiboot" line. This
does not work? It does not seize the device after a reboot.
>
> If i use:
>    quote:
>    GRUB_CMDLINE_LINUX_DEFAULT="quiet xen-pciback.permissive
xen-pciback.hide=(00:14.2)(01:05.1)"
>
>
> The result is:
>    ### BEGIN /etc/grub.d/20_linux_xen ###
>    menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and
XEN 4.0-amd64'' --class debian --class gnu-linux --class gnu --class os
--class xen {
>    insmod part_msdos
>    insmod ext2
>    set root=''(hd0,msdos1)''
>    search --no-floppy --fs-uuid --set 5a097ed6-415b-45ff-bba7-d628c92b1f7a
>    echo ''Loading Linux 2.6.32-5-xen-amd64 ...''
>    multiboot /xen-4.0-amd64.gz placeholder
>    module /vmlinuz-2.6.32-5-xen-amd64 placeholder
root=/dev/mapper/vg_dom0-lv_root ro quiet xen-pciback.permissive
xen-pciback.hide=(00:14.2)(01:05.1)
>    echo ''Loading initial ramdisk ...''
>    module /initrd.img-2.6.32-5-xen-amd64
>    }
>
>
>
> Now the "pciback" command is at the "module" line and
the device is actually seized. The problem is that is added to all linux kernels
and not only the Xen kernel.
>
This is more of a bug against the packaging of grub2 support for Xen
in Debian. You should file a bug with Debian.

Thanks,
Todd


-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html
http://runningxen.com/

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users