[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] DomU Console Flow of Control


  • To: xen-users@xxxxxxxxxxxxxxxxxxx, Pasi Kärkkäinen <pasik@xxxxxx>
  • From: John Riedl <riedl@xxxxxxxxxx>
  • Date: Sun, 7 Feb 2010 14:06:50 -0600
  • Cc:
  • Delivery-date: Sun, 07 Feb 2010 12:07:28 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ZjdAn+9YsU6nXLeb7GcqQm7vWh8VG5gOmsjASQVtKfBixI0M3Who5zgBAupmy83VS8 Bm8cOy+fsOf2eJND4631BwgPszuOViWBDr7MJzP0dV7R/Ejp4zJy4F9X6bEVJChIUCXt 9heInvV+m9OwpySOfzJNHyEt1HUR6R4Cy6PqA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Thank you for the reply.  Letting me know that getty needed to be
running and the pointer to the Common Problems wiki page
http://wiki.xensource.com/xenwiki/XenCommonProblems was just the help
I needed.

Turned out my twin problems were :

1) After trying both xvc0 and hvc0 I was incorrectly concentrating on
xvc0 since that's what was working on my hardy domUs. On the pv_ops
kernels, including the recent Ubuntu -server kernels, the correct
device is hvc0.  /dev/hvc0 exists on my karmic installs.

2) getty does not start on /dev/hvc0 by default on karmic.  To start
it, just copy /etc/init/tty1.conf to /etc/init/hvc0.conf, and edit
appropriately.

After that, console works as advertised on both my upgraded karmic,
and my new install.

Thanks!
John

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.