No monitor is plugged in to it at the moment so we will see when I get home if it works when I plug the monitor in. I was playing with it a bit here from work and for giggles I enabled the ATI card and it didn't BSOD.
So far I have the ATI 5450 video card passed through a windows 7 vm (both HDMI & Video passed, 2GB ram assigned to the VM) and last night any time I tried to enable the card it would BSOD. I would love to roll my Windows 7 HTPC into this box as it is currently about 4 feet from the TV. OpenSolaris/Napp-it VM with 8 port LSI SATA card passed through
Right now I have my VM host as ESX 5 with 16GB ram Working VGA passthrough is my holy grail for my home virtual server setup. Thankfully I have PV passthrough to fallback on, but that's not an option for VMWare people. I think there're just general problems with Intel VT-d I see people passing through all sorts of stuff on AMD no problem, for me hardware passthrough with an i5-2400 on a Q67 chipset has been hit and miss.
If you do it right xen-pciback is what shows up as the driver when you list lspci -vvv. I had to blacklist the original module responsible for the device on dom0, or I guess you could probably manually unbind like you're doing it. You can use xen-pciback to passthrough stuff to PV domUs, you'll have to put that stuff in /etc/modprobe.d/ though. My guess is if you remove that stuff from grub it'll still work, I don't think it does anything. You're using pci-stub which is different. Check your dmesg it could be complaining that it doesn't know what you're asking it to do with that, but, regardless, that's not the driver you're using for passthrough. Typically in 2.6.x specific xen kernels xen-pciback is compiled in so grub command line is how you pass options to it, but I see you're using 3.1 upstream where it's a module. The stuff you added to grub kernel command line - that's xen-pciback driver and you're using pci-stub. The only way for usb or mouse is whole USB3 controller passtrough, no time for dealing with USB over network or USB 1.0 emulation by qemu The only bad thing is 30MB/s between vm even pv driver My nas is pure rockstable SSH, no vnc ! It uses 3 Mo of ram and deserve my Windows by NFS.I give to my nas 6 GB of ram for insane ram cahing. Nothing else is changed, no modprobe blablah launch your VM with xm create MyVM.cf and monitor it with xm top see screen below : my windows get an HD5850, a xonar 2 and nec USB 3, my nas on freebsd get the whole SATA controller in raidzġ0.a hide all pci used from dom0 OS (see first screen)ġ0b. put config files in /etc/xen/MyVM.cfg like on screen belowĩ. hide your pci card in /etc/default/grub : list what u want to passtrough with lspci and lspci -nĥ.
install xen package and only that, no virtmanager, python bla blah blahĤ. Install Debian 6.0.4 stable and no other OS (i have 6.0.3 testing, so it is the same)Įdit : use testing package, to get xen 4.1.2 and linux 3.1.0 or newerģ. Check out Vt-d or IOMMU option in your biosĢ.
Ok, first it is great that you are interested, i'll post below what is needed.I plan to make a blog,but lack of time.įirst you need to have some basic linux experiment.ġ. Please understand that my english is buggy like a windows millenium, dont know if you undertsand what i say but bi-gpu ? I think yes, need money and time crossfire may not working, since the VM dont see the chipset you can run 2 windows and 2 card, 1 windows = 1 card BF3 is not launching, but it need a crapy dll fixe, no time for that perfs are native, Windows see the true card, ther is no emulation, I doesnt encoutered any Vt-d relative bug
If Windows crash, i have to bring another PC and make some ssh comand to reboot the VM I have only 1 GPU, so once the GPU is passed trough, the only way to manage my hypervisor is distant ssh. If your GPU is crashing, the main OS (xen) is not affected. New asus board should be good, you have to If your virtual machine crashes your hypervisor is not affected On x79 it should be OK, but i think you should use an Intel board to be sure. As you can see I use PV driver, my average ping on BF2 is 20 x58, it is working on gigabyte and Intel Board, Asus has a bios that enable Vt-d but it is buggy Native ! now disk and network can suffer if not optimised.