From: Michael J Coss <mjcoss@alcatel-lucent.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Nvidia, Xen, and Vt-d
Date: Mon, 14 Sep 2009 17:31:59 -0400 [thread overview]
Message-ID: <4AAEB64F.8010906@alcatel-lucent.com> (raw)
In-Reply-To: <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F67B@heavy-vm03.heavy.org.uk>
Tim Moore wrote:
> Hi Michael,
>
> I have found that the lspci output changes once you have successfully loaded a driver against it.
>
> In both cases, when used by pci-stub/pciback in DomU or starting X on Dom0 will make the NV card appear differently in the lspci output.
>
> I would try and use the 2.6.18 kernel with the shipped "nv" X driver - I have found this combination to be the most compatible. In the xen-unstable tree, run "make linux-2.6-xen0-build" (from memory).
>
> So far I have only had success with passing through the Primary display adapter, I can`t get my secondary to work.. (I dont think it`s anything to do with the models of card, more that the secondary passthru doesnt work..)
>
> My Pri = GTX260 (512mb+sharedmem=864mb)
> Sec: 9500 GT (512mb)
>
> The main complication and issue that needs to be overcome is the support for FLR. Without this PCIe capability, the GPU cannot be reset after the DomU has initialised it. I have to perform a hard-reset of Dom0 for GPU Passthrough to work a second time.
>
> Tim
>
Just as a follow up to this. I decided before I go back to 2.6.18, to
try the open source "nv" driver instead of the proprietary ones. It
started up the Xserver just fine, although performance for glxgears
dropped through the floor. <100 fps on a GTX 295 with an i7 3.3Ghz
processor ouch. Thanks for all the suggestions.
I'm going to try working with Nvidia to see if I can get them to help
identify the problem, but I don't expect to get very far with that.
Clearly, there is a problem with how they are accessing the card.
---Michael J Coss
next prev parent reply other threads:[~2009-09-14 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 8:47 Nvidia, Xen, and Vt-d Michael J Coss
2009-09-09 8:56 ` Keir Fraser
2009-09-09 20:04 ` Jeremy Fitzhardinge
2009-09-10 9:46 ` Michael J Coss
2009-09-10 10:12 ` Tim Moore
2009-09-14 21:31 ` Michael J Coss [this message]
2009-09-15 7:07 ` Pasi Kärkkäinen
2009-09-09 9:17 ` Pasi Kärkkäinen
2009-09-09 11:26 ` Michael J Coss
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=4AAEB64F.8010906@alcatel-lucent.com \
--to=mjcoss@alcatel-lucent.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.