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/
Home Products Support Community News


Re: [Xen-users] Error on xm create

To: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Error on xm create
From: Andrew Turnbull <abturnbull@xxxxxxxxx>
Date: Fri, 25 Nov 2005 14:36:19 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 25 Nov 2005 14:36:19 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UpP9R3NXGeltsPjeAtQ386xEFe2BGwYnYfzTy5UO+kaexoAATajGh1eLdXb3WIIs66KTetObE7zsY03s7c719f3kcwNYNoRDCdGxWtMpJUIjrzakZxp1gTXDftjZ0tvqRT1lxFIaQ4SGtuQ3tML7TecYoPls4hhOLjjfypRZVw0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E1EfeZT-00010c-00@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <abturnbull@xxxxxxxxx> <bff20ae20511250614v32646299x@xxxxxxxxxxxxxx> <E1EfeZT-00010c-00@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 25/11/05, Steven Hand <Steven.Hand@xxxxxxxxxxxx> wrote:
> > On 25/11/05, Steven Hand <Steven.Hand@xxxxxxxxxxxx> wrote:
> > >
> > > > > As far as I can see most error paths should issue something on stderr
> > > > > - can you check /var/log/xend-debug.log?
> > >
> > > You're sure this is /var/log/xend-debug.log (not /var/log/xend.log) ?
> >
> > Yes positive. The Attatchment I sent before was the xend.log and the
> > latest paste i did was from the xen-debug.log
> Yes, I see.
> The "Error constructing guest OS" message comes from xc_linux_build()
> when setup_guest() fails. Most of the error paths in there spit out
> some stuff to stderr (which would appear in the log prior to the
> "Error constructing guest OS" mesage).
> Given that you're not getting any, it seems like it must be one of the
> 'silent' paths, which is trickier to track down. The first of these
> 'silent' paths is a failure to parse the image format (which should
> be the elf parser), hence my other question.
> > > And did you check the image itself, e.g. "file /boot/vmlinuz-2.6.12-xenU" 
> > > ?
> >
> > I did an ls -al  /boot/vm* How else can it be verified ?
> Well "file /boot/vmlinuz-2.6.12-xenU" to check it's actually a gzip
> compressed image; and if so, "cat /boot/vmlinuz-2.6.12-xenU | gunzip
> -c >/tmp/FOO" and "objdump -d /tmp/FOO" to check its an ok ELF image.


Followed your steps, and it came out with load of

c035d68f:       c3                      ret
c035d690:       83 ec 04                sub    $0x4,%esp
c035d693:       e8 b8 2d f6 ff          call   0xc02c0450
c035d698:       e8 63 83 f5 ff          call   0xc02b5a00
c035d69d:       c7 04 24 e0 99 31 c0    movl   $0xc03199e0,(%esp)
c035d6a4:       e8 d7 ff f5 ff          call   0xc02bd680
c035d6a9:       c7 04 24 60 9a 31 c0    movl   $0xc0319a60,(%esp)
c035d6b0:       e8 cb ff f5 ff          call   0xc02bd680
c035d6b5:       e8 e6 33 f6 ff          call   0xc02c0aa0
c035d6ba:       59                      pop    %ecx
c035d6bb:       e9 50 33 f6 ff          jmp    0xc02c0a10

> cheers,
> S.

Xen-users mailing list