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

Re: [Xen-users] kernel parameter for multiple pci hide?


  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Christian Holpert <christian@xxxxxxxxxx>
  • Date: Thu, 19 Dec 2019 11:13:14 +0100
  • Delivery-date: Thu, 19 Dec 2019 10:14:51 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>
  • Openpgp: preference=signencrypt

my grub.cfg lists:

module  /kernel-5.3.7-xen0 placeholder root=/dev/sda3 ro
init=/lib/systemd/systemd xen-pciback.hide=(04:00.0)(00:14.0)
rootfstype=ext4 [...]

xen ~ # dmesg|grep pcib
[    0.000000] Command line: placeholder root=/dev/sda3 ro
init=/lib/systemd/systemd xen-pciback.hide=(04:00.0)(00:14.0)
rootfstype=ext4 net.ifnames=0 reassign_resources noirqdebug
[    6.581153] Kernel command line: placeholder root=/dev/sda3 ro
init=/lib/systemd/systemd xen-pciback.hide=(04:00.0)(00:14.0)
rootfstype=ext4 net.ifnames=0 reassign_resources noirqdebug
[    7.360586] pciback 0000:00:14.0: seizing device
[    7.360622] pciback 0000:04:00.0: seizing device

xen_version  is 4.12.1

perhaps your syntax is just incorrect: (01.00.1) instead of (01:00.1).

regards,
Christian

Hi All
>
> I've a problem with the kernel parameter xen-pciback.hide.
>
> This works:
>
> xen-pciback.hide=(01:00.0)
>
> dmesg:
> pciback 0000:01:00.0: seizing device
> pciback 0000:01:00.0: enabling device (0000 -> 0003)
> xen_pciback: backend is vpci
>
> this doesnt work (syntax from official xen docu):
>
> xen-pciback.hide=(01:00.0)(01.00.1)
>
> dmesg:
> xen_pciback: Error parsing pci_devs_to_hide at "(01:00.01)"
>
> what is the correct syntax for it?
>
> -- 
> ------
> Greetz
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.