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: Wed, 31 Mar 2010 14:10:59 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Wed, 31 Mar 2010 14:11:17 -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:received:message-id:subject:from:to:cc:content-type; bh=Wko031NhkoL5FHBM/y/XmwFKDKv1GAXCyNMo98pcMYs=; b=DWy4MnDU9lWuG233Fy1fhvceRHs1AK4K2WD/DALAMDAruFsKeDUwF+huExOMTHxfGL sZHDQ7tvElVqLAbE0Pt75NjArUjuaXr4C0pgFSNLSsLmijI+7wYV7al6iXVrbkiLwrER Km3DffJlIudIKQDwinPoIB6iBMH5DY/9p4E0A=
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=ifzjoAwpOXEKWtgsDLss+ndZffSxyiyeqIp0P0BvTb0I1jik/VsiDp+TKbZYM+L+hB 9wRNKMfF9sCdnCOFCHZ6zFc761vCO2Y3+MO1iYatUPmDX1DB8+ku/JNbdyV5vPPcUluz qp430PDz4ysQtXJZ67ihHGLrqWxrihw2O3FwA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100331143913.GL1878@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: <29b32d341003271832p5337a2e4q70e443face36030b@xxxxxxxxxxxxxx> <20100328113439.GO1878@xxxxxxxxxxx> <20100328115550.GQ1878@xxxxxxxxxxx> <h2q29b32d341003301728q8b505cebx1c0326d9451121f5@xxxxxxxxxxxxxx> <w2p29b32d341003301807gf1d41307u422737add9e20f71@xxxxxxxxxxxxxx> <20100331063035.GI1878@xxxxxxxxxxx> <z2r29b32d341003310615wd6a0a690nac365f3011aaf5cf@xxxxxxxxxxxxxx> <20100331134210.GD28074@xxxxxxxxxxxxxxxxxxx> <k2w29b32d341003310655ha47eb0e4y88f85e34f3aec964@xxxxxxxxxxxxxx> <20100331143913.GL1878@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Attached xen debug logs. Just to update this is with xen/next and xcp0.1.1 as dom0. Inputs appreciated.

Thanks


On Wed, Mar 31, 2010 at 7:39 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Wed, Mar 31, 2010 at 06:55:54AM -0700, Ritu kaur wrote:
>    Konrad, yes it is a null-modem cable. Cable was bought for this testing.
>

First get it working on baremetal Linux (non-Xen), then continue with Xen.

-- Pasi

>    Thanks
>
>    On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk
>    <[1]konrad.wilk@xxxxxxxxxx> wrote:
>
>      On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:
>      > It's a onboard serial port. From dmesg there are ttyS0 and ttyS1 ports
>      are
>      > shown and I have tried both of them.
>
>      And the cable you have, it is a null modem serial cable? Have you ever
>      had serial cable working (say with baremetal Linux?)
>
> References
>
>    Visible links
>    1. mailto:konrad.wilk@xxxxxxxxxx

Attachment: xen-debugs.xcp
Description: Binary data

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