[Bug 1391919] Comment bridged from LTC Bugzilla
bugproxy
bugproxy at us.ibm.com
Tue May 5 05:09:37 UTC 2015
------- Comment From hellerda at us.ibm.com 2015-05-05 05:04 EDT-------
A few more thoughts: The situation may be more complicated on PowerKVM due there being many ways to create the console device in the domain file. What I mean is: it's possible there is some domain configuration that makes 14.04 work as-is, and I just haven't seen it. The bug I just worked on had a configuration like this, with no "video" or "graphics" stanza:
<serial type='pty'>
<source path='/dev/pts/4'/>
<target type='isa-serial' port='0'/>
<alias name='serial0'/>
<address type='spapr-vio' reg='0x30001000'/>
</serial>
<console type='pty' tty='/dev/pts/4'>
<source path='/dev/pts/4'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
<address type='spapr-vio' reg='0x30001000'/>
</console>
Honestly, I'm not even clear how the console gets mapped to /dev/hvc0 on
PowerKVM. On x86 KVM a similar-looking config maps the console to
/dev/ttyS0. But in all cases, the device can be gleaned from
/proc/consoles.
And of course, I'm considering only what is seen over the text console
accessed by "virsh console". There are additional ttys mapped to the
video console, and that's something that's also a bit different between
x86 and Power..
Anyway, without going into more detail that may not be relevant: I'd
like to understand how hvc0.conf is created, why it's not being created
in some cases, and if ensuring it is created might just be the simple
fix.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1391919
Title:
ISST-KVM:Ubuntu14.04: guest console not accessible but ssh and ping
works fine
Status in debian-installer package in Ubuntu:
Confirmed
Bug description:
-- Problem Description --
I installed a guest with ubuntu14.04 using vga over vnc using kimchi. All setup was done, i could ping, ssh to guest, access guest using kimchi. But to access guest using "virsh console":
1. Removed video and graphics line from xml
2. Destroyed guest
3. Started guest using "virsh start --console <<guestname>>
After this guest hangs and dmesg is as follows:
* Starting SystemD login management service [ OK ]
* Starting load fallback graphics devices [fail]
* Starting configure network device security [ OK ]
* Starting system logging daemon [ OK ]
* Starting save udev log and update rules [ OK ]
* Stopping rpcsec_gss daemon [ OK ]
* Stopping save udev log and update rules [ OK ]
* Starting set console font [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Stopping set console font [ OK ]
* Starting userspace bootsplash [ OK ]
* Stopping userspace bootsplash [ OK ]
* Starting Send an event to indicate plymouth is up [ OK ]
* Stopping Send an event to indicate plymouth is up [ OK ]
* Starting configure virtual network devices [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device [ OK ]
* Starting Mount network filesystems [ OK ]
* Starting Upstart job to start rpcbind on boot only [ OK ]
* Starting Failsafe Boot Delay [ OK ]
* Stopping Upstart job to start rpcbind on boot only [ OK ]
* Stopping Failsafe Boot Delay [ OK ]
* Starting System V initialisation compatibility [ OK ]
* Stopping Mount network filesystems [ OK ]
* Starting configure network device [ OK ]
* Starting Mount network filesystems [ OK ]
* Stopping Mount network filesystems [ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
* Starting RPC portmapper replacement [ OK ]
* Starting NSM status monitor [ OK ]
* Starting AppArmor profiles [ OK ]
* Starting Bridge file events into upstart [ OK ]
* Starting Bridge socket events into upstart [ OK ]
* Stopping System V initialisation compatibility [ OK ]
* Starting System V runlevel compatibility [ OK ]
* Starting save kernel messages [ OK ]
* Starting internet superserver inetd [ OK ]
* Stopping save kernel messages [ OK ]
* Restoring resolver state... [ OK ]
* Starting CPU interrupts balancing daemon [ OK ]
* Stopping System V runlevel compatibility [ OK ]
I can ping and ssh to guest when machine is in hung state.
It seems it is not giving console output due to below error
Starting load fallback graphics devices
[fail]
Problem occurs when video and graphics lines are deleted, cannot
access console of guest. But we can ssh to guest.
Logging into your system:
root at ubu14mdbsvr1:~# cd /etc/init
root at ubu14mdbsvr1:/etc/init# cat hvc0.conf
cat: hvc0.conf: No such file or directory
On my Ubuntu guest, I have the following in hvc0.conf:
# hvc0 - getty
#
# This service maintains a getty on hvc0 from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345] and (
not-container or
container CONTAINER=lxc or
container CONTAINER=lxc-libvirt)
stop on runlevel [!2345]
respawn
exec /sbin/getty -L hvc0 9600 vt100
I expect if you create that file and issue a `start hvc0`, you will be able to login. I believe the Ubuntu installer when using graphics mode assumes you will maintain graphics mode and you are responsible as the user to setup the hvc0 login.
I created "hvc0.conf" file in /etc/init, issued `start hvc0` and i
could access the console of guest. It worked.
Problem persists in 14.10. General sense is that we should require
that regardless of the installation method (graphical or not), hvc0 is
always enabled on powerkvm guests, from a customer perspective.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1391919/+subscriptions
More information about the foundations-bugs
mailing list