18.04 Vagrant Box long boot time

[Coury Ryan Richards]

Running in VirtualBox 6.0.4r128413
With Vagrant 2.2.3

The Ubuntu images here:
https://app.vagrantup.com/ubuntu/boxes/bionic64
https://app.vagrantup.com/ubuntu/boxes/xenial64

Have an incredibly long boot time. Vagrant times out waiting and I have not waited long enough to see it finish 45 min max.

Retrieving an ISO file from the Ubuntu server 18.04 download page and spinning up a VM from that worked successfully.

Using other vagrant boxes for other distos centos 7 specifically were able to boot as well.

Dropping back down to VirtualBox 5.2.26 successfully let both images build.

I am not a server admin so I do not have a detailed log at the moment but whatever information is needed I will assist in gathering.

[Coury Ryan Richards (nerdlyist)]

Title mis-leading and needed to point to Virtualbox not vagrant. VirtualBox 5.2.26 still boots fine.

[Dan Watkins (oddbloke)]

Hi Coury,

Thanks for filing this bug, and for using Ubuntu! Could you clarify what platform you're using when you're seeing these issues? If the host isn't Ubuntu, then you'll need to file a bug with whoever provided you with that version of Virtualbox (presumably Virtualbox upstream?).

Thanks!

Dan

[Coury Ryan Richards (nerdlyist)]

Hello Dan,

Ubuntu is a great system! I use it almost exclusively for my development.
Always looking for a way to give back. I know just opening a bug is not the
most help so whatever way I can assist I am more than happy to do.

Yes it was the latest from VirtualBox upstream. I am running on a Windows
10 host. I can open a bug with VirtualBox as well but based on my usage
other cloud-images are working fine. It seems to be the Ubuntu cloud-image
because a fresh install with the ISO worked fine.

Again if there are any more details I can provide please let me know.

Kind regards,

Coury

On Tue, Feb 12, 2019 at 11:00 AM Dan Watkins <email address hidden>
wrote:

> Hi Coury,
>
> Thanks for filing this bug, and for using Ubuntu! Could you clarify
> what platform you're using when you're seeing these issues? If the host
> isn't Ubuntu, then you'll need to file a bug with whoever provided you
> with that version of Virtualbox (presumably Virtualbox upstream?).
>
>
> Thanks!
>
> Dan
>
> ** Also affects: virtualbox (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1815409
>
> Title:
> 18.04 Vagrant Box long boot time
>
> Status in cloud-images:
> New
> Status in virtualbox package in Ubuntu:
> New
>
> Bug description:
> Running in VirtualBox 6.0.4r128413
> With Vagrant 2.2.3
>
> The Ubuntu images here:
> https://app.vagrantup.com/ubuntu/boxes/bionic64
> https://app.vagrantup.com/ubuntu/boxes/xenial64
>
> Have an incredibly long boot time. Vagrant times out waiting and I
> have not waited long enough to see it finish 45 min max.
>
> Retrieving an ISO file from the Ubuntu server 18.04 download page and
> spinning up a VM from that worked successfully.
>
> Using other vagrant boxes for other distos centos 7 specifically were
> able to boot as well.
>
> Dropping back down to VirtualBox 5.2.26 successfully let both images
> build.
>
> I am not a server admin so I do not have a detailed log at the moment
> but whatever information is needed I will assist in gathering.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-images/+bug/1815409/+subscriptions
>

--
Kind Regards,
Coury Richards
Cell [phone]
<email address hidden>

[Dan Watkins (oddbloke)]

Hi Coury,

If the same Ubuntu cloud image (launched with the same version of Vagrant) works under VirtualBox 5.2.26 but not under VirtualBox 6.0.4, then it seems to me like the problem lies with VirtualBox. We'll be more than happy to deal with any image issues that are found, but we aren't best placed to debug VirtualBox bugs, I'm afraid.

We're currently in the process of getting a version of vagrant that support VirtualBox 6 in to the Ubuntu development release (disco), and then we may be able to reproduce this issue; that may make it easier for us to identify what is happening.

Thanks!

Dan

[Coury Ryan Richards (nerdlyist)]

Hey Dan,

I actually found the root cause of the issue. I had a line in the Vagrantfile to customize the vm so that the ubuntu-bionic-18.04-cloudimg-console.log would not output. That was achieved by.

vb.customize [ "modifyvm", :id, "--uartmode1", "disconnected" ]

Basically disconnecting the serial port.

Taking that line out the machine boot fine (with a log). This is clearly a VirtualBox command and issue.

Thought I had a clean init on the vagrantfile.

Thanks,

Coury