booting from a cloud image hangs until virsh console is used

[Vincent Ladeuil]

on a quantal host:
  sudo virt-install --noautoconsole --network network=default --video cirrus --name selftest --ram 1024 --vcpus 2, --disk path=/caviar3/libvirt/installers/ubuntu/raring-server-cloudimg-amd64-disk1.img,format=qcow2 --boot hd --hvm

With raring-server-cloudimg-amd64-disk1.img downloaded from http://cloud-images.ubuntu.com/raring/current/.

The graphical console (from virt-manager) will display some lines ending with:

 [ 0.000000] console [tty1] enabled

and the guest cpu is at 100%.

Running 'virsh console selftest' and typing return from the kbd will unblock it.

After the boot completes, if I edit /etc/default/grub to remove ttyS0 from GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0" the hand doesn't occur.

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

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1122245/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ben Howard (darkmuggle-deactivatedaccount)]

Marking this as confirmed. I was able to replicate this with virtinst, but not with generic KVM. I believe that this is related to the VNC options:

Here is the KVM config used by virsh:

/usr/bin/kvm-spice \
      -name selftest \
      -S -M pc-1.2 \
      -enable-kvm \
      -m 1024 \
      -smp 2,sockets=2,cores=1,threads=1 \
      -uuid 48f92f8b-7eaf-46c0-e74a-41b12e716cbf \
      -no-user-config \
      -nodefaults \
      -chardev socket,id=charmonitor,path=/home/ben/.config/libvirt/qemu/lib/selftest.monitor,server,nowait \
      -mon chardev=charmonitor,id=monitor,mode=control \
      -rtc base=utc \
      -no-shutdown \
      -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \
      -drive file=/work/images/raring-server-cloudimg-amd64-disk1.img,if=none,id=drive-ide0-0-0,format=qcow2 \
      -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 \
      -netdev user,id=hostnet0 \
      -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:72:26:91,bus=pci.0,addr=0x3 \
      -chardev pty,id=charserial0 \
      -device isa-serial,chardev=charserial0,id=serial0 \
      -vnc 127.0.0.1:0 \
      -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4

[Scott Moser (smoser)]

not related to vnc i dont think I think its related to console options.
I really think the tty1 i mentioned was a red-herring.

[Scott Moser (smoser)]

I'd like to see if this was a regression in libvirt or kvm, by basically running and reporting
 precise host with precise guest
 precise host with quantal guest
 quantal host with quantal guest
 quantal host with precise guest

To me, this feels like fallout of a libvirt change if it is a regression. If it is not regression, then we'll figure out some way to invoke virt-inst/libvirt that doesn't trip this issue .

Outside of trying to do some polling/poking around in grub2 magic, I really dont know how we could otherwise get the right kenrel cmdline.

[Vincent Ladeuil (vila)]

quantal host with precise guest: the bug doesn't occur, so at least the precise cloud image works

[Vincent Ladeuil (vila)]

quantal host with quantal guest: the bug occurs

[Serge Hallyn (serge-hallyn)]

Given the affected releases are all EOL, I will mark this bug invalid. If anyone still sees this happen, please re-open.

[Guilherme G. Piccoli (gpiccoli)]

This is pretty much related with the initramfs-tools issue 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)

Cheers,

Guilherme