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] Unable to bring up Mini-OS on x86_64

To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Subject: Re: [Xen-devel] Unable to bring up Mini-OS on x86_64
From: "Jacob Gorm Hansen" <jacobg@xxxxxxx>
Date: Wed, 17 May 2006 13:48:57 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 17 May 2006 04:49:23 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=hwIh43e99h73AafJ3SnQGOoghb2iFDHaVo/uSfZtHMsWve25BwLAxUN9ZHTiZEPOXuBI3quim8YAnF1L9kZZtnkpk1rJ3i3i+VQ7SS9eY0RzgaN/guXvcObfxIjbrK91lqwp0xQ0Dx5VX7UJ3ww13tlyXlGcxsJPWCuZBTvWNfs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <EF8D308BE33AF54D8934DF26520252D3047E4E0F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <EF8D308BE33AF54D8934DF26520252D3047E4E0F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 5/17/06, Puthiyaparambil, Aravindh <aravindh.puthiyaparambil@xxxxxxxxxx>

I did a fresh clone and a build and I am still running into the same
issue. So it looks like there is a bug in xc_linux_build() and/or
Mini-OS.

What is the best way to debug libxc? I usually do fprintf(stderr,...)
and the output shows up in xend-debug.log. But it is very flaky as
sometimes messages are overwritten. Is there a better way to do prints?

I would recommend writing a small c program that calls libxc directly,
that will save you a bunch of time fighting the python/xend logging.

I have attached a patch with my own hand-rolled tools as an example.
The most interesting one is buscreate, which reads a config-file like:

kernel=/home/jacobg/xen-3.0-testing2.hg/linux-2.6.16-xen/vmlinux
mem=16
maxmem=16
console=1
initrd=/home/jacobg/domUinitrd
cmdline=mem=16M init=/linuxrc root=/dev/ram xencons=ttyS0
vbd=706,301,w

- and creates a domain without needing xend at all. xenstored and
xenconsoled need to be running though.

Jacob

Attachment: migrationtools
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>