From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tobias Geiger Subject: Re: Re : Re : Re : Re : Re : Re : Re : Re: Patches for VGA-Passthrough XEN 4.2 unstable Date: Fri, 17 Feb 2012 17:19:59 +0100 Message-ID: <4F3E7E2F.5@vido.info> References: <1319695116310-4942047.post@n5.nabble.com> <1319710499.206.YahooMailNeo@web29804.mail.ird.yahoo.com> <1323123990448-5050354.post@n5.nabble.com> <1323170568.90631.YahooMailNeo@web29813.mail.ird.yahoo.com> <1323504740494-5063848.post@n5.nabble.com> <1323520193389-5064245.post@n5.nabble.com> <1323810239102-5072769.post@n5.nabble.com> <201112141043.45780.tobias.geiger@vido.info> <1329399537084-5489530.post@n5.nabble.com> <201202170934.41725.tobias.geiger@vido.info> <1329478339260-5492208.post@n5.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1329478339260-5492208.post@n5.nabble.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jamesffs Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi James, ah ok - somehow my client didnt display anything in bold, therefore my irritation :) But i'm nearly equally irritated by your Problem(description)... 1st, for reference, here is my xl dmesg output regarding iommu: (XEN) Intel VT-d Snoop Control not enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) I/O virtualisation enabled Yours indicates a few more "not enabled" features, but iirc the only important one here is the last "I/O virtualisation enabled", but dont nail me down on that; Is "01:00.0" the output of "xl pci-list-assignable-devices" ? if not, you have a config/hardware problem you need to solve first. lets assume your hardware is capable and your xen is conf'ed correct (xen cmdline and dom0-kernel cmdline regarding pcipassthrough and iommu) then: after you installed your domu os (i assume here its windows), with gfx_passthrough=0 (so that the cirrus-card gets used as primary within domu), you should see within the qemu-vnc on localhost:5900 (or whereever it listens according to your domu-config), 2 Graphics-devices: one cirrus, working "normaly" and one representing your passed-through card, which is disabled because no device driver is loaded for it. From here on you should be able to normaly install the driver for the card (nvidia/ati-catalyst installer...), and after a reboot, the card should get initialized and bring a picture to the physically connected monitor of the passedtrough card. After all that you can set gfx_passthrough=1 for the pure cosmetic reason that the cirrus card gets removed from the devicemanager (and you therefore only see the qemu-command-console when you vnc to localhost:5900) - but its not necessary at all. Good luck! Greetings Tobias Am 17.02.2012 12:32, schrieb Jamesffs: > Hi Tobias, thank you for the answer. > > The * on my cfg appear because I used bold letter there.(They dont exists on > my real cfg) > > In order to install the driver I need to see the graphic card in my Windows > DomU, so I must passed through the card first right? > So I used the options 'pci = [ '01:00.0' ]' and 'gfx_passthru=1' to > passthru the card, but when I do this (after bind the device with pci-stub) > I just can see (through VNC) a screen with qemu console and after a while > the DomU crash. When u said before that it is not possible to see the DomU > with VNC I thought that I should use a monitor attached to the graphic card > but Im not sure how to do that. > > Anyway Im start thinking that the DomU crash is due to VT-d is not enabled > properly, after using the parameter iommu=1 i have the following output in > xl dmesg: > > (XEN) I/O virtualisation enabled > . > . > (XEN) Intel VT-d Snoop Control not enabled. > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation not enabled. > (XEN) Intel VT-d Interrupt Remapping not enabled. > (XEN) Intel VT-d Shared EPT table not enabled. > > So maybe the problem is there... > > Well thank you for your help > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/Patches-for-VGA-Passthrough-XEN-4-2-unstable-tp4406265p5492208.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel