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 24

post #231 of 824
absolutely not. For one thing that is 32 bit only (LOL). and i doubt it supports anything around pci pass through

And if you're already running windows why would you want to run an additional windows VM? makes no sense. The idea here is to use a real OS as the host and have windows around in a bastardized state just for what it is _needed for. Now that makes a ton of sense. thumb.gif
stable again
(25 items)
 
  
CPUCPUMotherboardGraphics
E5-2687W E5-2687W ASUS Z9PED8-WS EVGA GTX 570 (Linux host) 
GraphicsRAMHard DriveHard Drive
EVGA GTX 970 FTW (win7 guest) 64GB G.SKILL 2133 2x Crucial M4 256GB raid1 4x 3TB raid 10 
CoolingCoolingCoolingCooling
2x Apogee HD  2x RX 480 2x MCP 655 RP-452x2 rev2 (new) 
CoolingCoolingOSOS
16x Cougar Turbine CFT12SB4 (new) EK FC 580 Gentoo (host) Gentoo (x23 guests) 
OSMonitorMonitorPower
windows 7 (guest w/ vfio-pci) Viewsonic 23" 1080P Viewsonic 19" Antec HCP Platinum 1000 (new) 
CaseOtherOther
Case Labs TH10 (still the best ever) 2x Lamptron FC-5 IOGEAR 2 way DVI KVM Switch 
  hide details  
Reply
stable again
(25 items)
 
  
CPUCPUMotherboardGraphics
E5-2687W E5-2687W ASUS Z9PED8-WS EVGA GTX 570 (Linux host) 
GraphicsRAMHard DriveHard Drive
EVGA GTX 970 FTW (win7 guest) 64GB G.SKILL 2133 2x Crucial M4 256GB raid1 4x 3TB raid 10 
CoolingCoolingCoolingCooling
2x Apogee HD  2x RX 480 2x MCP 655 RP-452x2 rev2 (new) 
CoolingCoolingOSOS
16x Cougar Turbine CFT12SB4 (new) EK FC 580 Gentoo (host) Gentoo (x23 guests) 
OSMonitorMonitorPower
windows 7 (guest w/ vfio-pci) Viewsonic 23" 1080P Viewsonic 19" Antec HCP Platinum 1000 (new) 
CaseOtherOther
Case Labs TH10 (still the best ever) 2x Lamptron FC-5 IOGEAR 2 way DVI KVM Switch 
  hide details  
Reply
post #232 of 824
So. Tested against stock Xen 4.1 under Mint13 as well (extensively).
Xen's infrastructure is much more robust but more work to manage. Where KVM did VGA PCI-passthrough with zero manual configuration (just click and click and click and click, Xen's toolkit is all scattered and bastard-packaged. That said however, both my 69xx and 7xxx worked perfect at bare metal performance. Benched with Heaven DX11 with tessellation on normal, all stock settings, at 1680x1050 and hit 1800 on the bench with the 7850, which is exactly the number I achieved on bare metal.
Played Portal2 for a bit, graphics were smooth but there was an occasional stutter which I believe to be caused by lack of CPU pinning.

NO GODDAMN AUDIO SUPPORT IN XEN!? ***?
Xen apparently stopped compiling qemu-dm for Alsa/Pulse support last year and instead are compiling for only OSS support?
Anyone have working audio (without a spare card) with Xen 4.1?

KVM required some configuration for audio as well, which was surprising. As your guests will run as "libvirt" in Ubuntu/Mint, they cannot access an unmodified PulseAudio server. Have to set the "system" startup in /etc/default/pulse. Seems silly they don't have something in the .deb to add a rule to pulse.
post #233 of 824
Followed this guide and have win7 running successfully on a F17 Xen.

Installed a Radeon HD6850 card, paseed through and it was recognised by windows and installed latest drivers, reboot but greeted with a BSOD with "atikmpag.sys" being the message.
Can now only reboot in safe mode.

Anyone else come across this with their Radeon?

Re CCC - do you install this or only the drivers in a Xen DomU?

Trying to figure out if this is a xen, radeon driver or faulty card issue.

Build:
Asrock Extreme 6 MB
i7 3770 CPU
24GB Ram
120GB HDD
750W PSU
Fedora 17 Dom0
Win7 Ult DomU

Thanks
post #234 of 824
I've run into this heaps of times and I've not found the cause.
I take two identical installs and one will work while the other will not, then miraculously both will work, then one will fail. I'm sure I must be changing something but I haven't yet figured out what.

I did notice however that I've had more consistent success using the xm tools and a native xen-xm config compared to using virt-manager/virsh to create the initial machine.

Here's my working setup

win7.cfg:
##########################################
kernel="/usr/lib/xen-default/boot/hvmloader"
builder='hvm'
memory = 8096
vcpus=6
name = "win7"
vif = [ 'type=ioemu, bridge=br0' ]
disk =
acpi = 1
boot="c"
sdl=0
serial='pty'
vnc=1
pci=[ '06:00.0', '06:00.1' ]
#usb=1
#usbdevice = "host:046d:c048"
###########################################

Use 'xm create win7.cfg' to bring the machine up. This will not add it to your inventory but will boot up (sorry, maybe add a CD drive as well. I have so many installs going now that I've taken to recycling).

Once the machine is up, use 'xtightvncviewer localhost" to view the machine, complete installation, reboot guest, hit it with vnc again, install ati drivers (I use most recent stable). I can't say that I see a definitive correllation between BSOD and CCC installed or not. I've stopped installing it recently (last 4 or 5 builds) and everything's been working. That said however, I've got 3 or 4 others with CCC installed (express install) which work just fine.

Once your machine is happy, you'll want to dump it into your inventory if you're using virt-manager. The official method (domxml-from-native) rarely works as your $xm.cfg has to have a tonne of stuff that is automatically generated on boot. I do it like this instead:

#Bring up the machine with
'xm create win7.cfg'
#Connect to xen with virsh
'virsh -c xen:///'
#Dump the generated XML and exit virsh
'dumpxml win7'
'exit'
#Copy/paste the output to "win7.xml"
#Shutdown the running guest.
'xm destroy win7'
#Define your new machine in Xen/Virsh
'virsh -c xen:///'
'define win7.xml' #NOTE: XML smile.gif
#All done.

If all went well, you'll now see the machine in virt-manager
Also of note, when I bring up a new machine via XML config ripped directly from the XM config, I consistently get a BSOD which is why I'm doing my initial creation and driver installation with an xm.cfg.


Post your config?
Maybe also try booting to safe mode, wipe out the driver, reboot and reinstall driver (without CCC?)
I dunno. I've been up all night babysitting a goddamn VMware snapshot deletion which has left me with about 9 additional hours to my day to hack'n'slash my guests. I might be entirely delirious at this point. Please disregard everything I'm saying and have said.
Edited by blistovmhz - 10/30/12 at 4:57am
post #235 of 824
If I remember correctly (I'm not at home), I'm booting Windows using xm new /etc/xen/win7.cfg (versus xm create ...). I put a shortcut on my desktop and it just works.

Still haven't figured out the difference between xm create and xm new.

In any case, using Linux Mint 13 (Ubuntu-based), I didn't use virt-manager but a script and /etc/modules entry to load pciback and to detach/attach the graphic card etc.

With regard to Nvidia, they still support Linux in proprietary drivers and they are usually damn good. BUT, they are useless for Xen frown.gif. Moreover, very few Nvidia cards support PCI passthrough out of the box. The Nvidia supported cards are specified "Multi-OS".

Next thing - are you trying to pass through your primary (your only) graphics card, or do you have two cards?

I gave up on primary graphics card passthrough. For once, I'm using an Nvidia card (Quadro 2000). That card works perfect under Windows 7 when passing through, but supposedly works under Linux dom0 only with the open source driver. I tried getting a Quadro 600 to work under a Linux dom0 with a proprietary driver but failed. The same card worked perfectly under native Linux Mint 13, just not with the Xen hypervisor.

It seems that ATI cards are generally recommended for use with Xen (plus the Mutli-OS Nvidia cards as secondary cards for pass-through).
post #236 of 824
Quote:
Originally Posted by powerhouse View Post

If I remember correctly (I'm not at home), I'm booting Windows using xm new /etc/xen/win7.cfg (versus xm create ...). I put a shortcut on my desktop and it just works.
Still haven't figured out the difference between xm create and xm new.
In any case, using Linux Mint 13 (Ubuntu-based), I didn't use virt-manager but a script and /etc/modules entry to load pciback and to detach/attach the graphic card etc.
With regard to Nvidia, they still support Linux in proprietary drivers and they are usually damn good. BUT, they are useless for Xen frown.gif. Moreover, very few Nvidia cards support PCI passthrough out of the box. The Nvidia supported cards are specified "Multi-OS".
Next thing - are you trying to pass through your primary (your only) graphics card, or do you have two cards?
I gave up on primary graphics card passthrough. For once, I'm using an Nvidia card (Quadro 2000). That card works perfect under Windows 7 when passing through, but supposedly works under Linux dom0 only with the open source driver. I tried getting a Quadro 600 to work under a Linux dom0 with a proprietary driver but failed. The same card worked perfectly under native Linux Mint 13, just not with the Xen hypervisor.
It seems that ATI cards are generally recommended for use with Xen (plus the Mutli-OS Nvidia cards as secondary cards for pass-through).

Difference between 'xm new' and 'xm create':
xm new = create a new machine and add it to your dom0 inventory
xm create = create and run the specified config, but do not add to inventory.


I haven't tried passthrough on the primary card.

I use options in modprobe to dettach my pci dev like so (saves work, makes easier day to day):
/etc/modprobe.d/xen-pciback.conf
options xen-pciback passthrough=1 hide=(0000:06:00.0)(0000:06:00.1)

Also testing in Mint13.
I haven't got the Nvidia proprietary drivers working with the dom0 yet either, but I was under the impression that was because I borked my module pathing real bad. Will try again today.
post #237 of 824
Quote:
Originally Posted by blistovmhz View Post

Difference between 'xm new' and 'xm create':
xm new = create a new machine and add it to your dom0 inventory
xm create = create and run the specified config, but do not add to inventory.
I haven't tried passthrough on the primary card.
I use options in modprobe to dettach my pci dev like so (saves work, makes easier day to day):
/etc/modprobe.d/xen-pciback.conf
options xen-pciback passthrough=1 hide=(0000:06:00.0)(0000:06:00.1)
Also testing in Mint13.
I haven't got the Nvidia proprietary drivers working with the dom0 yet either, but I was under the impression that was because I borked my module pathing real bad. Will try again today.

Thanks for the explanations. I hope one day I'll remember that.

With regard to adjusting paths in Linux Mint 13, have a look at my how-to (I know, it's lengthy, but you know what you are looking for): http://forums.linuxmint.com/viewtopic.php?f=42&t=112013. Look at Part 3, section 2.

I believe the proprietary Nvidia driver with Xen issue stems from the need to compile the driver into the kernel (at least some compilation is done). Somehow the Xen hypervisor doesn't like the modified kernel, at least that is my impression. Haven't bothered to search for answers, though, just bought a cheap ATI card for dom0.
post #238 of 824
blistovmhz - Thank you!!! Sorted with using your config and xm create command.

It also shows up in virt-manager, no need for the extra commands you specified.
Dom0 card is the onboard iGPU so not trying to pass through a primary card.

Re USB passthrough - usbdevice = "host:046d:c048" where do I find this type of address for the usb devices?

Next: Sort out the data transfer as per posts previously.

post #239 of 824
Quote:
Originally Posted by fergalom View Post

blistovmhz - Thank you!!! Sorted with using your config and xm create command.
It also shows up in virt-manager, no need for the extra commands you specified.
Dom0 card is the onboard iGPU so not trying to pass through a primary card.
Re USB passthrough - usbdevice = "host:046d:c048" where do I find this type of address for the usb devices?
Next: Sort out the data transfer as per posts previously.

bens@octillion ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04cc:1520 ST-Ericsson USB 2.0 Hub (Avocent KVM)
Bus 012 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 013 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 04cc:1520 ST-Ericsson USB 2.0 Hub (Avocent KVM)
Bus 007 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 007 Device 003: ID 046d:c048 Logitech, Inc. G9 Laser Mouse
Bus 001 Device 003: ID 10d5:5552 Uni Class Technology Co., Ltd KVM Human Interface Composite Device (Keyboard/Mouse ports)
Bus 002 Device 003: ID 10d5:5552 Uni Class Technology Co., Ltd KVM Human Interface Composite Device (Keyboard/Mouse ports)
Bus 002 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth

That's the output you're looking for. It's a pain in the ass the virt-manager doesn't yet support adding usb to Xen guests. If you're only running one keyboard/mouse, you're pretty much screwed.
I've found that the VNC display in virt-manager works fine for keyboard and mouse for anything other than gaming. Too much lag for mousing action. I keep a dom0 and domU mouse at all times, but use the vnc window to lock my keyboard to the domU.
You can also simply passthrough the PCI device for a given USB host, in which case all USB ports associated with that PCI device will be available in your domU. I haven't (embarrassingly) been able to figure out how to determine which PCI slot is associated with which USB bus. But when I do....!

Also, if you're running an older ATI card (<7xxx series), I'd give KVM serious consideration. Do some benchmarks between Xen and KVM with your older card. KVM is not as robust but it's tookchain is much more ... organized and I've had no problems with KVM and <7xxx cards. Plus, KVM is built in to pretty near every kernel in the Universe and Mr. Linux is fully behind it.
At this point, I use Xen only when I have performance or support problems with KVM. Were I using an older card (had I known about this, I'd have saved some money and got an older card) I'd be using KVM.
post #240 of 824
Quote:
I haven't (embarrassingly) been able to figure out how to determine which PCI slot is associated with which USB bus. But when I do....!

this I think I can help with

http://www.gossamer-threads.com/lists/xen/users/259868
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