[Pkg-xen-devel] xen 2.6.26 on amd64 console troubles
freggy at gmail.com
Fri Oct 10 09:48:17 UTC 2008
On Fri, Oct 10, 2008 at 11:00 AM, Ian Campbell <ijc at hellion.org.uk> wrote:
> On Fri, 2008-10-10 at 10:44 +0200, Frederik wrote:
>> I just installed xen-linux-system-2.6.26-1-xen-amd64 2.6.26-7 on a
>> freshly installed Debian Lenny AMD64 system, and when I create a
>> Debian Lenny DomU with xen-tools I cannot attach to a console nor log
>> in with SSH. When running
>> # xm create -c test.cfg
>> the system starts booting, but it seems to "freeze" after the kernel has booted.
>> Googling a bit, shows that I seem to have the problem that the kernel
>> is not finding or using the correct console:
>> Currently, I'm trying this in /etc/xen/test.cfg:
>> extra = "console=hvc0 xencons=hvc0"
>> and in the DomU I have in /etc/inittab:
>> 1:2345:respawn:/sbin/getty 38400 tty1
> Needs to be hvc0 not tty1?
No, that does not work. In the end I get:
INIT: Entering runlevel: 2
Starting enhanced syslogd: rsyslogd.
Starting OpenBSD Secure Shell server: sshd.
Starting periodic command scheduler: crond.
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
The only workaround that somehow works is
extra = "console=hvc0 xencons=hvc0" and tty1 ini inittab. Then I get a console,
but it's limited to 80 chars wide. And the SSH problem still happens.
>> When I run xm create -c test.cfg, nothing happens anymore once all
>> init scripts have finished (no login prompt appears). And when I try
>> to log in via SSH, I get:
>> PTY allocation request failed on channel 0
>> stdin: is not a tty
> Dunno about that one.
More information about the Pkg-xen-devel