Re: [Xen-users] Installing a Debian Etch DomU using debootstrap

[Thomas <iamkenzo@xxxxxxxxx>]

I am still having the problem with the tty. I cannot xm console into a
running domU.

My setup is: dom0: Debian Etch with a custom kernel. My domU is a
Debian Etch with kernel 2.6.18-6-xen-amd64

I have discovered that for domU with 2.6.18 one must use xvc0, and
with kernels >= 2.6.25 one must use hvc0.

I have finally managed to use debootstrap to create a VM. When my VM
gets created, I see the console appear if I use "xm create -c VM", and
the console is tty1. But if I do ctrl+] to leave the console, I can no
longer "xm console" into. However when I do "xm reboot VM", then if I
am fast enough, I can "xm console" into it.

What is wrong with my configuration? I know I am missing a piece in
this puzzle what is it? This is getting crazy.

Here is my configuration file:
---
extra = 'console=xvc0 xencons=xvc0' # Use xvc0 for kernel 2.6.18
#extra = 'console=hvc0 xencons=hvc0' # Use hvc0 for kernels >= 2.6.25
---

My /etc/inittab:
---
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
---

/etc/securetty:
---
 /etc/securetty: list of terminals on which root is allowed to login.
# See securetty(5) and login(1).
console
xvc0
hvc0
...
----

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