From: Paul Durrant <Paul.Durrant@citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>,
"Dario Faggioli" <dario.faggioli@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Ian Jackson <Ian.Jackson@citrix.com>,
Anthony Perard <anthony.perard@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: Wondering about cirris and stdvga
Date: Mon, 21 Nov 2016 08:34:59 +0000 [thread overview]
Message-ID: <b6317d55be104a2abe032b470e0f1cda@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20161119105641.GL28824@reaktio.net>
> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: 19 November 2016 10:57
> To: Dario Faggioli <dario.faggioli@citrix.com>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>; Paul Durrant
> <Paul.Durrant@citrix.com>; Anthony Perard <anthony.perard@citrix.com>;
> xen-devel <xen-devel@lists.xenproject.org>; Stefano Stabellini
> <sstabellini@kernel.org>; Ian Jackson <Ian.Jackson@citrix.com>; Roger Pau
> Monne <roger.pau@citrix.com>
> Subject: Re: [Xen-devel] Wondering about cirris and stdvga
>
> On Fri, Nov 18, 2016 at 07:04:15PM +0100, Dario Faggioli wrote:
> > Sending again, this time, with Anthony's and xen-devel address spelled
> > right. Sorry!! :-(
> > -------------------------------------------
> > Hello to you, various pseudo-random people,
> >
> > It's not my field of expertise, so bear with me, at least a little bit
> > (and, Konrad, you help me, or there will be consequences! :-D)
> >
> > So, I and Konrad recently discovered --while testing the about to be
> > released Fedora 25 as a Xen guest-- that the Cirrus emulated graphic
> > card that we consume from QEMU for HVM guests is broken on Wayland.
> >
> > We just discovered it because Fedora 25 uses Wayland by default, but it
> > appears not to be something new:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1227770
> >
> > And at least from what we see in that bugreport, not much has happened
> > so far.
> >
> > Using "vga='stdvga'" in the config file, or even "vga='qxl'" make
> > things work again. Disabling Wayland in the guest also works (i.e., if
> > not using Wayland, Cirrus is ok). And that's what made us think that
> > it's probably a Wayland issue.
> >
> > I've tried the same on KVM, and the situation is identical
> > (Cirrus+Wayland=breaks, whatever-else+Wayland=works,
> > Cirrus+Xorg=works).
> >
> > I've also read around that these days, e.g., stdvga is at least as good
> > as cirrus, performance wise, that cirrus is broken and impossible to
> > fix (because it is the hardware that it's emulating that was broken),
> > that stdvga enables better screen resolution in guests, etc.
> >
> > I'm not sure about these claims, in particular the performance one, is
> > probably pretty hard to verify. And as I said, it's not my field.
> >
> > Still I thought it could be worthwhile to at least bring this up:
> > should we start to consider changing the default from cirrus to stdvga
> > (or something else)?
> >
>
> There's multiple things here..
>
> 1) Yes, +1, let's change the Xen HVM default to "stdvga".
>
In general std-vga also gets a +1 from me, but I have recently found that a Windows Server 2008 guest does not boot (ar at least the display freezes on boot) when using std-vga with QEMU trad but everything is fine with Cirrus... so probably worth making the default dependent on which QEMU is being used. Never had any issues with std-vga on upstream QEMU.
Paul
> 2) It'd good to create an upstream Wayland bugreport and investigate more
> about why cirrus is broken with Wayland.
>
> 3) It'd be good to have Xen HVM with "qxl" tested by OSStest aswell..
>
>
> > Thanks for your time and Regards,
> > Dario
>
>
> Thanks,
>
> -- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-21 8:37 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 [this message]
2016-11-21 17:47 ` Stefano Stabellini
2016-11-21 9:04 ` Dario Faggioli
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=b6317d55be104a2abe032b470e0f1cda@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=pasik@iki.fi \
--cc=roger.pau@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).