[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] can't passthrough video card
> -----Original Message----- > From: gordan@xxxxxxxxxx > Sent: Mon, 28 Oct 2013 07:14:06 +0000 > To: b.evans@xxxxxxxxx > Subject: Re: [Xen-users] can't passthrough video card > > On 10/28/2013 07:08 AM, bob evans wrote: >> Hi Gordan, thank you very much for your reply. >> >>> 1) Put something like this in your /etc/modprobe.d/xen-pciback.conf (or >>> equivalent on your distro) >>> >>> options xen-pciback hide=(08:00.0)(08:00.1) >>> >>> where 08:00.0 and 08:00.1 are PCI IDs of the device in question. >>> Alternatively, you may need to do the equivalent of this on your kernel >>> boot line if your xen-pciback module is built into the kernel. >> >> Ok, I've done this now. >> >>> If any of the devices were bound to a different driver first, for those >>> devices it is easier to do something like: >>> >>> xl pci-assignable-remove 0000:08.00.0 >>> >>> instead of what you did above. >> >> I switched from xm to xl, when I try this command it gives me this >> error: pci-assignable-remove: malformed BDF specification "0000:02.00.0" >> I also tried it with the format 02.00.0, and I tried it with >> pci-assignable-add, and I also tried it with another device. > > My bad - that should have been 0000:02:00.0 rather than 0000:02.00.0 > (note the 2nd colon). > >>> This is a problem - if the radeon driver has already initialized the >>> card, it's not going to work. ATI cards' BIOS and drivers aren't good >>> enough to handle this situation properly. >>> >> >> So I should blacklist the radeon driver then right? I can do this >> because only my AMD graphics card uses this driver. I'm not sure what to >> do about the HDMI sound device though, because I have many components >> using that driver. > > You'll have to pass both through to the domU, but HDMI audio device > being tainted by the snd-hda-intel driver doesn't seem to break it > completely. > > Gordan > > P.S. > Any particular reason why you left out the list from the recipient list? Sorry, I didn't mean to leave the list out. Your new command is working for me, now I only need to figure out how to blacklist the radeon driver. I can figure that out with the help of Google probably. Thanks so much for your help! I also found that using the format "xl pci-assignable-add 002:0.01" worked for me. When I tried to add the video device that was already bound to the Linux kernel driver I had a segmentation fault, probably because it was already bound to a driver. I tried again after the segmentation fault and get these errors: libxl: warning: libxl_pci.c:654:libxl__device_pci_assignable_add: 0000:02:00.0 not bound to a driver, will not be rebound. libxl: error: libxl_pci.c:350:sysfs_write_bdf: write to /sys/bus/pci/drivers/pciback/bind returned -1: No such device libxl: error: libxl_pci.c:535:pciback_dev_assign: Couldn't bind device to pciback!: No such device libxl: error: libxl_pci.c:659:libxl__device_pci_assignable_add: Couldn't bind device to pciback! I was able to pass the audio device without a problem though so I'm much closer now thanks to your help. I think the reason for the segmentation fault is because I didn't unbind it from the radeon driver first. Because this information was very good and helped me solve my problem I will resend my message to you to the mailing list so others can see it. I'm going to work on trying to configure this more now, I might come back and ask for more help later but for right now you seem to have set me in the right direction. At least I am making progress again! ____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |