From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony PERARD Subject: Re: Need help with qemu args debug Date: Fri, 9 Mar 2012 14:55:18 +0000 Message-ID: <4F5A19D6.8030408@citrix.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> <1331290695325-5550240.post@n5.nabble.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------070301050607050306000606" Return-path: In-Reply-To: <1331290695325-5550240.post@n5.nabble.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: Fantu Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --------------070301050607050306000606 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 09/03/12 10:58, Fantu wrote: > > 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. I think there is a better solution for your spice issue. Just specify videoram=32 in your config file, and remove your maxmem options. Also apply the patch attached to this mail, that should fix the issue. Regards, -- Anthony PERARD --------------070301050607050306000606 Content-Type: text/x-patch; name="libxl_patch.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="libxl_patch.patch" diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index 922b20b..2fe000e 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -518,7 +518,7 @@ static char ** libxl__build_device_model_args_new(libxl__gc *gc, flexarray_append(dm_args, "-m"); flexarray_append(dm_args, libxl__sprintf(gc, "%d", - libxl__sizekb_to_mb(b_info->target_memkb))); + libxl__sizekb_to_mb(b_info->max_memkb - b_info->video_memkb))); if (b_info->type == LIBXL_DOMAIN_TYPE_HVM) { for (i = 0; i < num_disks; i++) { --------------070301050607050306000606 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --------------070301050607050306000606--