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
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
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
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
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
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
** 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:
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
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.
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+
@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
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
** 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
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
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
@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
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
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
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.
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
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
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
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
*
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,
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
25 matches
Mail list logo
