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] domU guest for xcp 0.1.1

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Mon, 22 Mar 2010 14:02:33 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 22 Mar 2010 14:04:29 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=tcPozoI4dOWEdgDetVV8VjWzlQRadz1RyocUXx1UiBM=; b=X63+oppt86ezkI/NaqA1t12BjYxvn3bkOKgeb4IdI9DGPFUvJA5iRxKb6YcSd2PGeR byra7Yrh2puawzM1gfLN6ZMv5LwV+Ce/NrgMwcJ6bVKrt7UmN8YlUpXTa5IY7/SleVl/ aOIzZdamzHMxSwTHEWhi5g2a9EqWVXBUuIYj4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TbJRw4t0Bp7iGv8oklQfIKqftiMRzZpEvNMglOGO0XrqDDRVcrp+ymbE5WTV/pu5lG 2azzvghG6FnrcuHlgv0Af1n4iOC3iRJopQSQ5x/aqdcB8MWMgWs/vx2rAPJTxgmdeNVG LQ1a2d9KMfi8sDghvK0uRfNdvfQF6RJR25pUQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100322085832.GZ1878@xxxxxxxxxxx>
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: <29b32d341003180643o326f7f43h97c25bd104f3b658@xxxxxxxxxxxxxx> <20100318143906.GH14445@xxxxxxxxxxxxxxxxxxx> <29b32d341003180828j3b606b2bh8267a6cadd889240@xxxxxxxxxxxxxx> <20100318162641.GA24175@xxxxxxxxxxxxxxxxxxx> <29b32d341003190827yf3cddcdgc7d4713cae41cbde@xxxxxxxxxxxxxx> <29b32d341003201850v6328f6afp1183c16ae6771cb1@xxxxxxxxxxxxxx> <29b32d341003211022k43817d37h6ed23913cf2b85af@xxxxxxxxxxxxxx> <20100321184105.GV1878@xxxxxxxxxxx> <29b32d341003211421g2a49a807obfcfd7c8b3260b74@xxxxxxxxxxxxxx> <20100322085832.GZ1878@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
While I wait for access to the system for serial debugging, I am suspecting probably .config file used to build kernel might be wrong. Is there a reference .config file for 32bit xen/next which I could compare with?

Thanks

On Mon, Mar 22, 2010 at 1:58 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Sun, Mar 21, 2010 at 02:21:31PM -0700, Ritu kaur wrote:
>    Thanks Pasi, I did look into debugging via serial console yesterday,
>    system is rack mounted and currently not a viable option for me since it
>    requires admin approval, I am looking into this. Aside from that, I
>    believe xen/next should work with xcp 0.1.1 i.e
>
>    1. xen 3.4.3.gz, xen/next kernel. Take tar-pkg built from xen/next, untar
>    it in xcp0.1.1 dom0, modify extlinux.conf to boot from 3.4.3 and new
>    kernel. will this work?
>

It should, assuming you don't have some incompatibility with xen/next and your hardware.
You might also want to try xen 4.0.0 instead of 3.4.3!

But anyway it's best to use the serial console, or SOL (Serial-Over-Lan) to capture
the boot messages, so we can actually SEE what's the problem.

-- Pasi


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