From: Anthony PERARD <anthony.perard@gmail.com>
To: Fantu <fantonifabio@tiscali.it>
Cc: xen-devel@lists.xensource.com
Subject: Re: Need help with qemu args debug
Date: Thu, 8 Mar 2012 16:59:10 +0000 [thread overview]
Message-ID: <4F58E55E.6080609@gmail.com> (raw)
In-Reply-To: <1331043535494-5540944.post@n5.nabble.com>
On 06/03/12 14:18, Fantu wrote:
> Stefano Stabellini-3 wrote
>>
>> There is nothing on the logs but SPICE, unfortunately.
>> You might have to add few printf to QEMU to see how far it is able to
>> go. For example block.c:bdrv_open.
>>
>
> Problem found, device not found is caused by maxmem parameter,domU S.O.
> starts without maxmem, probably there are same unexpected cases on xen
> and/or seabios with ram and videoram allocation.
> I tried searching but could not find the solution to make allocation of ram
> and videoram works with more than standard values.
I tried to reproduce this, but I did not have any issue (with an iso).
Also I could not understand why maxmem will have an issue with a drive.
Also, spice+qemu on debian does not work well, so I'm not sure if I will
have the same issue. When you found the issue related to the "device not
found", do you have run the VM without qxl and spice ?
I've just send a patch that fix a memory mapping issue (at least for
me), could you try with it? :
http://lists.xen.org/archives/html/xen-devel/2012-03/msg00627.html
Then, do you have the same issue if you use an .iso instead of /dev/sr0
as a cdrom ?
--
Anthony PERARD
next prev parent reply other threads:[~2012-03-08 16:59 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 [this message]
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
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=4F58E55E.6080609@gmail.com \
--to=anthony.perard@gmail.com \
--cc=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).