[Bug 1391919] Re: ISST-KVM:Ubuntu14.04: guest console not accessible but ssh and ping works fine
Adam Conrad
adconrad at 0c3.net
Tue May 19 22:48:04 UTC 2015
If it works on 15.04, but not 14.04, it's by accident. As in, the
installer isn't making this work, it's systemd that's spawning a console
anyway. Your XML file shows the same non-standard console setup that we
previously complained about with kimchi. Maybe this is a libvirt issue
that it's picking bizarre port addresses for the serial, but we
definitely need to relax how we look at those.
However, the initial bug report was for installing via VGA (so, no text
console) and then rebooting. Fixing that case in trusty is a bit
tougher, but we might be able to just detect the machine type and decide
those should always have an hvc0 regardless, or similar. I'll think
about it.
The reason this always works with PowerVM is the combination of (a) all
installs are text-mode, so we can always look up the root console(s)
during install, and they'll always exist, and (b) PowerVM gives us a
consistent address for hvc0/hvc1 and we therefore detect them correctly
every time. qemu/kvm allowing people to define these things willy-nilly
is marginally unhelpful.
Anyhow, the above paragraph isn't excuses, so much as an explanation for
why things work the way they do now. We assumed the world of SLOF-
under-qemu would look just like OF-under-PowerVM (and, 99% of the time,
this assumption is true), and that is biting us a bit. When I get back
from vacation later this week, I'll dream up some solid ways to deal
with the this new world order.
--
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