[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From lagar...@br.ibm.com 2015-05-28 17:54 EDT--- (In reply to comment #57) > (In reply to comment #54) > > 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. > > > So, can someone provide an example of the "standard" console setup in the > XML, that will make this work? I suppose that if you use 0x3000 as the address for the serial console that should work on Ubuntu, as explained before on LTC bug 110860 comment 12. -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From helle...@us.ibm.com 2015-05-28 16:21 EDT--- (In reply to comment #54) > 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. > So, can someone provide an example of the "standard" console setup in the XML, that will make this work? -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From lagar...@br.ibm.com 2015-05-22 18:10 EDT--- (In reply to comment #48) > 2) The console he set up was using an old kimchi default that used a > non-standard address we don't look for. Newer versions of kimchi > are meant to use a more standard address to work around that, but > it's still an Ubuntu bug that we blatantly ignore random consoles. I don't think this has changed in newer versions of Kimchi, and from libvirt documentation, Kimchi is just following libvirt's convention: https://libvirt.org/formatdomain.html#elementsAddress type='spapr-vio' On PowerPC pseries guests, devices can be assigned to the SPAPR-VIO bus. It has a flat 64-bit address space; by convention, devices are generally assigned at a non-zero multiple of 0x1000, but other addresses are valid and permitted by libvirt. Each address has the following additional attribute: reg (the hex value address of the starting register). Since 0.9.9. -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From helle...@us.ibm.com 2015-05-19 04:44 EDT--- (In reply to comment #48) > > I'd like to understand how hvc0.conf is created, why it's not > > being created in some cases, > > The installer uses various means to detect if a serial console is in use and > creates the upstart job on the fly. > As I suggested above, maybe checking /proc/consoles, if it's not already doing that? > > and if ensuring it is created might just be the simple fix. > > Yes that is the correct fix. > Yeah, if we think there's no harm in always adding the file, let's just do that and be done with it, :-) > The slightly more long-winded analysis I tossed in an email a few minutes > ago: > > So, there are two (maybe three) issues in play with this specific bug. > FYI, I just worked on a bug that was a dup of this and... > 1) The console wasn't in use as "The Console" when we installed, which > we (probably incorrectly, in this case) key off of to decide what > console to set up. > In my case it was the console used for install: a text-based install using "virsh console", and it was recognized as hvc0. > 2) The console he set up was using an old kimchi default that used a > non-standard address we don't look for. Newer versions of kimchi > are meant to use a more standard address to work around that, but > it's still an Ubuntu bug that we blatantly ignore random consoles. > In my case no kimchi, just generic PowerKVM and virsh. > 3) He may not have had that console configured at install time at all, > and we only probe for and setup up console jobs in the installer, > we make no attempt to do so at boot time. So, if new consoles were > to show up on second or fifth boot, tough look, no console for you. > In my case console was present (and used) at install. > The first two bugs are ones we can and should fix in trusty. The third > is probably a wart we need to live with, but can probably fix a bit > better with systemd in 15.04/15.10/16.04. Actually it works in 15.04. We only need a fix for 14.04 LTS, and then only on PowerKVM. It works on PowerVM. Not sure about 14.10, but I'm guessing it's broken there too if that is pre-systemd. -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From helle...@us.ibm.com 2015-05-05 14:30 EDT--- *** Bug 124322 has been marked as a duplicate of this bug. *** -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From helle...@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: 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 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From helle...@us.ibm.com 2015-05-05 04:55 EDT--- Apparently this is still a problem for 14.04 on PowerKVM. I just looked at a bug that was dup of this (LTC bug 124322). It was a 14.04.2 with 3.13.0-51 kernel, but I think this affects all 14.04 LTS. Adding the "hvc0.conf" as described above fixed it. This doesn't seem to be a problem for 15.04. GA level 15.04 on the same PowerKVM guest worked fine. There are some differences between 14.04 and 15.04; the latter uses systemd to manage the gettys 14.04 and uses initscripts (upstart)? But the requirement is the same: we must have a getty running on hvc0. This also doesn't seem to be a problem for 14.04 in the PowerVM environment, and I'm not sure why. Both appear to use hvc0 for the text console, but on PowerVM /etc/init/hvc0.conf is getting created and on PowerKVM it is not. (It's also not a problem for 14.04 on x86 KVM, which uses a device other than /dev/hvc0...) I noticed that most of the other, similar files are owned by upstart: $ dpkg-query -L upstart | egrep "tty|console" /etc/init/console.conf /etc/init/tty1.conf /etc/init/tty2.conf /etc/init/tty3.conf /etc/init/tty4.conf /etc/init/tty5.conf /etc/init/tty6.conf But I could not find the owner of hvc0.conf, and by the timestamp is clear it is created at intall time: $ dpkg-query -S /etc/init/hvc0.conf dpkg-query: no path found matching pattern /etc/init/hvc0.conf $ ll /etc/init/hvc0.conf -rw-r--r-- 1 root root 353 May 5 00:01 /etc/init/hvc0.conf Can we get someone from Canonical to explain how this file is created, and why we might be getting it in PowerVM but not PowerKVM? I noticed in both PowerVM and PowerKVM, /proc/consoles lists hvc0... $ cat /proc/consoles hvc0 -W- (EC) 229:0 $ cat /proc/devices | grep 229 229 hvc So maybe this can be used as an indicator of when hvc0.conf should be created? -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From helle...@us.ibm.com 2015-05-02 05:57 EDT--- *** Bug 124322 has been marked as a duplicate of this bug. *** -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From helle...@us.ibm.com 2015-02-21 18:49 EDT--- *** Bug 121875 has been marked as a duplicate of this bug. *** -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391919] Comment bridged from LTC Bugzilla
--- Comment From vaish...@in.ibm.com 2015-02-02 09:11 EDT--- Any updates on this bug ? -- 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/debian-installer/+bug/1391919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
