Xen users - Apr 2010 - Xen 4.0 - No console prompt after booting domU but functional SSH

Hello xen-users !

I am coming for help concerning the just released 4.0 version. Install has
worked rather well on my Debian Lenny. I have just had a few bugs for which
I have found the answer looking around on this list.

I have created a Debian Lenny domU which boots up just fine. The only
problem is that I am unable to get a console prompt when using "xm console
nameofdomU". I do see all the startup stuff but I see no login prompt. If I
connect to the domU via SSH, it work perfectly fine.

I have tried adding the following line to the domU configuration file which
used to work fine in Xen 3.2 but with no success :

extra       = ''xencons=tty1, clocksource=jiffies''

I have also tried with tty instead of tty1 but that doesn''t change
anything.

Am I missing something ?

Thank you in advance for your help,

Antoine Benkemoun


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

I am seeing such warning messages :

INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel

INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: Id "1" respawning too fast: disabled for 5 minutes

This is just a vanilla Debian Lenny install installed via xen-tools.

Antoine

On Tue, Apr 20, 2010 at 10:16 AM, Antoine Benkemoun <
antoine.benkemoun@gmail.com> wrote:
> Hello xen-users !
>
> I am coming for help concerning the just released 4.0 version. Install has
> worked rather well on my Debian Lenny. I have just had a few bugs for which
> I have found the answer looking around on this list.
>
> I have created a Debian Lenny domU which boots up just fine. The only
> problem is that I am unable to get a console prompt when using "xm
console
> nameofdomU". I do see all the startup stuff but I see no login prompt.
If I
> connect to the domU via SSH, it work perfectly fine.
>
> I have tried adding the following line to the domU configuration file which
> used to work fine in Xen 3.2 but with no success :
>
> extra       = ''xencons=tty1, clocksource=jiffies''
>
> I have also tried with tty instead of tty1 but that doesn''t change
> anything.
>
> Am I missing something ?
>
> Thank you in advance for your help,
>
> Antoine Benkemoun
>

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

Make sure /dev/hvc0 is set up as a login console in /etc/inittab

On 20 April 2010 09:16, Antoine Benkemoun
<antoine.benkemoun@gmail.com>wrote:
> Hello xen-users !
>
> I am coming for help concerning the just released 4.0 version. Install has
> worked rather well on my Debian Lenny. I have just had a few bugs for which
> I have found the answer looking around on this list.
>
> I have created a Debian Lenny domU which boots up just fine. The only
> problem is that I am unable to get a console prompt when using "xm
console
> nameofdomU". I do see all the startup stuff but I see no login prompt.
If I
> connect to the domU via SSH, it work perfectly fine.
>
> I have tried adding the following line to the domU configuration file which
> used to work fine in Xen 3.2 but with no success :
>
> extra       = ''xencons=tty1, clocksource=jiffies''
>
> I have also tried with tty instead of tty1 but that doesn''t change
> anything.
>
> Am I missing something ?
>
> Thank you in advance for your help,
>
> Antoine Benkemoun
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

> I have tried adding the following line to the domU configuration file which
> used to work fine in Xen 3.2 but with no success :
> 
> extra       = ''xencons=tty1, clocksource=jiffies''
extra       = ''console=hvc0 xencons=tty''
works for me.

-- Adi

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

Perfect it worked when I applied both of your suggestions !

Thank you very much for you quick answer !

On Tue, Apr 20, 2010 at 10:23 AM, Adi Kriegisch <kriegisch@vrvis.at>
wrote:
> > I have tried adding the following line to the domU configuration file
> which
> > used to work fine in Xen 3.2 but with no success :
> >
> > extra       = ''xencons=tty1, clocksource=jiffies''
> extra       = ''console=hvc0 xencons=tty''
> works for me.
>
> -- Adi
>

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

On Tue, Apr 20, 2010 at 5:27 AM, Antoine Benkemoun <
antoine.benkemoun@gmail.com> wrote:
> Perfect it worked when I applied both of your suggestions !
>
> Thank you very much for you quick answer !
>
>
> On Tue, Apr 20, 2010 at 10:23 AM, Adi Kriegisch
<kriegisch@vrvis.at>wrote:
>
>> > I have tried adding the following line to the domU configuration
file
>> which
>> > used to work fine in Xen 3.2 but with no success :
>> >
>> > extra       = ''xencons=tty1,
clocksource=jiffies''
>> extra       = ''console=hvc0 xencons=tty''
>> works for me.
>>
>> -- Adi
>>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

Hi guys,

I tried with all your recommendations but didn''t work. I have no prompt
access to the dumU. I successfully installed Xen 4.0 on Slackware64, make
world and make installed worked like a charm. I usually use images from
stacklet.com for domU''s but always 32bit. I wanted to give Slack64 a
try as
domU so downloaded it. First I tried as it comes but not able to access
console. It gave me this error:

INIT: Id "xvc0" respawning too fast: disabled for 5 minutes

I have a Debian Etch running Xen 3.0.2 and I usually have that error but
whenever I press Enter, it gave me prompt.


So I found this threaded and replaced every ttyS* with hvc0 in /etc/inittab
as well as /etc/securetty. I also added
extra       = ''console=hvc0 xencons=tty''
to domU''s config with almost same result but now I have this output:


INIT: Id "c2" respawning too fast: disabled for 5 minutes
INIT: Id "c1" respawning too fast: disabled for 5 minutes
INIT: Id "c3" respawning too fast: disabled for 5 minutes
INIT: Id "c4" respawning too fast: disabled for 5 minutes
INIT: Id "c5" respawning too fast: disabled for 5 minutes
INIT: Id "c6" respawning too fast: disabled for 5 minutes
INIT: Id "xvc0" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel

I did not try to access it using ssh as I wanted to access console first.


Any help on this will be much appreciated

Thanks and regards.

Christian


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

> domU''s but always 32bit. I wanted to give Slack64 a try as domU so
downloaded
> it. First I tried as it comes but not able to access console. It gave me
this
> error:
> 
> INIT: Id "xvc0" respawning too fast: disabled for 5 minutes
This error indicates that the corresponding device could not be
found/used/opened. In the Xen context this almost always hints at the wrong
device name.
"respawn" means reopen if connection was closed. In /etc/inittab there
are
several lines dealing with terminals (format:
<id>:<runlevels>:<action>:<process>):
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
> 
> So I found this threaded and replaced every ttyS* with hvc0 in /etc/inittab
as
> well as /etc/securetty. I also added
> extra       = ''console=hvc0 xencons=tty''
> to domU''s config with almost same result but now I have this
output:
Hmm... ttyS? Those devices refer to serial ports. In domU''s
/etc/inittab
you should look for the line with "xvc0" and just replace the
"xvc0" with
"hvc0" -- this should do the trick.

-- Adi

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

On Mon, Apr 26, 2010 at 12:08 AM, Adi Kriegisch <adi@cg.tuwien.ac.at>
wrote:
> > domU''s but always 32bit. I wanted to give Slack64 a try as
domU so
> downloaded
> > it. First I tried as it comes but not able to access console. It gave
me
> this
> > error:
> >
> > INIT: Id "xvc0" respawning too fast: disabled for 5 minutes
> This error indicates that the corresponding device could not be
> found/used/opened. In the Xen context this almost always hints at the wrong
> device name.
> "respawn" means reopen if connection was closed. In /etc/inittab
there are
> several lines dealing with terminals (format:
> <id>:<runlevels>:<action>:<process>):
> 1:2345:respawn:/sbin/getty 38400 tty1
> 2:23:respawn:/sbin/getty 38400 tty2
> 3:23:respawn:/sbin/getty 38400 tty3
> 4:23:respawn:/sbin/getty 38400 tty4
> 5:23:respawn:/sbin/getty 38400 tty5
> 6:23:respawn:/sbin/getty 38400 tty6
>
> >
> > So I found this threaded and replaced every ttyS* with hvc0 in
> /etc/inittab as
> > well as /etc/securetty. I also added
> > extra       = ''console=hvc0 xencons=tty''
> > to domU''s config with almost same result but now I have this
output:
> Hmm... ttyS? Those devices refer to serial ports. In domU''s
/etc/inittab
> you should look for the line with "xvc0" and just replace the
"xvc0" with
> "hvc0" -- this should do the trick.
>
> -- Adi
>

Yes, sir!! That did the trick!! Now I''m able to access domU through
console
without any complains.

And for the record, when I said ttyS*, I should say tty*. It was my mistake,
sorry for that.

Thanks and regards!! You save my day!!

Christian


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