From mboxrd@z Thu Jan 1 00:00:00 1970 From: Geraldes Subject: Re: Unable to get QXL vga working / videomem over 4MB issue Date: Fri, 11 May 2012 05:19:07 -0700 (PDT) Message-ID: <1336738747897-5702906.post@n5.nabble.com> References: <1335946863612-5679908.post@n5.nabble.com> <1336048124596-5683034.post@n5.nabble.com> <20120503140045.GP2058@reaktio.net> <1336055231213-5683345.post@n5.nabble.com> <20120503160244.GQ2058@reaktio.net> <1336119794999-5685158.post@n5.nabble.com> <1336120109.26385.7.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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.