From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Tramnitz Subject: Re: graphics passthrough with VT-d Date: Fri, 04 Sep 2009 12:25:46 +0200 Message-ID: References: <715D42877B251141A38726ABF5CABF2C054B533D27@pdsmsx503.ccr.corp.intel.com> <715D42877B251141A38726ABF5CABF2C054B533D81@pdsmsx503.ccr.corp.intel.com> <715D42877B251141A38726ABF5CABF2C054B5B3F96@pdsmsx503.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: 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 It seems this was unrelated to the gfx_passthrough, I started with "fresh" domU configs and also reinstalled them and now its working WITH gfx_passthrough and USB (the whole controller as pci device) passthrough. I do have (all as pass-through): - accelerated video (even survives hardware detection during Win7 installation) - audio (onboard HDA, using digital output) - USB (UHCI only, EHCI crashed Windows during HW detection) running Windows 7 x64 (b7600). I'll now try to swap the primary and secondary gfx (both ATI) to get some real 3D horse-power. Best regards, Christian Christian Tramnitz wrote: > Yes without gfx_passthrough it was working (even the same domU with just > USB devices passed through). > I think it might be related to the modifications to the memory addresses > you mentioned in another post. > I'll verify that, recompile and retest.