Overclock.net › Forums › Software, Programming and Coding › Operating Systems › {Guide} Create a Gaming Virtual Machine
New Posts  All Forums:Forum Nav:

{Guide} Create a Gaming Virtual Machine - Page 18

post #171 of 824
Quote:
Originally Posted by Killhouse View Post

1. I'm using an AMD chip with 4 cores, so I would only have 4 threads I believe. I think what I would want to do is impossible: assign all 4 threads to both dom0 and domU and have the clock cycles shared such that a heavy application could run on dom0 constantly, but allow gaming on domU temporarily by sharing CPU time with dom0.
2. The SSD is moot really, its just an LVM for the different doms, no problem there. The issue was my "data" drives which I could only manage to do a software RAID on. Its not an issue, I just unRAIDed them and I'll use them as regular drives. I'll run some sort of automatic backup software on them from dom0. I also install a backup OS on one of the mechanical drives in case of SSD failure - I don't need full usage then, just a simple OS I can log in to to trouble-shoot (it'll probably be Fedora or Windows).
I just wanted to make sure that data was safe. And I'd rather do it in a transparent copy+paste into a file system that I *know* can be opened by Windows, Linux... or any other OS that I can use to retrieve the data in case of my original installs breaking smile.gif
3. I've been trying a few random things with pciback, I will try your links in the next day or so when I'm back home. I ran a script that was meant to detach the graphics driver, make a slot in pciback for it, then attach it to pciback. I don't know if it works, because my screen obviously shuts off after the first line wink.gif I have a feeling that is the script I should be forcing at init, but I'll do some more investigation!
I'm going to try very hard to get around this and end up with a system that switches (full screen) between dom0 and domU, each having total control of the graphics card and therefore the monitor tongue.gif
Thanks for your tremendous help again. +rep!

1. If you have a native Windows installation running, check in Device Manager and see how many threads you got. On Intel I got twice as many threads as cores. Could be Intel-specific, though.

Actually I read today something about oversubscribing vcpus. It makes perfect sense, since I know there are features like queue priority and CPU pinning which only make sense with some sort of floating CPU management. To be perfectly honest, I'n very new to all this and half a year ago I wouldn't have known how to spell Xen, let alone hypervisor.

So, I suggest you check out the Xen.org documentation on vcpus and all the options in the domU config file and xend-config files under /etc/xen. I clearly remember that dom0 should be given dedicated CPU resources to prevent bottlenecks. You could experiment with different settings and see how they work out.

2. If you need to work in Windows, then that is a good option to keep you going when things go wrong. But otherwise use Linux, as you have much more over your system, particularly the ext4 drives and LVM. I'd also keep a bootable live USB stick with your current Linux system handy.

3. That sounds good for a start! Before putting anything in init, I would use remote access via VNC or ssh (-X) to access your machine and see what's going on. I think I posted a link to my how-to for Ubuntu-based systems. You could check there to see what's needed. If you feel comfortable with Fedora, I'm sure you can manage to change the steps to make it work. Unfortunately Fedora and me don't get along very well.

Keep us informed.
post #172 of 824
Quote:
Originally Posted by cladus View Post

VM2-5 will be using remote desktop's on my families computers/laptops and I will use VM1 on the main computer.

Thanks for the explanation. A year ago I've experimented a little with different remote desktop protocols. One thing I noticed is that there are some differences in performance and CPU usage between the protocols. For example using VNC might be just about OK for normal office, web browsing, etc work, but you can forget any video (youtube or VLC) stuff unless you stream VLC from your desktop to the clients. NX is an interesting option but it put a lot of load on my remote machine (perhaps also on the desktop, I can't remember). IIRC the Spice project is also working on a solution, though I haven't tried it.

In essence, any remote desktop solution that works well with CAD-CAM or video editing should be a good starting point. If you haven't got one, I suggest you get a Gigabit router cause 100Mb/s are just not enough in most cases.

By the way I thought about a similar setup to avoid having to deal with all the PCs in the family. I use remote desktop for some time now, either from the desktop to all the PCs or wireless from my Macbook to various PCs. For desktop work it's fine. I haven't tried any game playing as this is most likely not working in my current setup. I've tried video running on the remote and it's not usable.

So, I don't want to discourage you but remote desktop is another thing you will have to look into.
Edited by powerhouse - 9/18/12 at 2:56pm
post #173 of 824
Now that suck, just got offered a 2500k+GA-Z68XP-UD3 for 200$... and now I see that none of it support VT-d...

Why do "k" don't support vt-d, is there a physical reason?
    
CPUMotherboardGraphicsRAM
AMD FX-8320 3.5Ghz @ 3.5ghz Gigabyte 990FXA-UD3 Gigabyte 6850 OC windforce 1GB GDDR5  8GB (2x4GB) G.SKILL RipjawsX F3-12800CL9D-8GBXL 
Hard DriveHard DriveHard DriveCooling
2TB Caviar Green 250GB Hitachi 64GB Crucial M4 Noctua D14 
OSMonitorMonitorMonitor
Linux + Windows 7 64Bits LG Flatron Wide 20.1" 1680x1050 LG Flatron W2442PA 24" 1080p Samsung B2430HD 24 With TV Tuner 1080p 
KeyboardPowerCaseMouse
CM Quickfire Rapid Blue Corsair TX750V2 CM 690 II Logitech G5 
Mouse PadAudio
Steelseries QCK Cloth medium Logitech x-540 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
AMD FX-8320 3.5Ghz @ 3.5ghz Gigabyte 990FXA-UD3 Gigabyte 6850 OC windforce 1GB GDDR5  8GB (2x4GB) G.SKILL RipjawsX F3-12800CL9D-8GBXL 
Hard DriveHard DriveHard DriveCooling
2TB Caviar Green 250GB Hitachi 64GB Crucial M4 Noctua D14 
OSMonitorMonitorMonitor
Linux + Windows 7 64Bits LG Flatron Wide 20.1" 1680x1050 LG Flatron W2442PA 24" 1080p Samsung B2430HD 24 With TV Tuner 1080p 
KeyboardPowerCaseMouse
CM Quickfire Rapid Blue Corsair TX750V2 CM 690 II Logitech G5 
Mouse PadAudio
Steelseries QCK Cloth medium Logitech x-540 
  hide details  
Reply
post #174 of 824
Quote:
Originally Posted by spikexp View Post

Now that suck, just got offered a 2500k+GA-Z68XP-UD3 for 200$... and now I see that none of it support VT-d...
Why do "k" don't support vt-d, is there a physical reason?

It's either been turned off inside the CPU or no code included. Anyway, for all practical purposes, there is no VT-d. And yes, you need VT-d support both in the CPU and the motherboard, unless you try with older CPUs where the memory controller and VT-d is on the board chipset (again, the board must provide it).
post #175 of 824
Quote:
Originally Posted by powerhouse View Post

1. If you have a native Windows installation running, check in Device Manager and see how many threads you got. On Intel I got twice as many threads as cores. Could be Intel-specific, though.
Actually I read today something about oversubscribing vcpus. It makes perfect sense, since I know there are features like queue priority and CPU pinning which only make sense with some sort of floating CPU management. To be perfectly honest, I'n very new to all this and half a year ago I wouldn't have known how to spell Xen, let alone hypervisor.
So, I suggest you check out the Xen.org documentation on vcpus and all the options in the domU config file and xend-config files under /etc/xen. I clearly remember that dom0 should be given dedicated CPU resources to prevent bottlenecks. You could experiment with different settings and see how they work out.
2. If you need to work in Windows, then that is a good option to keep you going when things go wrong. But otherwise use Linux, as you have much more over your system, particularly the ext4 drives and LVM. I'd also keep a bootable live USB stick with your current Linux system handy.
3. That sounds good for a start! Before putting anything in init, I would use remote access via VNC or ssh (-X) to access your machine and see what's going on. I think I posted a link to my how-to for Ubuntu-based systems. You could check there to see what's needed. If you feel comfortable with Fedora, I'm sure you can manage to change the steps to make it work. Unfortunately Fedora and me don't get along very well.
Keep us informed.

1. I think you are talking about Intel Hyperthreading which AMD does not have. Its some sort of virtual threading at the hardware level I believe. I've been reading a little that you can oversubscribe CPUs - using this technique you can run 8 VMs on (for example) 1 core. The VMs will share the CPU time. I'm planning to give dom0 and domU the same 4 cores and let them fight for it. Should work well! Unfortunately, oversubscribing memory is not so trivial (impossible with Xen as far as I can tell) but this isn't such a big issue for me.

2. I decided to put a Linux backup on one mechanical drive and a Windows backup on the other (probably images of the two main VMs).

3. I don't actually know if pciback is installed as a module or... the other option... using the xen-pciback hide tools doesn't work, which makes things a bit more challenging. Hopefully I should have time to play with all this tonight.

Thanks again for your ideas and suggestions. I will check out your how-to and get some more info on VNC/SSH!
PAROXYSM
(13 items)
 
  
CPUMotherboardGraphicsRAM
Phenom x4 II 965 GA-990FXA-UD3 XFX HD 4870 1GB Corsair (12gb) 
Hard DriveHard DriveCoolingOS
2x1TB Caviar Black OCZ Vertex 60gb H50 W7 64-bit / Fedora 17 64-bit 
MonitorKeyboardPowerMouse
V7 22" Logitech Deluxe 250 Antec TruePower 750W Modular Razer Lachesis 
Mouse Pad
None 
  hide details  
Reply
PAROXYSM
(13 items)
 
  
CPUMotherboardGraphicsRAM
Phenom x4 II 965 GA-990FXA-UD3 XFX HD 4870 1GB Corsair (12gb) 
Hard DriveHard DriveCoolingOS
2x1TB Caviar Black OCZ Vertex 60gb H50 W7 64-bit / Fedora 17 64-bit 
MonitorKeyboardPowerMouse
V7 22" Logitech Deluxe 250 Antec TruePower 750W Modular Razer Lachesis 
Mouse Pad
None 
  hide details  
Reply
post #176 of 824
Quote:
Originally Posted by Killhouse View Post

1. I think you are talking about Intel Hyperthreading which AMD does not have. Its some sort of virtual threading at the hardware level I believe. I've been reading a little that you can oversubscribe CPUs - using this technique you can run 8 VMs on (for example) 1 core. The VMs will share the CPU time. I'm planning to give dom0 and domU the same 4 cores and let them fight for it. Should work well! Unfortunately, oversubscribing memory is not so trivial (impossible with Xen as far as I can tell) but this isn't such a big issue for me.
2. I decided to put a Linux backup on one mechanical drive and a Windows backup on the other (probably images of the two main VMs).
3. I don't actually know if pciback is installed as a module or... the other option... using the xen-pciback hide tools doesn't work, which makes things a bit more challenging. Hopefully I should have time to play with all this tonight.
Thanks again for your ideas and suggestions. I will check out your how-to and get some more info on VNC/SSH!

1. You can also give dom0 higher priority. In my setup I give dom0 one CPU core = 2 threads, out of 6 cores = 12 threads. Linux works just fine like that. When I shutdown my Win domU I regain all cores. With the SSD it takes only seconds to shut down Windows, so it's no big deal. Booting takes longer, though, about 20-30 sec. So when I'm ripping DVDs for my media center under Linux I can just give all the CPU power to Linux.

2. I doubt the VMs will be bootable on bare metal. I would give it a try and boot them up to make sure things work. If not, copy (clone) the entire SSD with Xen hypervisor, dom0 and Win domU, check the fstab file and grub files to make sure they address the right drives.

3. You mean xen-pciback hide ... in grub? If it doesn't work it means xen-pciback is not compiled into the kernel. Enter the "xen-pciback passthrough=1" line into /etc/modules. Reboot and check with lsmod | grep pciback to see the module is loaded.

IIRC you have 2 graphics cards? If yes you can run the pciback script to detach the secondary graphics card. Check with xm pci-list-attachable-devices to see the PCI IDs you want to pass through. The next step is to run the domU with xm new /etc/xen/win7.cfg and virt-manager or just xm create /etc/xen/win7.cfg and connect to it via VNC.

In any case, it's much easier to passthrough a secondary graphics card, as long as it supports VGA passthrough. A range of AMD cards are good for that. In case of Nvidia you need to stick to "multi-OS" cards such as the Quadro 2000 (I have) or even more expensive Quadro 4000 etc. cards.
post #177 of 824
Thread Starter 
Hey all!

First off: A big sorry for being away for so long mad.gif

I am mad at myself too, but life happens.

Anyway I am back now, and will start working on a new version of the guide with the revised 4.1.3 Hypervisor and a more lightweight dom0. Good news is that my system is still 100% stable and runs 24/7 thumb.gif

Expect updates soon!

Thank you all for adding to the thread while I was away +rep
Test Chamber ITX
(14 items)
 
Dream Rig (AMD)
(11 items)
 
Dream Rig (Intel)
(11 items)
 
CPUMotherboardGraphicsRAM
i7-2600 Gigabyte H77N-wifi Radeon HD 7750 16GB Corsair DDR3 1600 CL 10 (@1333 CL 8) 
Hard DriveHard DriveOSPower
Corsair Force 3 180gb Seagate Barracuda STBD2000101 2x in RAID1 Lubuntu / Win 8.1 / CentOS 6.4 -- Xen 4.3 FSP 80+ Micro-ATX 450w 
Case
Fractal Node 304 
CPUMotherboardGraphicsGraphics
AMD FX-8350 ASRock Fatal1ty 990FX Professional Sapphire Radeon HD 7970 GHz Edition 3GB AMD FirePro W5000 
RAMHard DriveHard DriveCooling
G.Skill Trident X Series 32GB (4 x 8GB) DDR3-1866 Seagate Barracuda 1TB 3.5" 7200RPM x2 RAID 1 Corsair Force Series GT 120GB x2 RAID 0 NZXT Kraken X60 
PowerCaseOther
SeaSonic Platinum 860W 80 PLUS Platinum Lian-Li PC-100 (Black) ATX Mid Tower Case RaspberryPi 
CPUMotherboardGraphicsGraphics
i7-3930k ASrock X79 EXTREME4-M SAPPHIRE Radeon HD 7870 GHz Edition 2GB  AMD FirePro W5000 
RAMHard DriveHard DriveCooling
G.Skill Ripjaws Z Series 32GB (4 x 8GB) DDR3-1866 2x Corsair Force Series 3 180GB RAID 0 2x Western Digital Red 2TB RAID 1 Noctua NH-D14 SE2011 
PowerCaseOther
SeaSonic 660W 80 PLUS Platinum Silverstone TJ08B-E Integrated RaspberryPi 
  hide details  
Reply
Test Chamber ITX
(14 items)
 
Dream Rig (AMD)
(11 items)
 
Dream Rig (Intel)
(11 items)
 
CPUMotherboardGraphicsRAM
i7-2600 Gigabyte H77N-wifi Radeon HD 7750 16GB Corsair DDR3 1600 CL 10 (@1333 CL 8) 
Hard DriveHard DriveOSPower
Corsair Force 3 180gb Seagate Barracuda STBD2000101 2x in RAID1 Lubuntu / Win 8.1 / CentOS 6.4 -- Xen 4.3 FSP 80+ Micro-ATX 450w 
Case
Fractal Node 304 
CPUMotherboardGraphicsGraphics
AMD FX-8350 ASRock Fatal1ty 990FX Professional Sapphire Radeon HD 7970 GHz Edition 3GB AMD FirePro W5000 
RAMHard DriveHard DriveCooling
G.Skill Trident X Series 32GB (4 x 8GB) DDR3-1866 Seagate Barracuda 1TB 3.5" 7200RPM x2 RAID 1 Corsair Force Series GT 120GB x2 RAID 0 NZXT Kraken X60 
PowerCaseOther
SeaSonic Platinum 860W 80 PLUS Platinum Lian-Li PC-100 (Black) ATX Mid Tower Case RaspberryPi 
CPUMotherboardGraphicsGraphics
i7-3930k ASrock X79 EXTREME4-M SAPPHIRE Radeon HD 7870 GHz Edition 2GB  AMD FirePro W5000 
RAMHard DriveHard DriveCooling
G.Skill Ripjaws Z Series 32GB (4 x 8GB) DDR3-1866 2x Corsair Force Series 3 180GB RAID 0 2x Western Digital Red 2TB RAID 1 Noctua NH-D14 SE2011 
PowerCaseOther
SeaSonic 660W 80 PLUS Platinum Silverstone TJ08B-E Integrated RaspberryPi 
  hide details  
Reply
post #178 of 824
Quote:
Originally Posted by dizzy4 View Post

Hey all!
First off: A big sorry for being away for so long mad.gif
I am mad at myself too, but life happens.
Anyway I am back now, and will start working on a new version of the guide with the revised 4.1.3 Hypervisor and a more lightweight dom0. Good news is that my system is still 100% stable and runs 24/7 thumb.gif
Expect updates soon!
Thank you all for adding to the thread while I was away +rep

Good to see you back - I already felt hitchhiking your thread. I look forward to the new guide. And thanks for sharing your experience with running it 24/7.

Some questions: People have been asking about over-provisioning vcpus. I myself am not certain about it, but it seems Xen is providing virtual CPUs to the dom0 and domUs. From the Xen webpages I gather that it's good practice to pin some vcpus or core(s) to dom0. Another way of ensuring that dom0 gets enough resources is to increase it's priority for processor time. Any experience with this or suggestions?

Memory ballooning: This is another feature of Xen. However, it is suggested to disable ballooning and use fixed memory for dom0 and domUs since Linux supposedly isn't good at dealing with changing memory sizes. Any experience with that?

I found it difficult to find a good source on VGA passthrough supported graphics adapters. The Xen wiki pages http://wiki.xen.org/wiki/Xen_VGA_Passthrough and http://wiki.xen.org/wiki/Xen_VGA_Passthrough_Tested_Adapters seem pretty much outdated or incomplete. I would like to compile a list of graphics adapters have been successfully passed through as either primary or secondary adapters, with notes on the Xen hypervisor and kernel used. I will add a link here to the new thread. Help is greatly appreciated.

Here is the link to the VGA passthrough enabled graphics adapters list: http://www.overclock.net/t/1307834/xen-vga-passthrough-compatible-graphics-adapters. Please post your successfully passed through adapters there.
Edited by powerhouse - 9/20/12 at 12:10am
post #179 of 824
Thread Starter 
Overprovisioning CPUs is really not a good idea. I tried it with a domU running win7 and then I booted my win8 preview. I gave each of them 5 CPUs and the result was horrendous. With any load on the win8 domU simple tasks like streaming video from netflix to the win7 domU were choppy. Not to my surprise dom0 was also very slow and almost unresponsive. I tried assigning the dom0 its own cpu thread not used by either domU. It helped some, but the domU systems were still somewhat glitchy. Remember these are HVM domUs so you are actually assigning physical threads from your CPU. However, with only one HVM domU I assume there could be one or many other paravirtual domUs existing.

On to memory... Do not overprovision or balloon it! Errors will occur in your domU and your dom0. Once again I think this is something to be reserved for paravirtual machines. (I have seen it used in Xen VPS node setups)

I would stick to HD radeon cards for now. I think they patched it for nvidia but I can't confirm it until later. If not I will attempt to patch it for you nvidia guys.
Edited by dizzy4 - 9/20/12 at 12:09am
Test Chamber ITX
(14 items)
 
Dream Rig (AMD)
(11 items)
 
Dream Rig (Intel)
(11 items)
 
CPUMotherboardGraphicsRAM
i7-2600 Gigabyte H77N-wifi Radeon HD 7750 16GB Corsair DDR3 1600 CL 10 (@1333 CL 8) 
Hard DriveHard DriveOSPower
Corsair Force 3 180gb Seagate Barracuda STBD2000101 2x in RAID1 Lubuntu / Win 8.1 / CentOS 6.4 -- Xen 4.3 FSP 80+ Micro-ATX 450w 
Case
Fractal Node 304 
CPUMotherboardGraphicsGraphics
AMD FX-8350 ASRock Fatal1ty 990FX Professional Sapphire Radeon HD 7970 GHz Edition 3GB AMD FirePro W5000 
RAMHard DriveHard DriveCooling
G.Skill Trident X Series 32GB (4 x 8GB) DDR3-1866 Seagate Barracuda 1TB 3.5" 7200RPM x2 RAID 1 Corsair Force Series GT 120GB x2 RAID 0 NZXT Kraken X60 
PowerCaseOther
SeaSonic Platinum 860W 80 PLUS Platinum Lian-Li PC-100 (Black) ATX Mid Tower Case RaspberryPi 
CPUMotherboardGraphicsGraphics
i7-3930k ASrock X79 EXTREME4-M SAPPHIRE Radeon HD 7870 GHz Edition 2GB  AMD FirePro W5000 
RAMHard DriveHard DriveCooling
G.Skill Ripjaws Z Series 32GB (4 x 8GB) DDR3-1866 2x Corsair Force Series 3 180GB RAID 0 2x Western Digital Red 2TB RAID 1 Noctua NH-D14 SE2011 
PowerCaseOther
SeaSonic 660W 80 PLUS Platinum Silverstone TJ08B-E Integrated RaspberryPi 
  hide details  
Reply
Test Chamber ITX
(14 items)
 
Dream Rig (AMD)
(11 items)
 
Dream Rig (Intel)
(11 items)
 
CPUMotherboardGraphicsRAM
i7-2600 Gigabyte H77N-wifi Radeon HD 7750 16GB Corsair DDR3 1600 CL 10 (@1333 CL 8) 
Hard DriveHard DriveOSPower
Corsair Force 3 180gb Seagate Barracuda STBD2000101 2x in RAID1 Lubuntu / Win 8.1 / CentOS 6.4 -- Xen 4.3 FSP 80+ Micro-ATX 450w 
Case
Fractal Node 304 
CPUMotherboardGraphicsGraphics
AMD FX-8350 ASRock Fatal1ty 990FX Professional Sapphire Radeon HD 7970 GHz Edition 3GB AMD FirePro W5000 
RAMHard DriveHard DriveCooling
G.Skill Trident X Series 32GB (4 x 8GB) DDR3-1866 Seagate Barracuda 1TB 3.5" 7200RPM x2 RAID 1 Corsair Force Series GT 120GB x2 RAID 0 NZXT Kraken X60 
PowerCaseOther
SeaSonic Platinum 860W 80 PLUS Platinum Lian-Li PC-100 (Black) ATX Mid Tower Case RaspberryPi 
CPUMotherboardGraphicsGraphics
i7-3930k ASrock X79 EXTREME4-M SAPPHIRE Radeon HD 7870 GHz Edition 2GB  AMD FirePro W5000 
RAMHard DriveHard DriveCooling
G.Skill Ripjaws Z Series 32GB (4 x 8GB) DDR3-1866 2x Corsair Force Series 3 180GB RAID 0 2x Western Digital Red 2TB RAID 1 Noctua NH-D14 SE2011 
PowerCaseOther
SeaSonic 660W 80 PLUS Platinum Silverstone TJ08B-E Integrated RaspberryPi 
  hide details  
Reply
post #180 of 824
Quote:
Originally Posted by dizzy4 View Post

Overprovisioning CPUs is really not a good idea. I tried it with a domU running win7 and then I booted my win8 preview. I gave each of them 5 CPUs and the result was horrendous. With any load on the win8 domU simple tasks like streaming video from netflix to the win7 domU were choppy. Not to my surprise dom0 was also very slow and almost unresponsive. I tried assigning the dom0 its own cpu thread not used by either domU. It helped some, but the domU systems were still somewhat glitchy. Remember these are HVM domUs so you are actually assigning physical threads from your CPU. However, with only one HVM domU I assume there could be one or many other paravirtual domUs existing.
On to memory... Do not overprovision or balloon it! Errors will occur in your domU and your dom0. Once again I think this is something to be reserved for paravirtual machines. (I have seen it used in Xen VPS node setups)
I would stick to HD radeon cards for now. I think they patched it for nvidia but I can't confirm it until later. If not I will attempt to patch it for you nvidia guys.

Wow, thanks for the speedy reply.

CPU over-provisioning: I didn't know that HVM guests would get physical cores or threads. I've also never experimented with PV guests versus HVM guests, or a mix of it. Well, I assume my Linux dom0 is sort of a PV guest, isn't it? I should do some experimenting to see how multiple PV or HVM guests work together.
Have you tried increasing the dom0 CPU priority? I think it's the queue priority for CPU time. I've increased my dom0 priority but don't notice any difference, but then I never had any issue with starving CPU resources (I use 2 threads for dom0 when running the Windows HVM guest with 10 threads). The nice thing is that when closing Windows I get the full 12 threads for my dom0 (at least that's what my system monitor shows me - never done any benchmarking though).

Memory: Thanks for the advise. I will disable ballooning now. With 32GB memory I don't see much need for it anyway.

Graphics cards: I've opened a thread under the graphics cards hardware section (see link in previous post). Would you be able to share your experience with specific AMD cards? I know that AMD has generally better support for VGA passthrough, but I guess not all AMD cards are equal. I've posted the specs for my Nvidia Quadro 2000 card which works just perfect under the Windows HVM guest, using the latest Nvidia Windows driver for the card. See other thread for details.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Operating Systems
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › {Guide} Create a Gaming Virtual Machine