From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
"anthony.perard" <anthony.perard@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Roger Pau Monne <roger.paumonne@citrix.com>
Subject: Re: Wondering about cirris and stdvga
Date: Mon, 21 Nov 2016 10:04:13 +0100 [thread overview]
Message-ID: <1479719053.3832.103.camel@citrix.com> (raw)
In-Reply-To: <20161119105641.GL28824@reaktio.net>
[-- Attachment #1.1: Type: text/plain, Size: 1524 bytes --]
On Sat, 2016-11-19 at 12:56 +0200, Pasi Kärkkäinen wrote:
> There's multiple things here..
>
> 1) Yes, +1, let's change the Xen HVM default to "stdvga".
>
:-)
> 2) It'd good to create an upstream Wayland bugreport and investigate
> more about why cirrus is broken with Wayland.
>
Sure, I can do that.
> 3) It'd be good to have Xen HVM with "qxl" tested by OSStest aswell..
>
I've had a look at that too, and I'm happy to continue trying, although
I don't know much on the subject, so any help is appreciated.
I've found out that, if you install spice dev libraries, (upstream)
QEMU gets built with qxl enabled, and I can specity "vga=qxl" in guest
config, and that works.
I see the boot, I see X / Wayland, etc.
What I haven't understood yet is how to actually connect with a "spice
client" (or whatever the correct terminology is) and get the
acceleration and all the benefits. I've tried just connecting with
spicy or virt-viewer, but couldn't get that to work.
I think I've got to install/enable stuff inside the guest too, but I'm
not sure what yet.
I'll try to fetch docs online, and fish back one of those old thread we
had here about spice support, to see if there is some more info.
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: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-21 9:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 18:04 Wondering about cirris and stdvga Dario Faggioli
2016-11-19 10:56 ` Pasi Kärkkäinen
2016-11-21 8:34 ` Paul Durrant
2016-11-21 17:47 ` Stefano Stabellini
2016-11-21 9:04 ` Dario Faggioli [this message]
2016-11-25 18:17 ` Dario Faggioli
2016-11-29 4:55 ` Konrad Rzeszutek Wilk
2017-03-17 14:19 ` Konrad Rzeszutek Wilk
2017-03-17 15:51 ` Dario Faggioli
2017-03-17 16:08 ` Konrad Rzeszutek Wilk
2017-03-20 14:13 ` Roger Pau Monné
2017-03-20 14:21 ` Paul Durrant
2017-03-20 14:25 ` Roger Pau Monne
2017-04-04 20:18 ` Konrad Rzeszutek Wilk
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=1479719053.3832.103.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=pasik@iki.fi \
--cc=roger.paumonne@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).