If during the creation of a paravirtualized Debian everything is fine in the console up to the point where "Starting local scripts" appears, after which the (guest) Linux hangs and doesn't boot any further — most likely you have misconfigured the TTY for the console.
The thing is, Xen uses its own TTY so that you can attach to its paravirtualized guest virtual systems. For different DomU systems, the correct TTY name is usually different.
For our case — Debian — the correct TTY name will be HVC0.
To resolve this issue:
A) In the machine's configuration file, specify console=hvc0 in the root line:
...
root = "root=/dev/xvda1 ro console=hvc0"
...
B) You'll need to somehow get access to the file /etc/inittty (for Squeeze) or /etc/inittab (for Lenny) in the guest system. For example, boot it with an HVM config.
In this file, change tty1 to hvc0 in the line "1:2345:respawn:/sbin/getty 38400 tty1":
...
1:2345:respawn:/sbin/getty 38400 hvc0
...
From here you can try starting the paravirtualized domain again.
Comments