[xen-tools-discuss] Re: lenny domU hangs on lenny dom0
me at darkstar.be
Fri Mar 13 19:33:54 CET 2009
I think on domU it needs to be xva0 instead of ttyX, if you want I can
look when I'm at a real PC.
You'll prob see high CPU load as well as a result of that same config
On 13 Mar 2009, at 18:26, pietro <pietro at riseup.net> wrote:
> Alex Smith wrote:
>> If I remember correctly, this could be to do with /etc/inittab not
>> having the correct settings in it. You should fine that you can ssh
>> the domU still - I don't have the exact settings to hand at the
>> but if you can't find them I can dig the out for you.
>> Also think it can be set in the xen-tools config (at the bottom).
> right before your reply i tried ssh'ing to the domU and it worked. i
> just can't "xm console" into it. so not a big deal. but i'd like to
> able to do so. the issue here is that i'm using "hvc0" for serial
> console access on the dom0.
> On xen-tools.cfg on the dom0 "serial_device" is commented out. What
> should it be so I can "xm console" into the domU and still use
> serial to
> access the dom0?
> my configuration grub menu.lst for serial:
> serial=--unit=0 --speed=115200 --word=8 --parity=no --stop=1
> terminal=--timeout=10 serial console
> title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-1-
> root (hd0,0)
> kernel /xen-3.2-1-i386.gz com1=115200,8n1 console=com1,vg
> module /vmlinuz-2.6.26-1-xen-686
> root=/dev/mapper/vg_waxwing0-root ro console=tty0 console=hvc0
> module /initrd.img-2.6.26-1-xen-686
> the inittab on the dom0:
> 1:2345:respawn:/sbin/getty 38400 hvc0
> 2:23:respawn:/sbin/getty 38400 tty1
> 3:23:respawn:/sbin/getty 38400 tty2
> 4:23:respawn:/sbin/getty 38400 tty3
> 5:23:respawn:/sbin/getty 38400 tty4
> 6:23:respawn:/sbin/getty 38400 tty5
> there is *no* getty on ttyS0
> the inittab on the domU has only:
> 1:2345:respawn:/sbin/getty 38400 tty1
More information about the xen-tools-discuss