xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gordan Bobic <gordan@bobich.net>
To: therion@ninth-art.de
Cc: xen-devel@lists.xensource.com
Subject: Re: Fwd: Re:  Xen 4.3 / 4.4 - concurrent APIs, VGA Passthru
Date: Sun, 03 Aug 2014 10:40:09 +0100	[thread overview]
Message-ID: <53DE0379.1080005@bobich.net> (raw)
In-Reply-To: <53DD8BCB.1090202@ninth-art.de>

On 08/03/2014 02:09 AM, Georg Bege wrote:
> Hi
>
> I tried your suggestions now with Xen 4.3.2-r4 (Gentoo).
> On Win7 64bit its not working at all, I cannot passthru the GFX -
> I rolled back to a snapshot where I installed everything but not the
> nvidia package.

Just to clarify - which suggestion is that?

> So I tried it and it works out, reboots and then I get a message like:
> "This device reported an error and had to be stopped, code 43."
> within the device manager.
> This happens whether Im trying the DomU with 8GB or 1024MB - same results.
> On Xen 4.4 I can passthru the GFX, no problem but its very slow (as I've
> written already).

Have you tried an older Nvidia driver? I'm running the latest 331.x 
driver on both XP and Win7 (both x64).

The slowness might be indicative of an interrupt related problem. The 
boot parameters I'm running with are as follows:

xen.gz: dom0_vcpus_pin iommu=dom0-passthrough unrestricted_guest=1 msi=1
vmlinuz: intel_iommu=on pcie_aspm=off pcie_ports=compat

Note: The pcie_aspm=off pcie_ports=compat are to work around a bug on my 
motherboard that causes a massive interrupt flood due to a device on 
ICH10 flapping between hotplug states and creating an interrupt storm 
that makes the entire machine permanently unusable as soon as the kernel 
starts probing devices. You probably don't need those two options but 
they shouldn't do any harm while you're troubleshooting.

Gordan

      reply	other threads:[~2014-08-03  9:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53D5C00E.5040706@ninth-art.de>
2014-07-28 14:10 ` Fwd: Re: Xen 4.3 / 4.4 - concurrent APIs, VGA Passthru Georg Bege
2014-07-28 14:34   ` jacek burghardt
2014-07-28 15:01   ` Gordan Bobic
     [not found]     ` <53D6F500.1010806@ninth-art.de>
     [not found]       ` <53D748DC.10209@bobich.net>
     [not found]         ` <53D74F9E.6010508@ninth-art.de>
     [not found]           ` <bb4d5eb4f453e5596f696eb93c3f7df5@mail.shatteredsilicon.net>
2014-07-29 11:52             ` Georg Bege
2014-07-29 12:22               ` Gordan Bobic
2014-08-02 10:49                 ` Georg Bege
2014-08-03  9:49                   ` Gordan Bobic
     [not found]                     ` <53DE0A73.9040304@ninth-art.de>
2014-08-03 10:20                       ` Fwd: " Georg Bege
2014-08-04  8:18                       ` Gordan Bobic
2014-08-04 19:30                         ` Georg Bege
2014-08-18 15:26                         ` Georg Bege
2014-08-18 15:45                           ` Gordan Bobic
2014-08-18 21:13                             ` Richie
2014-08-19 10:31                               ` Gordan Bobic
2014-08-03  9:57                   ` James Harper
2014-08-03  1:09             ` Georg Bege
2014-08-03  9:40               ` Gordan Bobic [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53DE0379.1080005@bobich.net \
    --to=gordan@bobich.net \
    --cc=therion@ninth-art.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).