From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael J Coss Subject: Re: Nvidia, Xen, and Vt-d Date: Mon, 14 Sep 2009 17:31:59 -0400 Message-ID: <4AAEB64F.8010906@alcatel-lucent.com> References: <4AA80A47.9000707@goop.org> <4AA8CAE5.2010804@alcatel-lucent.com> <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F67B@heavy-vm03.heavy.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <14D9C9E2ED61ED41BC3B37ACDF4E880002E0C4B8F67B@heavy-vm03.heavy.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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