From: Paul Durrant <Paul.Durrant@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Dario Faggioli <dario.faggioli@citrix.com>,
ajax <ajax@redhat.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Anthony Perard <anthony.perard@citrix.com>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: Wondering about cirris and stdvga
Date: Mon, 20 Mar 2017 14:21:50 +0000 [thread overview]
Message-ID: <ac56f9423497436ebc0fab4b19e21c16@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20170320141332.7toocyirg7s4wloh@dhcp-3-128.uk.xensource.com>
> -----Original Message-----
> From: Roger Pau Monne
> Sent: 20 March 2017 14:14
> To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Dario Faggioli <dario.faggioli@citrix.com>; Ian Jackson
> <Ian.Jackson@citrix.com>; Pasi Kärkkäinen <pasik@iki.fi>; Stefano Stabellini
> <sstabellini@kernel.org>; Paul Durrant <Paul.Durrant@citrix.com>; Anthony
> Perard <anthony.perard@citrix.com>; xen-devel <xen-
> devel@lists.xenproject.org>; Roger Pau Monne <roger.pau@citrix.com>;
> ajax <ajax@redhat.com>
> Subject: Re: [Xen-devel] Wondering about cirris and stdvga
>
> On Fri, Mar 17, 2017 at 10:19:47AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Fri, Nov 25, 2016 at 07:17:31PM +0100, Dario Faggioli wrote:
> > > On Mon, 2016-11-21 at 10:04 +0100, Dario Faggioli wrote:
> > > > On Sat, 2016-11-19 at 12:56 +0200, Pasi Kärkkäinen wrote:
> > > > > 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.
> > > >
> > > An update.
> > >
> > > The discussion here has gone on a bit:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1227770
> > >
> > > The conclusion seems to be that:
> > > "cirrus (virtual) hardware is simply to old to run wayland."
> > >
> > > And so this is (and will very likely remain) a 'WONTFIX' for cirrus, at
> > > least on Fedora.
> > >
> > > I've also opened a thread on wayland-devel mailing list:
> > > https://lists.freedesktop.org/archives/wayland-devel/2016-
> November/0318
> > > 56.html
> > >
> > > There, I learned that Wayland is not the component to blame, as Wayland
> > > is the protocol. So, in our case, the 'bug' is most likely in
> > > gnome-shell / Mutter.
> > >
> > > That's not a good thing, though. In fact, just to cite a few sentences
> > > from the thread:
> > >
> > > "Packed 24bpp is going to be pain, not least because I don't know of
> > > any clients which render in packed-24"
> > >
> > > "The 24bpp paths in pretty much everything are also badly untested, so
> > > that's asking for trouble."
> > >
> > > "you will need to test and fix every single Wayland compositor out
> > > there."
> > >
> > > "I really think you'd be far far better off trying to figure out how to
> > > move off the legacy Cirrus emulation as soon as you can."
> > >
> > > So, we can try seeing if I manage to get some logs out of Mutter to
> > > figure out the actual bug more precisely _but_, considering all that
> > > people have said both here and in the other forums, I think it would be
> > > better to spend that time figuring out how to switch (and document this
> > > for 4.8 and previous version, of course).
> >
> >
> > Yes. Also as there does not seem to be any supported OS that
> > _needs_ the old Cirrus OS to boot and function.
>
> Not that I oppose to change to stdvga, but what would happen to Windows
> VMs
> that suddenly change from cirrus to stdvga, is that going to trigger the
> license invalidation stuff? AFAIK this happens when you change hardware,
> but
> maybe a VGA change doesn't trigger that because it's common for people to
> upgrade VGA cards?
>
Changing anything that Windows considers part of the core system will invalidate a license but, as you say, the graphics device may not be core. There is another issue (which I just verified myself) which as that at least some versions of Windows (Server 2008 in my case) won't boot when using stdvga with qemu trad.
Paul
> Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-20 14:31 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
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 [this message]
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=ac56f9423497436ebc0fab4b19e21c16@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=ajax@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=konrad.wilk@oracle.com \
--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).