From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Need help with qemu args debug
Date: Thu, 1 Mar 2012 01:43:16 -0800 (PST) [thread overview]
Message-ID: <1330594996706-5527425.post@n5.nabble.com> (raw)
In-Reply-To: <1330594273.18632.2.camel@zakaz.uk.xensource.com>
Ian Campbell-10 wrote
>
> On Thu, 2012-03-01 at 09:18 +0000, Fantu wrote:
>> Stefano Stabellini-3 wrote
>> >
>> > Try adding videoram=32 to the VM config file, I think the issue is that
>> > the default videoram size for QXL is much larger (32MB) than the
>> default
>> > videoram size for Cirrus (8MB).
>> >
>>
>> Minimum setting of the ram was 16 mb, I applied this patch for decrese
>> minimum to 4 mb:
>> http://git.qemu.org/?p=qemu.git;a=commit;h=80105bbfb2aa3023e959b6ea682a3fc9515080a3
>> And retry with -global qxl-vga.vram_size=4194304 (4 MB) but give same
>> error
>> /var/log/xen/qemu-dm-PRECISEHVM.log
>> do_spice_init: starting 0.10.1
>> spice_server_add_interface: SPICE_INTERFACE_MIGRATION
>> spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
>> spice_server_add_interface: SPICE_INTERFACE_MOUSE
>> qemu: hardware error: xen: failed to populate ram at 40000000
>
> I think you'll need to dig into the qemu code and find out where/why
> this message is coming from.
>
>>
>> Tried to change minimum patch and setting to 3 MB but always same result,
>> probably samething to change about xen for support qxl graphic and
>> assignment of its ram?
>> I do not know how to fix or what else to try now :(
>
I do other search about xen limit of video ram and found old patch about
limit of qemu video ram size, is probably something about...
http://xen.1045712.n5.nabble.com/PATCH-ioemu-drop-unused-4MB-video-memory-td2487287.html
I do search on new tree but not found for now on where is xen limit of video
ram allocation, someone can help me please?
--
View this message in context: http://xen.1045712.n5.nabble.com/Need-help-with-qemu-args-debug-tp5524689p5527425.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-03-01 9:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 11:09 Need help with qemu args debug Fantu
2012-02-29 11:22 ` Ian Campbell
2012-02-29 12:44 ` Fantu
2012-02-29 13:05 ` Ian Campbell
2012-02-29 16:20 ` Ian Jackson
2012-02-29 17:31 ` Philipp Hahn
2012-02-29 18:45 ` Ian Campbell
2012-02-29 13:05 ` Fantu
2012-02-29 15:06 ` Stefano Stabellini
2012-02-29 15:30 ` Fantu
2012-02-29 15:39 ` Fantu
2012-03-01 14:27 ` Stefano Stabellini
2012-03-02 9:00 ` Fantu
2012-03-02 13:30 ` Stefano Stabellini
2012-03-02 14:03 ` Fantu
2012-03-02 15:36 ` Stefano Stabellini
2012-03-06 14:18 ` Fantu
2012-03-07 15:00 ` Fantu
2012-03-09 0:45 ` Ian Campbell
2012-03-08 16:59 ` Anthony PERARD
2012-03-09 10:58 ` Fantu
2012-03-09 14:55 ` Anthony PERARD
2012-03-12 9:31 ` Fantu
2012-03-13 9:14 ` Fantu
2012-03-13 9:33 ` Ian Campbell
2012-03-13 9:41 ` Ian Campbell
2012-03-15 9:36 ` Fantu
2012-03-15 17:35 ` Anthony PERARD
2012-03-16 10:51 ` Fantu
2012-03-01 14:11 ` Stefano Stabellini
2012-03-01 9:18 ` Fantu
2012-03-01 9:31 ` Ian Campbell
2012-03-01 9:43 ` Fantu [this message]
2012-03-01 10:58 ` Fantu
2012-03-01 14:40 ` Stefano Stabellini
2012-02-29 17:25 ` Philipp Hahn
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=1330594996706-5527425.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).