Re: [Xen-devel] Wondering about cirris and stdvga

[Roger Pau Monne <roger.pau@xxxxxxxxxx>]

On Mon, Mar 20, 2017 at 02:21:50PM +0000, Paul Durrant wrote:
> > -----Original Message-----
> > From: Roger Pau Monne
> > Sent: 20 March 2017 14:14
> > To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> > Cc: Dario Faggioli <dario.faggioli@xxxxxxxxxx>; Ian Jackson
> > <Ian.Jackson@xxxxxxxxxx>; Pasi Kärkkäinen <pasik@xxxxxx>; Stefano Stabellini
> > <sstabellini@xxxxxxxxxx>; Paul Durrant <Paul.Durrant@xxxxxxxxxx>; Anthony
> > Perard <anthony.perard@xxxxxxxxxx>; xen-devel <xen-
> > devel@xxxxxxxxxxxxxxxxxxxx>; Roger Pau Monne <roger.pau@xxxxxxxxxx>;
> > ajax <ajax@xxxxxxxxxx>
> > 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.

IMHO, I would leave qemu-trad alone and just change the default gfx card for
qemu-xen. I don't see much point in touching anything in qemu-trad.

Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel