From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen 4.0 does not boot up. Date: Thu, 27 May 2010 11:59:13 -0400 Message-ID: <20100527155913.GA5734@phenom.dumpdata.com> References: <20100513114014.GX17817@reaktio.net> <774702.77673.qm@web34205.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <774702.77673.qm@web34205.mail.mud.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: ccmail111 Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, May 13, 2010 at 12:48:32PM -0700, ccmail111 wrote: >=20 > Hi Pasi, >=20 > Here it is: >=20 > title Xen 4.0 debug=A0 XenLinux 2.6 > =A0=A0=A0=A0=A0=A0=A0 root (hd0,0) > =A0=A0=A0=A0=A0=A0 kernel /xen-4.0.0-rc9.gz console=3Dvga noreboot logl= vl=3Dall=A0 vga=3Dtext-80x50,keep iommu=3Doff apic=3Ddebug gues > t_loglvl=3Dall > =A0=A0=A0=A0=A0=A0 module /vmlinuz-2.6.31.13=A0 root=3D/dev/sda2 ro con= sole=3Dtty0=A0 earlyprintk=3Dxen nomodeset initcall_debug deb > ug loglevel=3D10 The console=3Dtty0 means that when initrd kicks in, the console output switches over to the tty0 (which I belive is your screen). So no more serial output. Change that to 'console=3Dhvc0'. > =A0=A0=A0=A0=A0=A0 module /ramdisk.img.gz >=20 >=20 > Now I see Xen 4.0 reboot continuously.=20 > Is there a way to capture console logs=A0 when Xen boots up ? Serial console.