This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] xl and GFX passthrough

To: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Subject: Re: [Xen-devel] xl and GFX passthrough
From: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Date: Wed, 26 Jan 2011 10:01:25 -0500
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Sergey Tovpeko <tsv.devel@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 26 Jan 2011 07:03:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <987664A83D2D224EAE907B061CE93D53019434A445@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: National Security Agency
References: <4D2EC20D.2050603@xxxxxxxxx> <1294910794.8240.9.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D2ECE5A.8070807@xxxxxxxxx> <1294914282.8240.38.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D2EDF65.6080002@xxxxxxxxx> <987664A83D2D224EAE907B061CE93D53019434A445@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc13 Thunderbird/3.1.7
On 01/25/2011 09:49 PM, Kay, Allen M wrote:
> Sergey,
> Did you get gfx_passthru to work with xl?  I found the latest source still 
> does not seems to pass gfx_passthru to qemu correctly.
> By the way, how to output debug messages to xl*.log file?  I tried LOG() and 
> fprintf(stderr...) neither worked for me.
> Allen
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Sergey Tovpeko
> Sent: Thursday, January 13, 2011 3:18 AM
> To: Ian Campbell; Daniel De Graaf
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] xl and GFX passthrough
>> I just noticed that this appears to have been fixed by Daniel De Graf
>> just a few days ago, see 22711:4f6fee3a456e, which may only be in the
>> staging tree at http://xenbits.xen.org/staging/xen-unstable.hg since we
>> are waiting for a test pass.
> Ian, Daniel
>   my patch is almost like Daniel's one.  Thank you for pointing to it.
> And there's one absent thing in Daniel's commit (4f6fee3a456e). To 
> complete the gfx passthrough issue for xl we should pass this option to 
> qemu-dm, like this :
> +        if (info->gfx_passthru) {
> +            flexarray_set(dm_args, num++, "-gfx_passthru");
> +            flexarray_set(dm_args, num++, libxl__sprintf(gc, "%d", 
> info->gfx_passthru));
> +        }
> I suppose, without it 'qemu-dm' won't  know about gfx_passthru mode and 
> won't load passthru'ed vga bios.
> Daniel might plan to add this code or added it already?

Actually, I hadn't noticed that gfx_passthru takes an (apparently optional)
numeric parameter. This change is more correct than the one I posted,
although it also needs gfx_passthru to be changed from bool to int in the
IDL (assuming that -gfx_passthru 2 is still useful, I hadn't heard of it
until recently).

Kay: sounds like you have this fixed in your tree, I'll let you or Ian
fix it.

Daniel De Graaf
National Security Agency

Xen-devel mailing list