From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "Tim (Xen.org)" <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 1/2] libxl: set stdvga=1 by default when creating a hvm guest
Date: Wed, 27 Jun 2012 08:29:00 +0100 [thread overview]
Message-ID: <1340782140.14761.4.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A1010076A@SHSMSX101.ccr.corp.intel.com>
On Wed, 2012-06-27 at 02:45 +0100, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
> > Sent: Wednesday, June 27, 2012 1:00 AM
> > To: Ian Campbell
> > Cc: Ren, Yongjie; xen-devel@lists.xen.org; Ian Jackson; Tim (Xen.org);
> > Stefano Stabellini
> > Subject: Re: [PATCH 1/2] libxl: set stdvga=1 by default when creating a hvm
> > guest
> >
> > On Tue, 26 Jun 2012, Ian Campbell wrote:
> > > On Tue, 2012-06-26 at 07:02 +0100, Ren, Yongjie wrote:
> > > > libxl: set stdvga=1 by default when creating a hvm guest
> > > >
> > > > Most of the modern OSes (e.g. Windows XP, Windows 7, RHEL6.x,
> > Ubuntu, Fedora) support VBE 2.0 or later.
> > > > So, select a standard VGA card with VBE as the default emulated
> > graphics device.
> > >
> > > I'm not expert on the graphics side of HVM, but on the face of it
> > > switching the default to something more modern seems like a
> > reasonable
> > > idea, although I'm not sure if we should be doing this for 4.2 at this
> > > point.
> > >
> > > I've CCd Tim and Stefano for input from the HVM and QEMU sides.
> >
> > I think it is a good thing.
> > The only thing to keep in mind is that QEMU upstream is switching to
> > 16MB of videoram for stdvga. So at some point in the near future
> > upstream QEMU will stop working correctly with xen 4.2, unless we bump
> > the videoram to 16MB too.
> >
> Yes, we should pay attention to this when using upstream QEMU.
>
> >
> > > > It's also a workaround for the following bug.
> > > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> > >
> > > Do you understand the root cause of that bug?
> > >
> I don't understand the root cause.
>
> > > It's hard to see how detaching a VF relates to the VGA emulation in use.
> > > Can you explain it? Are you sure you aren't just masking the real issue
> > > here?
> >
> It's strange that detaching a VF may break the graphics display.
> As it only happens when 'stdvga=0', it might not be a normal usage.
>
> > Indeed. We cannot possibly accept the patch on the basis that it looks
> > like it is masking an unrelated pci-passthrough bug.
> >
> I don't want to mask that bug, either. :-)
> The following sentence is quoted from xl.cfg man page.
> "If your guest supports VBE 2.0 or later (e.g. Windows XP onwards)
> then you should enable this (stdvga option)."
> If we set 'stdvga=1', we will not meet the bug (#1812).
> I assume many Xen users (including me) are not very familiar with 'stdvga' and
> will leave it as default (it's 0 before my patch).
> If then, users may meet something *strange* like bug #1812.
> I don't think it's friendly to end users, so I set the default value
> of 'stdvga' to '1'.
There are good reasons which justify setting stdvga=1 by default. But
anything to do with #1812 is not one of them. It is obviously wrong to
justify making an unrelated configuration change on the basis that it
hides a bug by default without first understanding the reasons for the
bug.
I certainly hope you are not planning to close #1812 and stop
investigating it if we change the stdvga default.
Ian.
next prev parent reply other threads:[~2012-06-27 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 6:02 [PATCH 1/2] libxl: set stdvga=1 by default when creating a hvm guest Ren, Yongjie
2012-06-26 13:32 ` Ian Campbell
2012-06-26 16:59 ` Stefano Stabellini
2012-06-27 1:45 ` Ren, Yongjie
2012-06-27 7:29 ` Ian Campbell [this message]
2012-06-28 8:09 ` Ren, Yongjie
2012-06-27 10:45 ` Pasi Kärkkäinen
2012-06-27 10:51 ` Stefano Stabellini
2012-06-27 10:53 ` Pasi Kärkkäinen
2012-06-27 10:59 ` Stefano Stabellini
2012-06-27 11:12 ` Ian Campbell
2012-06-27 11:20 ` Pasi Kärkkäinen
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=1340782140.14761.4.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=yongjie.ren@intel.com \
/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).