[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] [Xen-devel] Intel HD Graphics 4600 Xen VGA Passthrough to Windows 7 Ultimate HVM domU

On Thu, 25 Jul 2013 10:14:41 -0500, David Sutton <kantras@xxxxxxxxx> wrote:
On Thu, Jul 25, 2013 at 9:51 AM, Gordan Bobic  wrote:

On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton  wrote:

 On Thu, Jul 25, 2013 at 4:20 AM, Gordan Bobic Âwrote:

 On Thu, 25 Jul 2013 12:07:25 +0300, Pasi KÃrkkÃinen Âwrote:

 Â On Thu, Jul 25, 2013 at 08:58:58AM +0000, Ren, Yongjie wrote:
 Â > > N.B. I didn't use the latest traditional qemu because of the
 following bug:
 Â> >


 Â> >
 Â> Hmm.. isn't that bug affecting qemu-traditional in general, not
 Â> passthru specifically?
 Â> Or is it *only* PCI/GPU passthru that it breaks for you?
 ÂIt's a general device assignment issue.
 ÂAny PCI device can't be assigned to a HVM guest with the latest

 ÂOk. Is there already a separate thread on xen-devel about the
 Âqemu-traditional PCI assignment issue?
 ÂIf not, we should create one.

 ÂFWIW, I'm using qemu-dm (i.e. traditional) in 4.3 and am
 Âpassing USB, audio, GPU PCI devices using it (as long as I stay
 Âthe 2GB domU RAM limit). So whatever the issue is it isn't generic.

 ÂThat bug report doesn't include the domU config file, and IIRC
 ÂI saw a similar error when device_model/device_model_override and
 Âdevice_model_version don't match or are unavailable in the build
 Â(e.g. building without upstream and specifying traditional or
 Âvice versa). More info needed to verify, I think.

 And just to add a little more variety, I'm also using traditional
 (under 4.3) to pass through USB and GPU (Radeon 6770) to a Windows 7
 DomU configured with 6Gb for memory. Only using a patch to work
 a broken BIOS implementation so I have IOMMU support.

 And you don't suffer from a memory stomp resulting
 in frame buffer corruption shortly followed by a domU
 crash with that much RAM passed to domU?

 No, its been stable; I tend to use that VM for gaming and for
management of an XCP instance. I even have CCC installed, so I can use
overscan. Everything I've used on it (Defiance, Skyrim, Oblivion,
Borderlands just to name a few) work without issue. I've included the
config file I use to start it.

 For booting the hypervisor and Dom0, the options I use are:

ÂÂÂÂÂÂ multibootÂÂÂÂÂÂ /boot/xen-4.3.0.gz
/boot/xen-4.3.0.gz dom0_mem=4096M,max:4096M dom0_max_vcpus=3
loglvl=all guest_loglvl=all apic_verbosity=debug e820-verbose=1
  module /boot/vmlinuz-linux /boot/vmlinuz-linux
root=/dev/mapper/PhoenixVG00-lvRoot ro console=hvc0 console=tty0

 (I use Grub2, in EFI mode)

 Â Specs: ASUS Sabertooth 990FX, AMD 8350, 24Gb RAM, Radeon 6770,
Radeon 7750.

Interesting. The config looks pretty much identical to mine, but mine
works fine for hours with a 2GB domU and crashes pretty much instantly
when firing up a 3D app with > 2GB given to domU. The only difference
is that I have no limiting on dom0 RAM/CPU, but I cannot see that
being the root cause of the problem; still, will try it tonight and
see if it makes a difference.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.