[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Solved - PCIe/VGA passthrough
-----Original Message----- From: Dariusz Krempa [mailto:imperiaonline4@xxxxxxxxx] Sent: Wednesday, September 19, 2012 11:23 AM To: Marc Tousignant Subject: Re: [Xen-users] PCIe/VGA passthrough 2012/9/19 Marc Tousignant <myrdhn@xxxxxxxxx>: > > > -----Original Message----- > From: Dariusz Krempa [mailto:imperiaonline4@xxxxxxxxx] > Sent: Wednesday, September 19, 2012 9:29 AM > To: Marc Tousignant > Subject: Re: [Xen-users] PCIe/VGA passthrough > > > Hi. > I've spend last few days to turn on vga passthrough on my box and > finally i did it. Everything what i've read about configurations tells > me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), but... > I followed also tutorial from Teo En Ming and i did patch from David > Gis. I have no BAR's, then i used ranges from dmesg | grep '1:00.0' | > grep mem and did patch like following David's Gis and Teo En Ming descriptions. > > I'm not yet sure that is full success, but Gpu-z and Cpu-z recognized > my hardware, also benchmark from Unigin heaven is pretty good. I did > pciback configuration for window xp DomU not like Teo En Ming with > pci-stub. I hope this will helpfully for You. > > --- > > Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/mem > line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff > pref] > > But my video card has ranges: > Region 0: Memory at cc000000 (32-bit, non-prefetchable) [size=16M] > Region 1: Memory at b0000000 (64-bit, prefetchable) [size=256M] > Region 3: Memory at ca000000 (64-bit, non-prefetchable) [size=32M] > Region 5: I/O ports at 9c00 [size=128] What the dmesg seems to > be finding is the one line from the lspci output on my card: > [virtual] Expansion ROM at cd000000 [disabled] [size=128K] > > MarcT > I am totally newbie with linux and Xen, but i think You could rebuild Dom0 or Xen or both, but first try to see what You get from this and compare to David's Gis output. I have for all "=y" grep -i xen /boot/config ---- Solved it. Turns out you can't find the memory without first setting up the kernel commands to hide the device. dmesg | grep 01:00.0 | grep "pci.*mem" pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] MarcT _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |