[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, Jul 25, 2013 at 9:51 AM, Gordan Bobic <gordan@xxxxxxxxxx> wrote:
On Thu, 25 Jul 2013 09:41:17 -0500, David Sutton <kantras@xxxxxxxxx> 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 successfully
 passing USB, audio, GPU PCI devices using it (as long as I stay under
 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 around
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 iommu=debug,verbose
       module  /boot/vmlinuz-linux /boot/vmlinuz-linux root=/dev/mapper/PhoenixVG00-lvRoot ro console=hvc0 console=tty0 earlyprintk=xen

  (I use Grub2, in EFI mode)

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



Attachment: obsidian.cfg
Description: Binary data

Xen-users mailing list



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