From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fantu Subject: Re: Need help with qemu args debug Date: Fri, 9 Mar 2012 02:58:15 -0800 (PST) Message-ID: <1331290695325-5550240.post@n5.nabble.com> References: <1330529436918-5525248.post@n5.nabble.com> <1330529975275-5525276.post@n5.nabble.com> <1330678830304-5530386.post@n5.nabble.com> <1330697029907-5531045.post@n5.nabble.com> <1331043535494-5540944.post@n5.nabble.com> <4F58E55E.6080609@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F58E55E.6080609@gmail.com> 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-3 wrote > > 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 ? > Thanks for reply, the problem is present also without spice, qxl and cdrom. Tried to apply patch, doesn't work, probably because it is based on qemu unstable (xen-unstable use stable-1.0 branch). I have applied manually modified lines but to no avail, same problem. -- View this message in context: http://xen.1045712.n5.nabble.com/Need-help-with-qemu-args-debug-tp5524689p5550240.html Sent from the Xen - Dev mailing list archive at Nabble.com.