Re: [Xen-users] Xen 4.0 - No console prompt after booting domU but functional SSH

[Christian Gonzalez <zulsolar@xxxxxxxxx>]

On Mon, Apr 26, 2010 at 12:08 AM, Adi Kriegisch <adi@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users