From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Thu, 1 Apr 2010 05:48:45 -0700 Message-ID: References: <29b32d341003271832p5337a2e4q70e443face36030b@mail.gmail.com> <20100328115550.GQ1878@reaktio.net> <20100331063035.GI1878@reaktio.net> <20100331134210.GD28074@phenom.dumpdata.com> <20100331143913.GL1878@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2108983764==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org --===============2108983764== Content-Type: multipart/alternative; boundary=001636b2b0e38ed29504832c48f1 --001636b2b0e38ed29504832c48f1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pasi, Sorry to bother. Any inputs on debugs provided? Thanks On Wed, Mar 31, 2010 at 2:10 PM, Ritu kaur wrote: > 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=E4rkk=E4inen 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 Xe= n. >> >> -- Pasi >> >> > Thanks >> > >> > On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk >> > <[1]konrad.wilk@oracle.com> 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 ttyS= 1 >> 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@oracle.com >> > > --001636b2b0e38ed29504832c48f1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pasi,

Sorry to bother. Any inputs on debugs provided?

Than= ks

On Wed, Mar 31, 2010 at 2:10 PM, Ritu = kaur <ritu.kaur.us= @gmail.com> wrote:
Attached xen debu= g logs. Just to update this is with xen/next and xcp0.1.1 as dom0. Inputs a= ppreciated.

Thanks



On Wed, Mar 31, 2010 at 7:39 AM, Pasi K=E4rkk=E4inen <pasik@iki.fi&= gt; wrote:
On Wed, Mar = 31, 2010 at 06:55:54AM -0700, Ritu kaur wrote:
> =A0 =A0Konrad, yes it is a null-modem cable. Cable was boug= ht for this testing.
>

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

-- Pasi

> =A0 =A0Thanks
>
> =A0 =A0On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk
> =A0 =A0<[1]konrad.wilk@oracle.com> wrote:
>
> =A0 =A0 =A0On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:<= br> > =A0 =A0 =A0> It's a onboard serial port. From dmesg there are t= tyS0 and ttyS1 ports
> =A0 =A0 =A0are
> =A0 =A0 =A0> shown and I have tried both of them.
>
> =A0 =A0 =A0And the cable you have, it is a null modem serial cable? Ha= ve you ever
> =A0 =A0 =A0had serial cable working (say with baremetal Linux?)
>
> References
>
> =A0 =A0Visible links
> =A0 =A01. mailto:konrad.wilk@oracle.com


--001636b2b0e38ed29504832c48f1-- --===============2108983764== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============2108983764==--