[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] PCI Passthrough, Radeon 7950 and Windows 7 64-bit
The configuration file below resolved my problems. I'm passing through gfx device to Win7 domU (as a secondary device). Interestingly I can reboot the domU without any gfx issues. I'm also now running a custom kernel with pciback built-in, but I don't think that's the solution. I'll do more troubleshooting soon to identify the culprit and share for posterity. Thanks all for the useful discussion and sustained interest -Chris On 6/25/12 3:51 PM, jocelyn falempe wrote: > Hi, > > I've got a similar setup : > > core i7-3770 + ASRock z77 pro 4M > and a sapphire radeon HD7950 > > Ubuntu 12.04 as Dom0, and Win8 release preview as HVM guest. > > I can start my VM multiple time without issue. > as I have 3 USB controller and 2 SATA controller, I use pci passthrough > to pass USB and SATA devices too > so my razer mouse, and secondary sata drive is "native" on windows too. > > here is my script (copied from someone) to reserve the PCI devices for > my HVM : > > remove_device () { > BDF=$1 > # Unbind a PCI function from its driver as necessary > [ ! -e /sys/bus/pci/devices/$BDF/driver/unbind ] || \ > echo -n $BDF > /sys/bus/pci/devices/$BDF/driver/unbind > # Add a new slot to the PCI Backend's list > echo -n $BDF > /sys/bus/pci/drivers/pciback/new_slot > # Now that the backend is watching for the slot, bind to it > echo -n $BDF > /sys/bus/pci/drivers/pciback/bind > } > > #USB Controller : > remove_device "0000:00:1a.0" > #SATA Controller : > remove_device "0000:04:00.0" > #Radeon 7950 > remove_device "0000:01:00.0" > #Radeon 7950 audio > remove_device "0000:01:00.1" > > and here is my .cfg file to launch the VM (xm create win8_lan.cfg) : > cat win8_lan.cfg > kernel="/usr/lib/xen-default/boot/hvmloader" > builder='hvm' > memory = 8096 > vcpus=6 > name = "win8_new" > vif = [ 'type=ioemu, bridge=br0' ] > disk = ['file:/xen-images/win8_2.img,ioemu:hda,w'] > acpi = 1 > boot="c" > sdl=0 > serial='pty' > vnc=1 > pci=[ '00:1a.0', '01:00.0', '01:00.1', '04:00.0' ] > > hope it helps > > Regards, > > Jocelyn > > > On 06/25/2012 05:32 PM, Radoslaw Szkodzinski wrote: >> On Mon, Jun 25, 2012 at 5:21 PM, Matthias >> <matthias.kannenberg@xxxxxxxxxxxxxx> wrote: >>> Maybe you should give xm a try just to see if it does the trick. I >>> never got vga passthrough working with xl (and from my understanding, >>> it's a lot mor complicated there with compiling the vga bios into xen >>> and manual calculating vga adress ranges.. with xm, I'm doing neither >>> of it). >> Why? I'm not using the VGA Passthrough, The card is set up as a >> secondary. >> That shouldn't need any VGA BIOS. Also, it works fine for the first >> boot very well! >> >> The problem occurs on the second start of the same VM. >> >>> Also, do you increase the log level for xen? my kernel line is: >>> multiboot /boot/xen.gz dom0_mem=2048M iommu=1 loglvl=all >>> guest_loglvl=all >> Will do. (except dom0_mem) >> >>> What kernel are you using? If you want i can provide my build commands >>> for the xen-patched openSuse Kernel.. >> I don't want to use the XenLinux kernel. PVOps only please. >> Unless the Xen kernel is actually Pvops-based, in which case why would >> I want to use OpenSUSE one instead of vanilla? >> >> As I've mentioned, vanilla 3.4.1. >> > > > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxx > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |