From: Dario Faggioli <dario.faggioli@citrix.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: ehouby@yahoo.com, xen@lists.fedoraproject.org,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: [TestDay] F20 Xen 4.4 RC3 Spice support
Date: Fri, 7 Feb 2014 10:08:59 +0100 [thread overview]
Message-ID: <1391764139.9917.54.camel@Solace> (raw)
In-Reply-To: <CABMPFzgwkc7RVakyTGTZZMkepQn5ENhsw-H8hAx78g4nxkwk9Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2272 bytes --]
On gio, 2014-02-06 at 08:35 +0100, Fabio Fantoni wrote:
> 2014-02-06 5:23 GMT+01:00 Eric Houby <ehouby@yahoo.com>:
> Is there a knob for qxl support?
>
> [root@xen ~]# cat /var/log/xen/qemu-dm-f20.log
> qemu-system-i386: -vga qxl: invalid option
>
>
> Here there is a patch that add qxl support in libxl updated to xen
> 4.4-rc3 if you want add it:
> https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
>
> Or you can simply compile from this already ready for spice/qxl
> testing:
> https://github.com/Fantu/Xen/commits/rebase/m2r-testing
>
>
>
> Is not upstream for now because there is something on xen that make it
> not working on linux domUs with qxl driver active and working with
> high performance problem on windows domUs.
>
Right.
> I spent several days without finding the exact problem to be solved :(
> If you want you can try it out and see if anything changes using
> Fedora instead of Debian as dom0, differents kernel domUs etc.
> Maybe you could even find some new informations/errors useful for
> solving the problem.
>
Yep, that would help... let us know! :-)
Anyway, first of all, sorry for my spice/qxl ignorance.
What I just wanted to say is this: searching the wiki, all I found about
spice and QXL is this section in the QEMU Upstream page:
http://wiki.xen.org/wiki/QEMU_Upstream#SPICE_.2F_QXL
Perhaps someone of you can double check whether the information there is
still fresh and accurate enough? Perhaps it's also worth adding
references to the patches mentioned above (with the proper disclaimer
about the known issues, of course)?
Also, maybe for the next DocsDay, this would be a nice one to have too:
http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Spice_Config_Example_for_upstream_QEMU
If keen on doing any of the above that involves modifying the wiki, send
me a note, and I think I can provide the necessary permissions.
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-02-07 9:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 15:41 [TestDay] F20 Xen 4.4 RC3 Spice support Eric Houby
2014-02-04 16:01 ` Fabio Fantoni
2014-02-05 4:00 ` Eric Houby
2014-02-05 8:06 ` Sander Eikelenboom
2014-02-06 0:17 ` Eric Houby
2014-02-06 4:23 ` Eric Houby
2014-02-06 7:35 ` Fabio Fantoni
2014-02-07 5:03 ` Eric Houby
2014-02-07 7:23 ` Fabio Fantoni
2014-02-07 9:08 ` Dario Faggioli [this message]
2014-02-07 10:52 ` Fabio Fantoni
2014-02-07 23:37 ` Eric Houby
2014-02-08 8:56 ` Fabio Fantoni
2014-02-06 0:30 ` Dario Faggioli
2014-02-10 17:05 ` George Dunlap
2014-02-11 9:56 ` Fabio Fantoni
2014-03-13 14:47 ` Fabio Fantoni
2014-04-10 12:26 ` Fabio Fantoni
2014-04-10 16:21 ` George Dunlap
2014-04-11 7:52 ` Fabio Fantoni
2014-04-11 11:55 ` George Dunlap
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=1391764139.9917.54.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=ehouby@yahoo.com \
--cc=fabio.fantoni@m2r.biz \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.org \
--cc=xen@lists.fedoraproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).