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-users

Re: [Xen-users] Re: Unable to xm console in a running domU

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: Unable to xm console in a running domU
From: "Andy Burns" <xen.lists@xxxxxxxxxxx>
Date: Mon, 1 Sep 2008 19:18:55 +0100
Delivery-date: Mon, 01 Sep 2008 11:19:31 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=z0TsY4Lzcqk4/h1vMsDl8cY02svBVOPr8sN/9r5cfcQ=; b=BKqJORzDyPZQ+JCt7e8OEBXj9hD9xBtgWu/232o4iQj2aSKSwaeh62ICgPNBJFXCUA r7b4b/+yUFOeZ4I7fYYg2Ay8EvOWimewMSq5YrhPMEkcJyBvy02c+Rfti2dzAY31uZT6 zEgtO1IyM/cUZ3FZH58YzeSmIokWeQJWHJTRg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=SZDcmH/Q9Hbr/jnUElPQllMFPnCentTHxKOoyZQjSqUDhQn3KjvLBETS/DHW3lQ4F+ Rp3WI1Nvey8olfeF2wKj4JWPyv2/7LxMUSV51dDIqR/UaGRobVsx16BkrZOOxqQAc3LN 94DG4NhNhbPCOtOgYP4S0B7GEhafCb2/6fJpM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <55da14450809011109n69dd8be1q1a85fe4fd7f217f8@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <55da14450809011040p24c76daco45386aba6af3d31e@xxxxxxxxxxxxxx> <55da14450809011044g371a9106u743b906045927659@xxxxxxxxxxxxxx> <b4057d410809011050t7668ebc4rfce8f8b991502c46@xxxxxxxxxxxxxx> <55da14450809011102l32948e93g290a5f9d3e8ef250@xxxxxxxxxxxxxx> <55da14450809011109n69dd8be1q1a85fe4fd7f217f8@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
2008/9/1 Thomas <iamkenzo@xxxxxxxxx>:

> config file:
> extra = "TERM=xterm xencons=tty console=tty1"
>
> and inittab:
> 1:2345:respawn:/sbin/getty 38400 tty1
>
> Now after the boot sequence is complete, the tty1 console appears. But
> I am still unable to "xm console" into the domU.

Since you are seeing the console messages at startup/shutdown  think
the actual xvc0 is working, just that you haven't got the getty
command right to allow login once it's up, when you do xm console,
does it connect (without login) and let you disconnect with ctrl-5 or
ctrl-[

Here is the inittab line from one of my CentOS domUs

co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav

worth a try.

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