xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Paul Durrant <Paul.Durrant@citrix.com>
Cc: "anthony.perard" <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Roger Pau Monne <roger.paumonne@citrix.com>
Subject: Wondering about cirris and stdvga
Date: Fri, 18 Nov 2016 19:04:15 +0100	[thread overview]
Message-ID: <1479492255.3832.52.camel@citrix.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2042 bytes --]

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)?

Thanks for your time 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

             reply	other threads:[~2016-11-18 18:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 18:04 Dario Faggioli [this message]
2016-11-19 10:56 ` Wondering about cirris and stdvga 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
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=1479492255.3832.52.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=konrad.wilk@oracle.com \
    --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).