WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Help with the migration to XEN-4.1 please

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Help with the migration to XEN-4.1 please
From: Flavio <fbcyborg@xxxxxxxxx>
Date: Mon, 17 Oct 2011 16:32:24 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 17 Oct 2011 07:33:20 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=utRcWXv7KPfdTbon6GSl3TRg+2pRYTeA2MQOxJH8Hk8=; b=OHFYW5FbYjH3UAtcIdkJ9ZLq7LAT0x6Rnt8CNlxEA9FuU9DZmLFpseBJalijmNwc0n 4pAIInxS87+j00/4Suf9j+HLYiwrLDSVAedBvKMXbEsH5HohlT0PT7cHmTp/a9xJudug qobXBo6xyoNOmpKOdngXp+qpZPPdNjMQEgO2M=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1318858019.16132.7.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAP8Jb=rKu5RFW0tuvHtD819Dz6Jy2HB5OT-d86T1tEk2OP=dtA@xxxxxxxxxxxxxx> <CAP8Jb=pX3mq7vebZ+CKGyh-YM+QH0Vr+Fphaqug_bEgNGLafBg@xxxxxxxxxxxxxx> <1315907178.2892.7.camel@xxxxxxxxxxxxxxxxxxxxxx> <CAP8Jb=qfMa1c8w10inO_gt6-RCscaAsdQ_SyjTxfjSuTAfDMOw@xxxxxxxxxxxxxx> <1316001435.2892.24.camel@xxxxxxxxxxxxxxxxxxxxxx> <CAP8Jb=qrdraJ0c7CLEYEug2nQjxCTvokfGQB4CjNgaacON_DPg@xxxxxxxxxxxxxx> <1316007936.2892.35.camel@xxxxxxxxxxxxxxxxxxxxxx> <CAP8Jb=rabtnD05T2ZQdkzw47ZkctYXMcEbrLPj_0LJHWyLegFw@xxxxxxxxxxxxxx> <1316009344.2892.38.camel@xxxxxxxxxxxxxxxxxxxxxx> <CAP8Jb=qm=kjU8cyCU+G9sht6NqeNyFK+R-P-41bkOiha1iGhYw@xxxxxxxxxxxxxx> <CAP8Jb=o1j2=e85J_aCab=zr7hyxU5VHVtuFUOyNBkrki8eA2hQ@xxxxxxxxxxxxxx> <CAP8Jb=qTNoG7_YKDEpo9ichNjE+x50jtKmCh-a-Z=5PZ4676Sw@xxxxxxxxxxxxxx> <1318858019.16132.7.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 17 October 2011 15:26, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> I'm afraid we'll need more info on the current state of your system,
> per: http://wiki.xen.org/xenwiki/ReportingBugs
>
> The qemu log in particular seems likely to be interesting.
Thanks, here we go:

PREMISE: I've solved the problem during the log file collection for
the bug report
submission. So, it is not due to a bug.

what happened: the domU (Gentoo or Debian) doesn't start becouse of
the following error:
# xl create /mnt/dati/xen/vmstore/gentoo-10.0/gentoo-10.0.x86-64.cfg -c
Parsing config file /mnt/dati/xen/vmstore/gentoo-10.0/gentoo-10.0.x86-64.cfg
xenconsole: Could not read tty from store: No such file or directory
libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device
Model not ready
xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup

when: when I was trying to start a domU.

what I was expecting: the domU should start showing the boot messages without
any error.

OS: Gentoo Linux arch x86_64, Linux Kernel 3.0.6 (gentoo-sources)
app-emulation/xen: v. 4.1.1-r2
app-emulation/xen-tools: v. 4.1.1-r5 USE Flags: hvm and pygrub


/var/log/xen/xen-hotplug.log: http://pastebin.com/4ZLmh64T

The problem was here. My fault not reading this log.
/var/log/xen/qemu-dm-gentoo-10.0-x86_64.log:
libxl: cannot execute /usr/lib/xen/bin/qemu-dm: No such file or directory

OK, qemu-dm was not present. It is strange.
And this is why I didn't think that qemu-dm was not present, because I was
certain it was right there, since I've used it.
Maybe some upgrade removed it.
Now I've recompiled the xen-tools package with the "qemu" USE flag active and
the binary is present now.

The Linux domUs start without any problem.

Thank you so much for giving me the input to read how to submit a bug report,
since I've solved the problem by myself. I hope this would be useful for other
people.

-- 
Flavio

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>