Comment # 3 on bug 867068 from Charles Arnold

(In reply to Bill Weidman from comment #0)

Sorry for the very slow response.  If this issue still matters to you
see the inlined comments below.

> User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8)
> AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.90 Safari/537.1
> 
> Xen 13.1 domU guest console is inaccessible immediately after installation.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Install 13.1 x86_64 domU in Xen 13.1 x86_64 dom0
> 2. Shut down guest
> 3. Change config files to boot using pygrub

This is done automatically when you use vm-install to install
a para-virtualized VM. How are you installing the domU?

> 4. Boot guest
> 5. Connect to console in dom0 "xl console guestname"

Connecting works for me after installing using vm-install.
See more info below.

> 
> Actual Results:  
> Console doesn't accept input
> 
> linux-wo1f login: root
> [   50.844129] tty_ldisc_hangup_halt: waiting (login) for xvc0 took too
> long, but we keep waiting...
> 
> Expected Results:  
> Xen guest console accepts inputs when connected to in dom0
> 
> Looks like a yast installation problem
> 
> To fix I did the following. Not sure if this is the best way to fix, but
> this is how I did it.
> 
> Add console=xvc0  to /boot/grub/menu.lst
>  kernel /boot/vmlinuz-3.11.10-7-xen root=/dev/xvda2 resume=/dev/xvda1
> splash=0 console=xvc0 showopts

The installed PV domU already has the /dev/xvc0 device without adding
this to menu.lst.

> 
> Then echo "xvc0"  >> /etc/securetty

This is done automatically by the installation (for PV domUs). It
also adds in the /etc/inittab file the following line,
x0:12345:respawn:/sbin/agetty -L 9600 xvc0 xterm

Are you using some special autoyast file when installing your
domUs that bypass this?

> 
> Then 
> ln -s '/usr/lib/systemd/system/getty@.service'
> '/etc/systemd/system/getty.target.wants/getty@xvc0.service'

I've never had to do this. I again wonder how you installed
the domU?