All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Zhou Peng <zpengxen@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH v14] libxl: Add qxl vga interface support for upstream qemu
Date: Wed, 25 Sep 2013 14:49:02 +0200	[thread overview]
Message-ID: <5242DBBE.6080509@m2r.biz> (raw)
In-Reply-To: <1380111624.23688.128.camel@kazak.uk.xensource.com>

Il 25/09/2013 14:20, Ian Campbell ha scritto:
> On Mon, 2013-09-23 at 17:17 +0200, Fabio Fantoni wrote:
>> Usage:
>>    vga="qxl"
>>
>> Changes from v13:
>> - refresh
>> - update qemu parameters (from -vga to -device)
>>
>> NOTE:
>> Seems needed other changes/fixes on xen side before
>> have it full working.
> IIRC last time we applied this we reverted for the release because the
> Xen side was broken, so I don't think we can take this yet. Please
> resend once the Xen side stuff has been figured out.
>
> Ian.
>

Yes, I know, I posted it only if someone want use it for fast testing.
Now I'm trying to found the exact problem basing of Gerd Hoffmann reply.
I'll post when I'll found all details but seem problem of xen static 
memory mapping, probably the problem is not only with qxl but probably 
also vgas and pci/vgas passthrough can have similar problems in some cases.
I have a small question about qemu debug, based on the commit 
8e4610ec55751c3d1a4f515ba4041ca6faa16d15 should be enabled and also on 
build logs seem ok but on qemu log of domUs seem not enabled, I need to 
add something else on domU start that I not see?
Thanks for any reply and sorry for my bad english.

  reply	other threads:[~2013-09-25 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23 15:17 [PATCH v14] libxl: Add qxl vga interface support for upstream qemu Fabio Fantoni
2013-09-25 12:20 ` Ian Campbell
2013-09-25 12:49   ` Fabio Fantoni [this message]
2013-09-26  7:52     ` Dario Faggioli
2013-09-26  8:20       ` Fabio Fantoni

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=5242DBBE.6080509@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=zpengxen@gmail.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.