From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ritu kaur <ritu.kaur.us@gmail.com>
Subject: Re: domU guest for xcp 0.1.1
Date: Sun, 21 Mar 2010 14:21:31 -0700
Message-ID: <29b32d341003211421g2a49a807obfcfd7c8b3260b74@mail.gmail.com>
References: <29b32d341003171144k628a7741x17b6658731f96e4b@mail.gmail.com>
	<29b32d341003180643o326f7f43h97c25bd104f3b658@mail.gmail.com>
	<1268921503.10129.39640.camel@zakaz.uk.xensource.com>
	<20100318143906.GH14445@phenom.dumpdata.com>
	<29b32d341003180828j3b606b2bh8267a6cadd889240@mail.gmail.com>
	<20100318162641.GA24175@phenom.dumpdata.com>
	<29b32d341003190827yf3cddcdgc7d4713cae41cbde@mail.gmail.com>
	<29b32d341003201850v6328f6afp1183c16ae6771cb1@mail.gmail.com>
	<29b32d341003211022k43817d37h6ed23913cf2b85af@mail.gmail.com>
	<20100321184105.GV1878@reaktio.net>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2071697997=="
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20100321184105.GV1878@reaktio.net>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=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?= <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

--===============2071697997==
Content-Type: multipart/alternative; boundary=001636b14a5312ff3d0482562ad0

--001636b14a5312ff3d0482562ad0
Content-Type: text/plain; charset=ISO-8859-1

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?

Thanks

--001636b14a5312ff3d0482562ad0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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/nex=
t should work with xcp 0.1.1 i.e<br>
<br>1. xen 3.4.3.gz, xen/next kernel. Take tar-pkg built from xen/next, unt=
ar it in xcp0.1.1 dom0, modify extlinux.conf to boot from 3.4.3 and new ker=
nel. will this work?<br><br>Thanks<br><br>

--001636b14a5312ff3d0482562ad0--


--===============2071697997==
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

--===============2071697997==--