[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Oh, so it's explained! Thanks Javier for the data. You're using an outdated version of the package that doesn't contain this fix. You need initramfs-tools version 0.122ubuntu8.17 - you can either try to get an updated cloud image, or after the first boot you may be able to update it (you could disable the console=ttySX entry in the cmdline as a workaround in the 1st boot). If possible, please try the new version and let us all know how it goes. Cheers, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
You are welcome. This is what i see in the ubuntu image i'm running on VMware for debugging purposes: ** Attachment added: "ubuntu16.04.PNG" https://bugs.launchpad.net/cloud-images/+bug/1573095/+attachment/5436062/+files/ubuntu16.04.PNG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Thanks for the report Javier! What version of initramfs-tools are you using ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
I've been able to reproduce this with a 16.04 Amazon EC2 exported image on VMware vSphere 6.7. The VM boot fine after adding a serial port. We will try to reproduce the same workaround adding a serial console connection in OCI (which is the final target for that cloud image). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
The specific issue (the bad return from printf) was worked in LP #1879987 - it was fixed recently on initramfs-tools versions: 0.122ubuntu8.17 (Ubuntu 16.04 - Xenial) 0.130ubuntu3.11 (Ubuntu 18.04 - Bionic) 0.136ubuntu6.3 (Ubuntu 20.04 - Focal) 0.137ubuntu12 (Ubuntu 20.10 - Groovy) I'll nominate this LP for initramfs-tools and set as Fix Released. If that's still reproducible in any way, likely there's another correlated issue, please open another LP and mention it here. Cheers, Guilherme ** Changed in: cloud-images Status: Confirmed => Invalid ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Good news! Debian maintainer merged my fix today: https://salsa.debian.org/kernel-team/initramfs-tools/-/commit/c3cbf355 (after only 10 weeks heh). The Ubuntu SRU process is ongoing on LP #1879987. Cheers, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
I have tested the PPA and works great for me[1]. Given the simplicity of this fix and the way we would need to go to provide a generic fix this looks a good trade off for me. [1] https://pastebin.ubuntu.com/p/z3Jsfnf5fK/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
I agree that if we can solve one problem, with the certainty to not introduce more harm/regression, let''s do it. We should do it instead of waiting for a fix/refactoring/ that we all know won't happen in short future. My 2 cents are that if we can convince Debian upstream, let's do it. Debian maintainer will be the ultimate approver/merger. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Hi Scott, thanks for you comment. While I agree with you that simply returning 0 in one function won't solve *all* problems, it'll solve this one, in a cheap and fast way. I tend to think initramfs-tool is a quite important package, it's part of the boot process. And yet, we have plenty of 5yr+ bugs complaining about this, while we couldn't find a perfect/generic solution. So I proposed we fix this one, for the sake of the giant user base in Ubuntu and Debian, and at small steps pursue a generic solution for the write() problem, that may involve a discussion with kernel and a change in long-term behavior. I'd rather not let users waiting while we do that... Oh, and I read the other LP you mentioned, it seems a different place of failure, in a different project. I say we go and fix there too, while we work a more generic/elegant solution. But that bug (cloud-init growpart related) it's not so common than this one (here we just need to remove 'quiet' and set the wrong console to break boot completely), so that one is a bit less priority than this one. Initramfs-tools is full of quirks to prevent issues, given its relevant role in the boot process. Thanks, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
@Guilherme, Simply returning non-error (0) in one function in the initramfs isn't going to solve the problem. Anything that is checking the return value of a write() to its stdout will fail. That could be a shell 'echo', it could be a C write(). In order to take that path completion, you'd have to have all programs ignore errors when writing to stdout, which might happen to be /dev/console. Here's an example of something else (growpart) caring: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs- tools/+bug/1123220 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
We had reports of good results from an user using my PPA. Anybody else was able to test it? Cheers, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
** Tags added: id-5b49154499e416396a3e983c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Sorry for the bad formatting of last comment, I should had the line breaks fixed before submitting. I'd like to point another duplicate one which was reported by a colleague: LP #1879987. I'll close that one to keep the effort in this single LP. Cheers, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
First, I'd like to thank Scott (for comment #43) and Alejandro (comment #45) - it seems there's a bunch of LP bugs orbiting around the same issue: Ubuntu isn't bootable if we set an invalid serial console on kernel command-line (and have no "quiet" option there), it seems. Specially, I'd like to thank WGH for the great debug work on comment #46, it saved me a lot of time debugging, and you're right, it's a pain to debug issues related to console, not easy to output stuff. I used the trick to echo debug messages to the right console, helped me to narrow down some stuff. But in the end, you're debug exposed what seems to be the major problem here: due to a return value carriage among functions (starting with printf returning 1 due to bad console), we end up looping in checkfs(), preventing the boot. I respectfully disagree with Scott: although I consider there are potential improvements on kernel in the console "front", we have here a userspace bug in init scripts, due to an error in printf if console is not correctly set. I don't agree we should let it alone and pursue a kernel-only solution, specially due to the easy nature of reproducing the issue, and hard nature of debugging it. Also, it seems there are long-term bugs reporting similar issues, it bothers a bunch of people. I cannot be 100% sure we don't have more issues than the checkfs() one found by WGH, but this one is definitely an issue and an easy one to fix; I proposed a pretty simple fix in the below test-only PPA: https://launchpad.net/~gpiccoli/+archive/ubuntu/lp1573095 The more users can test that, more confidence we'll have that there are no more initramfs bugs if console is wrongly set. I agree with the idea of showing some output message on kmsg if serial console is broken, it's helpful. We can do that as part of an improvement, maybe in the same "commit" as the fix. More opinions are welcome on this matter, of course. If my solution either doesn't resolve the issue for users or is not the optimal one, let's discuss alternatives to fix this initramfs long-term flaw. Thanks, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
@wgh, My experience is that it is unfortunately not that simple. It may have worked for you. At the point in which it starts to fail, it repeatedly will fail. But up until some point, writes to stdout work fine. I believe this is because there is a buffer and it only begins failing when it has filled the buffer and tried to flush. I have a script that I had put into the initramfs in one of the other bugs that shows this. Its quite possible that the behavior has changed in 8 years, but before you basically just had to write some amount of data to determine if it would fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Although I completely agree that's the kernel could've automatically chosen the working /dev/console "backend", and that would be the best fix, this won't be fixed soon. Right now users without serial port have unexplicable hang that is pretty hard to debug. Having initramfs init script report broken /dev/console would help this situation tremendously, and the fix is very easy: just add print "$@" || echo "/dev/console appears broken" to _log_msg, and users will at least know the source of the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
I of course meant print "$@" || echo "/dev/console appears broken" >/dev/kmsg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
The real fix here is kernel improvement (or bug fix if you want to consider current kernel behavior a bug). Anything else is just going to push around the failure. That is what was determined in 2013, and its probably still true how. https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1123220/comments/8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
I debugged this problem a bit. The problem stems from initramfs
attempting to use /dev/console (which refers to nonexisting /dev/ttyS0),
having its logging functions unexpectedly return errors, and broking
everything around.
You may have already noticed that when this happens, 100% CPU time is
consumed. If you enable sysrq keys with sysrq_always_enabled=1, and dump
the task list (e.g. virsh send-key ubuntu18.04 KEY_LEFTALT KEY_SYSRQ
KEY_T), you'll notice that there's always a combination of
console_setup/loadkeys/setfont processes with evergrowing PIDs, which
likely means that something is running them in tight loop.
Now, if you patch "panic()" in /usr/share/initramfs-
tools/scripts/functions so it would print its argument to the console
(echo "panic 1: " "$@" >/dev/kmsg), you'll see that the panic reason is
that "filesystem on /dev/vda1 requires manual fsck", and it's printed in
a loop. Indeed, the function does contain a loop:
checkfs()
{
while ! _checkfs_once "$@"; do
panic "The $2 filesystem on $1 requires a manual fsck"
done
}
This is actually a bogus error. The filesystem is (most likely) fine.
There's no fsck included in initramfs, so what happens is that the
following fragment is executed:
if ! command -v fsck >/dev/null 2>&1; then
log_warning_msg "fsck not present, so skipping $NAME file
system"
return
fi
log_warning_msg, however, returns non-zero status due to stdout being
broken, which causes _checkfs_once return non-zero status as well.
panic doesn't work correctly either: it simply can't spawn a shell on
broken /dev/console, and exits immediately, and that's what causes the
infinite loop.
What I think about the solution.
First, debugging this is PITA. Adding a serial device might be a
perfectly acceptable fix for many, but when this issue happens,
absolutely nothing in the console points to the direction that this's
what's missing. Even if it's necessary to leave ttyS0 as the main
console, initramfs should at least warn the user (through kmsg) that
/dev/console is broken.
Second, errors returned by logging function causing _checkfs_once return
error as well is a bug. I think errors in _log_msg should be suppressed.
If you do that, unless panic happens (which is rare), the boot will
succeed.
Third, as Grant Emsley said, maybe ttyS0 doesn't really have to be the
main console?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573095
Title:
Cloud images fail to boot when a serial port is not available
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Related bug: * bug 1829625: Vagrant box startup timeout due to no serial port -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
I ran into this bug trying to use cloud images on Hyper-V. The workaround in #40 does work - add a serial console to the VM, and change /etc/default/grub.d/50-cloudimg-settings.cfg If you still want to be able to use a serial console if available, but not require it to be able to boot, just change the line from 'GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0"' to 'GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0 console=tty1"' Then run update-grub. It seems /dev/console takes on whichever console is listed LAST in the kernel options. If that's ttyS0 and there is no serial port connected, that breaks things. Swapping the order ensures /dev/console goes to tty1, and the boot process works with or without a serial port attached to the VM. If there is a serial port, the serial console will still work with this method. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
I just added a bunch of other bugs that really are dups of this. The goal of doing so is just to inform whoever might be looking at making a change to more context on the unfortunate complexity of doing so. Related bugs: * bug 1016695: add console=tty1 to cloud-image kernel boot parameters * bug 1123220: cloud-image VM causes kernel panic if image is resized * bug 1061977: Machine fails to commission when console=ttyS0 is present on kernel opts * bug 1573095: Cloud images fail to boot when a serial port is not available * bug 1122245: booting from a cloud image hangs until virsh console is used ** Description changed: I tried to launch a ubuntu 16.04 cloud image within KVM. The image is not booting up and hangs at "Btrfs loaded" Hypervisor env is Proxmox 4.1 [racb: see comment 40 for minimal steps to reproduce using Ubuntu- provided tooling only] + + + Related bugs: + * bug 1016695: add console=tty1 to cloud-image kernel boot parameters + * bug 1123220: cloud-image VM causes kernel panic if image is resized + * bug 1061977: Machine fails to commission when console=ttyS0 is present on kernel opts + * bug 1573095: Cloud images fail to boot when a serial port is not available + * bug 1122245: booting from a cloud image hangs until virsh console is used -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Have the same trouble when I try to deploy cloud images based templates in a cloudstack managed environment on top of esxi 6.5 (GTT VDC). Is there a way to remove that without deploying a virtual machine? I tried to tar -x the ova, modify the vmdk via guestmount on ubuntu 18 or via fuse for osx, without success. If someone can tell me an efficient and short way to remove this setting from the .ova, it could be really great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
While you can workaround the issue with ``` sudo sed -i 's/ console=ttyS0//g' /etc/default/grub.d/50-cloudimg-settings.cfg sudo update-grub ``` You need ttyS0 in grub in order to interact with vm guest using ``` virsh console ``` I added a bug to virtualbox as it could be a compound issue or an issue on how they handle ttyS0 from os. https://www.virtualbox.org/ticket/18463 ** Bug watch added: Virtualbox Trac #18463 http://www.virtualbox.org/ticket/18463 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
