From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Unable to get QXL vga working / videomem over 4MB issue
Date: Wed, 9 May 2012 07:07:06 -0700 (PDT) [thread overview]
Message-ID: <1336572426286-5697470.post@n5.nabble.com> (raw)
In-Reply-To: <1336504555.4350.22.camel@dagon.hellion.org.uk>
Ian Campbell-10 wrote
>
> On Tue, 2012-05-08 at 17:24 +0100, Pasi Kärkkäinen wrote:
>> On Fri, May 04, 2012 at 12:32:19PM +0100, Ian Campbell wrote:
>> > On Fri, 2012-05-04 at 12:21 +0100, Anthony PERARD wrote:
>> > > On Fri, May 4, 2012 at 9:28 AM, Ian Campbell <Ian.Campbell@>
>> wrote:
>> > > > Anthony -- any idea why the videoram setting doesn't work with
>> upstream
>> > > > qemu?
>> > >
>> > > Well, the parameter could be pass to qemu qxl, but it's not yet. But
>> > > then, it seams you have to have this value of at least 32MB,
>> otherwise
>> > > the value is increase in qemu.
>> > >
>> > > For cirrus/stdvga, there is no way to pass the parameter to qemu, the
>> > > size in qemu is fixed to 8MB.
>> >
>> > OK, so this is simply a feature which upstream qemu doesn't have.
>> That's
>> > fine.
>> >
>>
>> Is this something that should be forward-ported from qemu-xen-traditional
>> to upstream qemu ?
>
> If there are reasons why this should be configurable, then I guess so.
> Are you going to look into that?
>
> This doesn't seem like 4.2 material to me though.
>
>> > I guess xl.cfg(5) needs updating to make it clear that this option only
>> > applies to qemu-xen-traditional.
>> >
>> > The docs also currently say that for stdvga the default is 8MB and for
>> > not stdvga (by which I guess it means Cirrus) the default if 4MB. So I
>> > guess even this is inaccurate for qemu-xen-upstream?
>> >
>> > Can someone send a patch please?
>> >
>>
>> For the documentation patch maybe add this to the 4.2 status todo list
>> as a reminder :)
>
> Please make requests for additions to the TODO list in the most recent
> TODO list thread, with a link to the relevant thread. Otherwise the
> chances are I won't remember when I update the list, since I only look
> at replies in the TODO threads.
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
>
I may have found something that makes the problem clearer.
With Precise hvm domU with spice and cirrus (default vga) on qemu-xen lspci
show 32 mb but Xorg only sees 4 mb.
----------------------------------------------------
lspci -vvv
...
00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA
controller])
Subsystem: Red Hat, Inc Device 1100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=<b>32M*]
Region 1: Memory at f3020000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at f3000000 [disabled] [size=64K]
Kernel modules: cirrusfb
...
-----------------
Xorg.0.log
---------------
...
[ 6.443] (--) CIRRUS(0): VideoRAM: 4096 kByte
...
----------------------------------------------------
If you need more information I'll post it.
--
View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5697470.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-05-09 14:07 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 [this message]
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
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=1336572426286-5697470.post@n5.nabble.com \
--to=fantonifabio@tiscali.it \
--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).