[Bug 1829625] Re: Vagrant box startup timeout due to no serial port

[Bert Driehuis]

I suspect the partyline is that cloudimage shall support serial console
come hell or high water. If that's the case, as an alternative to
modifying cloudimage to suite vagrant, it might make sense to petition
vagrant to provide a sensible default for the serial console to suit
cloudimage.

I ran into this with vagrant 2.2.9 and Ubuntu focal64.

If the cloudimage team can enlighten us about the rationale for
requesting ttyS0 I'll be happy to do the legwork with vagrant.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1829625

Title:
  Vagrant box startup timeout due to no serial port

Status in cloud-images:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  due to this issue the boot time of ubuntu 19.04 (disco) requires about
  2minutes on my systems instead of about 5-7 seconds.

  environment:
  * ubuntu 18.04
  * vagrant v2.0.2
  * virtualbox 6.0.8

  steps to reproduce:
  1) initialize vagrant: `vagrant init ubuntu/disco64`
  2) start vagrant image: `vagrant up`

  get the virtual machine name or uuid, and read the 'uartmode1' setup:
  `VBoxManage showvminfo <uuid|vmname> --machinereadable |grep ^uart`
  will result in:
  ----
  uart1="0x03f8,4"
  uartmode1="disconnected"
  uarttype1="16550A"
  uart2="off"
  uart3="off"
  uart4="off"
  ----

  with 'uartmode1' disconnected, meaning 'ttyS0' not attached to the vm
  ubuntu 19.04 will take a long time to boot.

  with previous ubuntu versions this works fine, e.g. cosmic64 or
  bionic64.

  ----
  uart1="0x03f8,4"
  uartmode1="file,/somedir/vagrant-test-cosmic64/ubuntu-cosmic-18.10-cloudimg-console.log"
  uarttype1="16550A"
  uart2="off"
  uart3="off"
  uart4="off"
  ----

  if the ttyS0 should no longer be attached by default then the grub parameter 'GRUB_CMDLINE_LINUX_DEFAULT' in '/etc/default/grub.d/50-cloudimg-settings.cfg' needs to be adjusted from:
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0"
  to 
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty1"

  
  the impact is best visible when the vm is started with a gui, either from virtualbox gui or with vagrant in 'Vagrantfile':
  ----
     config.vm.provider "virtualbox" do |vb|
       # Display the VirtualBox GUI when booting the machine
       vb.gui = true  
     end
  ----

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1829625/+subscriptions