From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Unable to get QXL vga working / videomem over 4MB issue
Date: Fri, 4 May 2012 01:56:44 -0700 (PDT) [thread overview]
Message-ID: <1336121804904-5685216.post@n5.nabble.com> (raw)
In-Reply-To: <1336120109.26385.7.camel@dagon.hellion.org.uk>
Ian Campbell-10 wrote
>
> (putting Pasi back in the CC, please retain CCs on xen-devel)
>
> On Fri, 2012-05-04 at 09:23 +0100, Fantu wrote:
>> Pasi Kärkkäinen wrote
>> > Ok. If you use qemu-upstream and cirrus/stdvga (without qxl), does
>> > videomem >4MB work then ?
>> >
>> No, always 4 mb, also with cirrus or stdvga videoram setting not work.
>
> But with Qemu-xen-traditional it does work?
>
> Anthony -- any idea why the videoram setting doesn't work with upstream
> qemu?
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
>
With qemu-xen-traditional videoram setting with stdvga work.
About Spice on qemu-upstream for now we did only basic tests and it seems to
be working but without qxl limited to 4 mb many of spices features are not
full working.
Qxl vga can be used also without spice and with videoram to 32 or 64 mb I
think can give better graphic performance with hvm domU.
For now is not good even without multimedia use.
--
View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5685216.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-04 8:56 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 [this message]
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
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=1336121804904-5685216.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).