From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Fabio Fantoni <fabio.fantoni@heliman.it>,
Rob Hoes <Rob.Hoes@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: libxl videoram for cirrus graphics
Date: Tue, 17 Sep 2013 15:00:24 +0100 [thread overview]
Message-ID: <1379426424.11304.100.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <20130917132419.GG22986@zion.uk.xensource.com>
On Tue, 2013-09-17 at 14:24 +0100, Wei Liu wrote:
> On Tue, Sep 17, 2013 at 12:54:57PM +0000, Rob Hoes wrote:
> > Hi,
> >
> > The videoram setting in xl config files is documented as follows:
> >
> > "
> > videoram=MBYTES
> >
> > Sets the amount of RAM which the emulated video card will contain, which in turn limits the resolutions and bit depths which will be available. The default amount of video ram for stdvga is 8MB which is sufficient for e.g. 1600x1200 at 32bpp and videoram option is currently working only when using the qemu-xen-traditional device-model.
> >
> > When using the emulated Cirrus graphics card (vga="cirrus") the amount of video ram is fixed at 4MB which is sufficient for 1024x768 at 32 bpp and videoram option is currently working only when using the upstream qemu-xen device-model.
> > "
> >
> > XenServer also uses a default of 4MB video ram for cirrus graphics.
> >
> > However, when I use xl to create a VM with cirrus graphics, I get 8MB of video RAM by default. Moreover, setting it to videoram=4 in the config file leads to complaints from libxl:
> >
> > libxl_create.c:228:libxl__domain_build_info_setdefault: videoram must be at least 8 mb
> >
> > Is there a bug in the logic in libxl_create.c?
> >
>
> I think the document needs to be updated.
>
> commit 2e814a017155b885e4d4b5a88dc05e7367a9722a
> Author: Fabio Fantoni <fabio.fantoni@heliman.it>
> Date: Fri Feb 15 13:32:27 2013 +0000
>
> tools/libxl: Improve videoram setting
>
> - If videoram setting is less than 8 mb shows error and exit.
I wonder why this is the case. Fabvio do you remmeberwhere this number
8M came from for Cirrus?
next prev parent reply other threads:[~2013-09-17 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 12:54 libxl videoram for cirrus graphics Rob Hoes
2013-09-17 13:17 ` Ian Campbell
2013-09-17 13:29 ` Rob Hoes
2013-09-17 14:04 ` Ian Campbell
2013-09-17 14:52 ` Rob Hoes
2013-09-17 15:01 ` Ian Campbell
2013-09-20 10:49 ` Stefano Stabellini
2013-09-17 13:24 ` Wei Liu
2013-09-17 14:00 ` Ian Campbell [this message]
2013-09-17 17:51 ` Fabio Fantoni
2013-09-17 19:13 ` Ian Campbell
2013-09-17 14:03 ` Frediano Ziglio
2013-09-17 17:00 ` Pasi Kärkkäinen
2013-09-18 13:51 ` Rob Hoes
2013-09-18 9:13 ` Rob Hoes
2013-09-18 9:40 ` Fabio Fantoni
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=1379426424.11304.100.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Rob.Hoes@citrix.com \
--cc=fabio.fantoni@heliman.it \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).