thr3ads.net - Xen users - [Xen-users] Yet Another PCI passthrough question [Aug 2011]

If this information is useful, please help other people find it:
Share via:

Beasley, Julien

2011-Aug-31 17:24 UTC

[Xen-users] Yet Another PCI passthrough question

Hello all,

I''m trying to pass my PCI device through to an HVM. I''m
following the steps on the xen pci passthrough wiki.

First I check my pci devices
#lspci -

03:00.0 VGA compatible controller: ATI Technologies Inc Device 671d
03:00.1 Audio device: ATI Technologies Inc Device aa80
04:00.0 Display controller: ATI Technologies Inc Device 671d
04:00.1 Audio device: ATI Technologies Inc Device aa80


Now I edit my grub entry. I''m on SuSE so it''s menu.list, not
grub.conf
#less /boot/grub/menu.lst

###Don''t change this comment - YaST2 identifier: Original name: xen###
title Xen -- openSUSE 11.4 - 2.6.37.6-0.7
    root (hd0,1)
    kernel /boot/xen.gz vga=mode-0x375 
    module /boot/vmlinuz-2.6.37.6-0.7-xen
root=/dev/disk/by-id/ata-ST3250410AS_6RYJWXM7-part2
resume=/dev/disk/by-id/ata-ST3250410AS_6RYJWXM7-part1 splash=silent quiet
showopts vga=0x375 xen-pciback.hide=(03:00.0)(04:00.0)
    module /boot/initrd-2.6.37.6-0.7-xen

Now reboot, and look at assignable devices
# xm pci-list-assignable-devices


Nothing shows up here. I''ve also tried adding the xen-pciback.hide line
to the other module line in grub, that''s not doing anything either.

What am I missing? I searched the archives of this list, found this
(http://lists.xensource.com/archives/html/xen-users/2011-05/msg00517.html) in
May, same problem. Followed the instructions. Am I missing something dumb?

Julien



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

Beasley, Julien

2011-Aug-31 17:29 UTC

head link

[Xen-users] RE: Yet Another PCI passthrough question

Oh, and I guess I should give my system info. I''m running with Suse
11.4, which has Xen 4.0.2_52-0.2.1 that comes built natively

-----Original Message-----
From: Beasley, Julien 
Sent: Wednesday, August 31, 2011 10:25 AM
To: xen-users@lists.xensource.com
Subject: Yet Another PCI passthrough question

Hello all,

I''m trying to pass my PCI device through to an HVM. I''m
following the steps on the xen pci passthrough wiki.

First I check my pci devices
#lspci -

03:00.0 VGA compatible controller: ATI Technologies Inc Device 671d
03:00.1 Audio device: ATI Technologies Inc Device aa80
04:00.0 Display controller: ATI Technologies Inc Device 671d
04:00.1 Audio device: ATI Technologies Inc Device aa80

Now I edit my grub entry. I''m on SuSE so it''s menu.list, not
grub.conf #less /boot/grub/menu.lst

###Don''t change this comment - YaST2 identifier: Original name: xen###
title Xen -- openSUSE 11.4 - 2.6.37.6-0.7
    root (hd0,1)
    kernel /boot/xen.gz vga=mode-0x375 
    module /boot/vmlinuz-2.6.37.6-0.7-xen
root=/dev/disk/by-id/ata-ST3250410AS_6RYJWXM7-part2
resume=/dev/disk/by-id/ata-ST3250410AS_6RYJWXM7-part1 splash=silent quiet
showopts vga=0x375 xen-pciback.hide=(03:00.0)(04:00.0)
    module /boot/initrd-2.6.37.6-0.7-xen

Now reboot, and look at assignable devices # xm pci-list-assignable-devices

Nothing shows up here. I''ve also tried adding the xen-pciback.hide line
to the other module line in grub, that''s not doing anything either.

What am I missing? I searched the archives of this list, found this
(http://lists.xensource.com/archives/html/xen-users/2011-05/msg00517.html) in
May, same problem. Followed the instructions. Am I missing something dumb?

Julien

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

Beasley, Julien

2011-Aug-31 18:20 UTC

head link

[Xen-users] RE: Yet Another PCI passthrough question

I wanted to say I also checked that virtualization is runnig:

# xm dmesg
 __  __            _  _    ___   ____      ____ ____      ___   ____    _ 
 \ \/ /___ _ __   | || |  / _ \ |___ \    | ___|___ \    / _ \ |___ \  / |
  \  // _ \ ''_ \  | || |_| | | |  __) |   |___ \ __) |__| | | |  __) |
| |
  /  \  __/ | | | |__   _| |_| | / __/     ___) / __/|__| |_| | / __/ _| |
 /_/\_\___|_| |_|    |_|(_)___(_)_____|___|____/_____|   \___(_)_____(_)_|
                                     |_____|                              
(XEN) Xen version 4.0.2_52-0.2.1 (abuild@) (gcc version 4.5.1 20101208
[gcc-4_5-branch revision 167585] (SUSE Linux) ) Tue Jul 26 20:31:58 UTC 2011 ...
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed


And also checked that pci pass through was enabled in the xen config

# less /boot/config-2.6.37.6-0.7-xen
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_PASS=y


At this point I''m really quite stumped. I''d appreciate any
thoughts on what I''m doing wrong.

Julien

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Beasley, Julien
Sent: Wednesday, August 31, 2011 10:30 AM
To: xen-users@lists.xensource.com
Subject: [Xen-users] RE: Yet Another PCI passthrough question

Oh, and I guess I should give my system info. I''m running with Suse
11.4, which has Xen 4.0.2_52-0.2.1 that comes built natively

-----Original Message-----
From: Beasley, Julien 
Sent: Wednesday, August 31, 2011 10:25 AM
To: xen-users@lists.xensource.com
Subject: Yet Another PCI passthrough question

Hello all,

I''m trying to pass my PCI device through to an HVM. I''m
following the steps on the xen pci passthrough wiki.

First I check my pci devices
#lspci -

03:00.0 VGA compatible controller: ATI Technologies Inc Device 671d
03:00.1 Audio device: ATI Technologies Inc Device aa80
04:00.0 Display controller: ATI Technologies Inc Device 671d
04:00.1 Audio device: ATI Technologies Inc Device aa80


Now I edit my grub entry. I''m on SuSE so it''s menu.list, not
grub.conf #less /boot/grub/menu.lst

###Don''t change this comment - YaST2 identifier: Original name: xen###
title Xen -- openSUSE 11.4 - 2.6.37.6-0.7
    root (hd0,1)
    kernel /boot/xen.gz vga=mode-0x375 
    module /boot/vmlinuz-2.6.37.6-0.7-xen
root=/dev/disk/by-id/ata-ST3250410AS_6RYJWXM7-part2
resume=/dev/disk/by-id/ata-ST3250410AS_6RYJWXM7-part1 splash=silent quiet
showopts vga=0x375 xen-pciback.hide=(03:00.0)(04:00.0)
    module /boot/initrd-2.6.37.6-0.7-xen

Now reboot, and look at assignable devices # xm pci-list-assignable-devices


Nothing shows up here. I''ve also tried adding the xen-pciback.hide line
to the other module line in grub, that''s not doing anything either.

What am I missing? I searched the archives of this list, found this
(http://lists.xensource.com/archives/html/xen-users/2011-05/msg00517.html) in
May, same problem. Followed the instructions. Am I missing something dumb?

Julien



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



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

James Pifer

2011-Aug-31 20:43 UTC

head link

Re: [Xen-users] Yet Another PCI passthrough question

> Nothing shows up here. I''ve also tried adding the xen-pciback.hide
> line to the other module line in grub, that''s not doing anything
> either.
> 
> What am I missing? I searched the archives of this list, found this
> (http://lists.xensource.com/archives/html/xen-users/2011-05/msg00517.html)
in May, same problem. Followed the instructions. Am I missing something dumb?
> 
> Julien
> 
Julien,

I''m using xen 4.0.2 in sles11. Below is a little "doc" I use
for passing
through devices. It seems there are always different ways to do these
things, but this one does seem to work. 

Btw, my experience has been that xm pci-list-assignable-devices
sometimes doesn''t list anything, but we''re still able to pass
through.

HTH,
James



lspci to find <PCI-ID>

find /sys/bus/pci/drivers -name 0000:<PCI-ID>

echo -n "<PCI-ID>" > "/sys/bus/pci/drivers/<driver
dir>/unbind"
*****(where <driver dir> is from the previous command.)
echo -n "<PCI-ID>" >
"/sys/bus/pci/drivers/pciback/new_slot"
echo -n "<PCI-ID>" >
"/sys/bus/pci/drivers/pciback/bind"


#Start Example:

find /sys/bus/pci/drivers -name 0000:0e:04.0

modprobe pciback
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/mptspi/unbind"
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/pciback/new_slot"
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/pciback/bind"

#End Example


Edit or create /etc/init.d/after.local and add:

modprobe pciback
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/mptspi/unbind"
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/pciback/new_slot"
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/pciback/bind"


Now try provisioning new VM using the hardware device or add hardware
device to existing VM.


Note:for some scsi devices such as tape drives, you may have to update
kernel boot parameters to hide the scsi card from the host OS. For
example, add the following to the modules line in /boot/grub/menu.lst
for the xen boot process:

pciback.permissive pciback.hide=(0e:04.0)(0e:04.1)
pci=resource_alignment=0e:04.0;0e:04.1


For example:
module /boot/vmlinuz-2.6.32.12-0.7-xen
root=/dev/disk/by-id/cciss-3600508b1001030364643393433300000-part2
resume=/dev/disk/by-id/cciss-3600508b1001030364643393433300000-part1
splash=silent showopts pciback.permissive pciback.hide=(0e:04.0)(0e:04.1)
pci=resource_alignment=0e:04.0;0e:04.1




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

Beasley, Julien

2011-Aug-31 21:29 UTC

head link

RE: [Xen-users] Yet Another PCI passthrough question

Thank you for the reply James,

I tried following your script, but even then something seems to be missing.

# lspci
03:00.0 VGA compatible controller: ATI Technologies Inc Device 671d
03:00.1 Audio device: ATI Technologies Inc Device aa80
04:00.0 Display controller: ATI Technologies Inc Device 671d
04:00.1 Audio device: ATI Technologies Inc Device aa80


I''m assuming at this point that <PCI-ID> is 04:00.0 and 03.00.0

# find /sys/bus/pci/drivers -name 0000:04:00.0

then returns no results. 

Also, regarding modprobe pciback, I did a grep in the modules directory for the
term "pciback" and no results are shown

# grep pciback /lib/modules/2.6.37.6-0.7-xen
# 

Is this indicative of something missing? I appreciate your help! I''m
not trying a scsi device, simply getting my video card to pass through.

Julien

________________________________________
Julien,

I''m using xen 4.0.2 in sles11. Below is a little "doc" I use
for passing
through devices. It seems there are always different ways to do these
things, but this one does seem to work.

Btw, my experience has been that xm pci-list-assignable-devices
sometimes doesn''t list anything, but we''re still able to pass
through.

HTH,
James



lspci to find <PCI-ID>

find /sys/bus/pci/drivers -name 0000:<PCI-ID>

echo -n "<PCI-ID>" > "/sys/bus/pci/drivers/<driver
dir>/unbind"
*****(where <driver dir> is from the previous command.)
echo -n "<PCI-ID>" >
"/sys/bus/pci/drivers/pciback/new_slot"
echo -n "<PCI-ID>" >
"/sys/bus/pci/drivers/pciback/bind"


#Start Example:

find /sys/bus/pci/drivers -name 0000:0e:04.0

modprobe pciback
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/mptspi/unbind"
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/pciback/new_slot"
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/pciback/bind"

#End Example


Edit or create /etc/init.d/after.local and add:

modprobe pciback
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/mptspi/unbind"
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/pciback/new_slot"
echo -n "0000:0e:04.0" >
"/sys/bus/pci/drivers/pciback/bind"


Now try provisioning new VM using the hardware device or add hardware
device to existing VM.


Note:for some scsi devices such as tape drives, you may have to update
kernel boot parameters to hide the scsi card from the host OS. For
example, add the following to the modules line in /boot/grub/menu.lst
for the xen boot process:

pciback.permissive pciback.hide=(0e:04.0)(0e:04.1)
pci=resource_alignment=0e:04.0;0e:04.1


For example:
module /boot/vmlinuz-2.6.32.12-0.7-xen
root=/dev/disk/by-id/cciss-3600508b1001030364643393433300000-part2
resume=/dev/disk/by-id/cciss-3600508b1001030364643393433300000-part1
splash=silent showopts pciback.permissive pciback.hide=(0e:04.0)(0e:04.1)
pci=resource_alignment=0e:04.0;0e:04.1




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



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

James Pifer

2011-Sep-01 14:20 UTC

head link

RE: [Xen-users] Yet Another PCI passthrough question

On Wed, 2011-08-31 at 16:29 -0500, Beasley, Julien
wrote:> Thank you for the reply James,
> 
> I tried following your script, but even then something seems to be missing.
> 
> # lspci
> 03:00.0 VGA compatible controller: ATI Technologies Inc Device 671d
> 03:00.1 Audio device: ATI Technologies Inc Device aa80
> 04:00.0 Display controller: ATI Technologies Inc Device 671d
> 04:00.1 Audio device: ATI Technologies Inc Device aa80
> 
> 
> I''m assuming at this point that <PCI-ID> is 04:00.0 and
03.00.0
> 
> # find /sys/bus/pci/drivers -name 0000:04:00.0
> 
> then returns no results. 
> 
> Also, regarding modprobe pciback, I did a grep in the modules directory for
the term "pciback" and no results are shown
> 
> # grep pciback /lib/modules/2.6.37.6-0.7-xen
> # 
> 
> Is this indicative of something missing? I appreciate your help!
I''m not trying a scsi device, simply getting my video card to pass
through.

If the find command doesn''t find anything, then there is not a specific
driver in use, so I believe you would be able to run the last two
commands giving the device to pciback. 
echo -n "0000:04:00.0" >
"/sys/bus/pci/drivers/pciback/new_slot"
echo -n "0000:04:00.0" >
"/sys/bus/pci/drivers/pciback/bind"

As far as pciback module, I also get no results fro the grep command
either, but try this. 

"lsmod | grep pciback" and verify it is not loaded. 
Then do "modprobe pciback" and redo "lsmod | grep pciback".
If you now
see it loaded you should be good to go. 

After loading pciback, and running the two commands above, do lspci -v.
Find the device in question, 04:00.0, and the driver in use should be
pciback. 

If so, then try passing it to your VM. 

James

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

Beasley, Julien

2011-Sep-01 18:17 UTC

head link

RE: [Xen-users] Yet Another PCI passthrough question

Thank you very much, James, that worked! I'm going to post exactly what I
did for future people that encounter the same problem.

// first check that nothing shows in lsmod
# lsmod | grep pciback
# 

// now type modprobe
# modprobe pciback

// now try the lsmod again. Note I had to wait a minute or so.. at first nothing
was showing up
# lsmod | grep pciback
pciback                50301  0 
xenbus_be               4261  5 pciback,usbbk,netbk,blkbk,blktap

// now do the step James suggested
# echo -n "0000:04:00.0" >
"/sys/bus/pci/drivers/pciback/new_slot"

# echo -n "0000:04:00.0" >
"/sys/bus/pci/drivers/pciback/bind"

// check that lspci shows pciback in use
# lspci -v
04:00.0 Display controller: ATI Technologies Inc Device 671d
	Subsystem: ATI Technologies Inc Device 1b2a
	Flags: fast devsel, IRQ 24
	Memory at d0000000 (64-bit, prefetchable) [disabled] [size=256M]
	Memory at fe6e0000 (64-bit, non-prefetchable) [disabled] [size=128K]
	I/O ports at e000 [disabled] [size=256]
	Expansion ROM at fe6c0000 [disabled] [size=128K]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Legacy Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
	Capabilities: [150] Advanced Error Reporting
	Kernel driver in use: pciback


// so far this works, and I can see the kernel driver in pciback. Good!

// Xen wiki says to check this and not proceed if empty
# xm pci-list-assignable-devices

// that was still empty... but let's keep going anyways


// edit the config to pass the pci device
# vi /etc/xen/vm/windowsvistax64
...
pci= [ '04:00.0' ]


// check that nothing is assigned to the pci list for that VM
# xm pci-list windowsvistax64

// now create the VM
# xm create windowsvistax64

// checkt hat something is assigned to the vm now
xm pci-list windowsvistax64
VSlt VFn domain bus  slot func
0x05 0x0 0x0000 0x04 0x00 0x0


// then I opened the VM graphics console, and it indeed saw my card. Thank you
James for your help!

Julien

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

James Pifer

2011-Sep-16 12:26 UTC

head link

RE: [Xen-users] Yet Another PCI passthrough question

On Thu, 2011-09-01 at 13:17 -0500, Beasley, Julien
wrote:> Thank you very much, James, that worked! I''m going to post exactly
what I did for future people that encounter the same problem.
> 
> // first check that nothing shows in lsmod
> # lsmod | grep pciback
> # 
> 
> // now type modprobe
> # modprobe pciback
> 
> // now try the lsmod again. Note I had to wait a minute or so.. at first
nothing was showing up
> # lsmod | grep pciback
> pciback                50301  0 
> xenbus_be               4261  5 pciback,usbbk,netbk,blkbk,blktap
> 
> // now do the step James suggested
> # echo -n "0000:04:00.0" >
"/sys/bus/pci/drivers/pciback/new_slot"
> 
> # echo -n "0000:04:00.0" >
"/sys/bus/pci/drivers/pciback/bind"
> 
> // check that lspci shows pciback in use
> # lspci -v
> 04:00.0 Display controller: ATI Technologies Inc Device 671d
> 	Subsystem: ATI Technologies Inc Device 1b2a
> 	Flags: fast devsel, IRQ 24
> 	Memory at d0000000 (64-bit, prefetchable) [disabled] [size=256M]
> 	Memory at fe6e0000 (64-bit, non-prefetchable) [disabled] [size=128K]
> 	I/O ports at e000 [disabled] [size=256]
> 	Expansion ROM at fe6c0000 [disabled] [size=128K]
> 	Capabilities: [50] Power Management version 3
> 	Capabilities: [58] Express Legacy Endpoint, MSI 00
> 	Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
> 	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
> 	Capabilities: [150] Advanced Error Reporting
> 	Kernel driver in use: pciback
> 
> 
> // so far this works, and I can see the kernel driver in pciback. Good!
> 
> // Xen wiki says to check this and not proceed if empty
> # xm pci-list-assignable-devices
> 
> // that was still empty... but let''s keep going anyways
> 
> 
> // edit the config to pass the pci device
> # vi /etc/xen/vm/windowsvistax64
> ...
> pci= [ ''04:00.0'' ]
> 
> 
> // check that nothing is assigned to the pci list for that VM
> # xm pci-list windowsvistax64
> 
> // now create the VM
> # xm create windowsvistax64
> 
> // checkt hat something is assigned to the vm now
> xm pci-list windowsvistax64
> VSlt VFn domain bus  slot func
> 0x05 0x0 0x0000 0x04 0x00 0x0
> 
> 
> // then I opened the VM graphics console, and it indeed saw my card. Thank
you James for your help!
> 
> Julien
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
I just came across a problem after updating some sles11sp1 servers with
pci passthrough. Apparently the way we are doing it, and the way I
shared here, is a combination of early and late binding, which might
cause some issues. 

Here''s how we fixed it. "xm pci-list-assignable-devices" also
works
after we did these changes. 

1- Make sure all the stuff is commented out in after.local
 
2-  Modify  /etc/sysconfig/kernel and add pciback:
INITRD_MODULES="thermal cciss hpsa pciback mptsas ata_piix ata_generic
ide_pci_generic processor fan jbd ext3 edd mptspi hpahcisr mptbase
mptscsih"

Note:  Make sure pciback is up towards the front as in this example

Then run "mkintrd" to build it into the init ram disk so it is
available
for the kernel load line parameters.  You may see some dependency errors
about it....but disregard.
 
3-  Then add the pci stuff back into the kernel module load line.  Run
lspci first to make sure the PCI identifiers  are still the same with
the new kernel. I don''t think they''ll be different.
 
For example:
module /boot/vmlinuz-2.6.32.12-0.7-xen root=/dev/cciss/c0d0p2
resume=/dev/cciss/c0d0p1 splash=silent showopts vga=0x317 pciback.permissive
pciback.hide=(0e:04.0)(0e:04.1) pci=resource_alignment=0e:04.0;0e:04.1
 
4-  Then re-boot and check "xm pci-list-assignable-devices" to see if
they show up.  

5. Assign devices to VM as you wish. 

This is actually a little bit cleaner as you don''t need anything in
after.local. Be aware that after a kernel update you need to make sure
you add the PCI stuff back to the module line in menu.lst.

James



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

Andy Burns

2011-Sep-17 13:22 UTC

head link

Re: [Xen-users] Yet Another PCI passthrough question

On 16 September 2011 13:26, James Pifer <jep@obrien-pifer.com> wrote:
> module /boot/vmlinuz-2.6.32.12-0.7-xen root=/dev/cciss/c0d0p2
resume=/dev/cciss/c0d0p1 splash=silent showopts vga=0x317 pciback.permissive
pciback.hide=(0e:04.0)(0e:04.1) pci=resource_alignment=0e:04.0;0e:04.1
One thing I''ve found when using grub2, then grub interprets the
semi-colon between multiple BDF triplets as a separator, e.g. in the
above case it
would only pass to the kernel

pci=resource_alignment=0e:04.0

and then give an error

error: unknown command `0e:04.1''

the fix is to wrap single quotes around the clause, e.g

module /boot/vmlinuz-2.6.32.12-0.7-xen root=/dev/cciss/c0d0p2
resume=/dev/cciss/c0d0p1 splash=silent showopts vga=0x317
pciback.permissive pciback.hide=(0e:04.0)(0e:04.1)
''pci=resource_alignment=0e:04.0;0e:04.1''

Hopefully google will squirrel this a way and it be useful to anyone
else hitting the same issue ...

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

James Pifer

2011-Sep-17 23:22 UTC

head link

Re: [Xen-users] Yet Another PCI passthrough question

On Sat, 2011-09-17 at 14:22 +0100, Andy Burns wrote:> On 16 September 2011 13:26, James Pifer <jep@obrien-pifer.com> wrote:
> 
> > module /boot/vmlinuz-2.6.32.12-0.7-xen root=/dev/cciss/c0d0p2
resume=/dev/cciss/c0d0p1 splash=silent showopts vga=0x317 pciback.permissive
pciback.hide=(0e:04.0)(0e:04.1) pci=resource_alignment=0e:04.0;0e:04.1
> 
> One thing I''ve found when using grub2, then grub interprets the
> semi-colon between multiple BDF triplets as a separator, e.g. in the
> above case it
> would only pass to the kernel
> 
> pci=resource_alignment=0e:04.0
> 
> and then give an error
> 
> error: unknown command `0e:04.1''
> 
> the fix is to wrap single quotes around the clause, e.g
> 
> module /boot/vmlinuz-2.6.32.12-0.7-xen root=/dev/cciss/c0d0p2
> resume=/dev/cciss/c0d0p1 splash=silent showopts vga=0x317
> pciback.permissive pciback.hide=(0e:04.0)(0e:04.1)
> ''pci=resource_alignment=0e:04.0;0e:04.1''
> 
> Hopefully google will squirrel this a way and it be useful to anyone
> else hitting the same issue ...
Thanks Andy. That''s interesting. I''ll have to keep note of
that. I have
not seen that issue. 

James


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

Pasi Kärkkäinen

2011-Sep-26 18:44 UTC

head link

Re: [Xen-users] Yet Another PCI passthrough question

On Sat, Sep 17, 2011 at 02:22:40PM +0100, Andy Burns
wrote:> On 16 September 2011 13:26, James Pifer <jep@obrien-pifer.com> wrote:
> 
> > module /boot/vmlinuz-2.6.32.12-0.7-xen root=/dev/cciss/c0d0p2
resume=/dev/cciss/c0d0p1 splash=silent showopts vga=0x317 pciback.permissive
pciback.hide=(0e:04.0)(0e:04.1) pci=resource_alignment=0e:04.0;0e:04.1
> 
> One thing I''ve found when using grub2, then grub interprets the
> semi-colon between multiple BDF triplets as a separator, e.g. in the
> above case it
> would only pass to the kernel
> 
> pci=resource_alignment=0e:04.0
> 
> and then give an error
> 
> error: unknown command `0e:04.1''
> 
> the fix is to wrap single quotes around the clause, e.g
> 
> module /boot/vmlinuz-2.6.32.12-0.7-xen root=/dev/cciss/c0d0p2
> resume=/dev/cciss/c0d0p1 splash=silent showopts vga=0x317
> pciback.permissive pciback.hide=(0e:04.0)(0e:04.1)
> ''pci=resource_alignment=0e:04.0;0e:04.1''
> 
> Hopefully google will squirrel this a way and it be useful to anyone
> else hitting the same issue ...
> 
Thanks! I added a note about this grub2 issue to:
http://wiki.xen.org/xenwiki/XenPCIpassthrough

-- Pasi


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

Possibly Parallel Threads

Search for more maybe matching threads

Xen users - Aug 2011 - Yet Another PCI passthrough question

[Xen-users] Yet Another PCI passthrough question

[Xen-users] RE: Yet Another PCI passthrough question

[Xen-users] RE: Yet Another PCI passthrough question

Re: [Xen-users] Yet Another PCI passthrough question

RE: [Xen-users] Yet Another PCI passthrough question

RE: [Xen-users] Yet Another PCI passthrough question

RE: [Xen-users] Yet Another PCI passthrough question

RE: [Xen-users] Yet Another PCI passthrough question

Re: [Xen-users] Yet Another PCI passthrough question

Re: [Xen-users] Yet Another PCI passthrough question

Re: [Xen-users] Yet Another PCI passthrough question

Possibly Parallel Threads