** Description changed: + [ SRU Justification ] + There seem to be any number of ways libvirt/qemu can give us a console on a port that is "non-standard" by PowerVM/OpenFirmware standards, and this leads to a system with no getty on hvc0 because finish-install isn't particularly bright about dealing with consoles appearing at device-tree nodes it wasn't expecting. + + This SRU just sidesteps all of that and, if we're running in a KVM- + emulated pSeries machine, we unconditionally set up an upstart job for + an hvc0 console, rather than trying to do fancy detection. + + [ Test Case ] + Run a netinst with apt-setup/proposed=true to pull in the new finish-install and verify that it always creates hvc0 on a qemu machine, regardless of the location of the console. + + [ Regression Potential ] + Basically zero, as I opted for the safer route of just cargo-culting the console-creation code into a new if block, rather than trying to alter the logic to reduce code duplication and risk subtly breaking the flow for cases where hvc* might exist, despite not being a qemu PPC machine. + + [ Original Report ] -- 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 + 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 ] + * 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 ] + * 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@ubu14mdbsvr1:~# cd /etc/init root@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) + 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 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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391919 Title: ISST-KVM:Ubuntu14.04: guest console not accessible but ssh and ping works fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/finish-install/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
