xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Geraldes <heliman@katamail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Unable to get QXL vga working / videomem over 4MB issue
Date: Fri, 11 May 2012 05:19:07 -0700 (PDT)	[thread overview]
Message-ID: <1336738747897-5702906.post@n5.nabble.com> (raw)
In-Reply-To: <CAJJyHj+FPw9cmNQ36mg7DXP=-tMH8bBxRJ7wgy-fEdy+8X142Q@mail.gmail.com>


Anthony PERARD-2 wrote
> 
> For cirrus/stdvga, there is no way to pass the parameter to qemu, the
> size in qemu is fixed to 8MB.
> 

How can you see these 8MB ?
In my tests with cirrus/stdvga, in a Linux guest lspci always report 32M and
Xorg.0.log report "VideoRAM: 4096 kByte". In a Windows XP/7 guest the Device
Manager show 32M as well. This is confusing.
Is there a better way to check videoram and videoram usage in a Linux or
Windows guest?


--
View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5702906.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

  parent reply	other threads:[~2012-05-11 12:19 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:23 Unable to get QXL vga working Fantu
2012-04-26 15:39 ` Ian Campbell
2012-04-27  5:15   ` ZhouPeng
2012-04-27  9:23     ` Fantu
2012-05-02  8:21     ` Fantu
2012-05-03 11:31       ` ZhouPeng
2012-05-03 12:28         ` Fantu
2012-05-03 14:00           ` Unable to get QXL vga working / videomem over 4MB issue Pasi Kärkkäinen
2012-05-03 14:27             ` Fantu
2012-05-03 16:02               ` Pasi Kärkkäinen
2012-05-04  8:23                 ` Fantu
2012-05-04  8:28                   ` Ian Campbell
2012-05-04  8:56                     ` Fantu
2012-05-04 11:21                     ` Anthony PERARD
2012-05-04 11:32                       ` Ian Campbell
2012-05-08 16:24                         ` Pasi Kärkkäinen
2012-05-08 19:15                           ` Ian Campbell
2012-05-09 14:07                             ` Fantu
2012-05-09 16:01                               ` Anthony PERARD
2012-05-04 12:02                       ` Fantu
2012-05-07 15:01                         ` Fantu
2012-05-11 12:19                       ` Geraldes [this message]
2012-05-11 13:00                         ` Anthony PERARD
2012-05-03 12:46         ` Unable to get QXL vga working Stefano Stabellini
2012-05-03 12:56           ` ZhouPeng
2012-05-03 13:05             ` Stefano Stabellini
2012-05-03 13:05               ` ZhouPeng
2012-05-03 13:13                 ` Ian Campbell
2012-05-03 13:27                   ` ZhouPeng
2012-05-03 13:56                 ` Stefano Stabellini
2012-05-04  1:15                   ` ZhouPeng
2012-05-04  8:30                     ` Ian Campbell
2012-05-24  3:13                       ` ZhouPeng
2012-05-24 10:13                         ` Stefano Stabellini
2012-05-24 11:28                           ` ZhouPeng
2012-06-11 11:56                             ` Fabio Fantoni
2012-06-13  9:02                               ` ZhouPeng
2012-06-13  9:38                                 ` Fabio Fantoni
2012-06-13 11:40                                   ` ZhouPeng
2012-06-14 13:51                                     ` Fabio Fantoni
2012-06-15  7:36                                       ` ZhouPeng

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=1336738747897-5702906.post@n5.nabble.com \
    --to=heliman@katamail.com \
    --cc=xen-devel@lists.xensource.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).