Bug 249133 - sysutils/packer emulators/virtualbox-ose ubuntu vm boot from packer crashes, continually reboots
Summary: sysutils/packer emulators/virtualbox-ose ubuntu vm boot from packer crashes, ...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Nikolai Lifanov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-05 21:00 UTC by freebsd
Modified: 2020-09-15 04:24 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (lifanov)


Attachments
ubuntu .json spec for packer (2.88 KB, application/json)
2020-09-05 21:00 UTC, freebsd
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description freebsd 2020-09-05 21:00:34 UTC
Created attachment 217771 [details]
ubuntu .json spec for packer

11.3-RELEASE-p6
packer-1.6.0
virtualbox-ose-5.2.44
virtualbox-ose-additions-5.2.44
virtualbox-ose-kmod-5.2.44
vagrant-2.2.9_1

All ports installed using pkg install on 2020-08-26

If I create a ubuntu-18.04.5 VM from ubuntu-18.04.5-live-server-amd64.iso directly in virtualbox, the VM is created successfully.

However, if I try to do the same thing using packer, the VM boots and starts the install process, automatically filling in prompts up to the point of choosing the disk allocation.  From there I choose the defaults, set user id, machine name, password, check box for ssh.  The install begins but then fails when fetching updates of some sort (about #16) and reboots and starts the install process all over again.  Unfortunately, it sticks a big error box up over the output and then crashes and reboots quickly, so I can't really see what's going on.

packer .json file is attached.

Side note: despite the fact that the virtualbox-ose-additions are installed, they are not found by virtualbox.  They are fetched as part of the build process so I don't think that's the issue.

I have modified the system as recommended:

kldload vboxdrv.ko

sysctl vfs.aio.max_buf_aio=8192
sysctl vfs.aio.max_aio_queue_per_proc=65536
sysctl vfs.aio.max_aio_per_proc=8192
sysctl vfs.aio.max_aio_queue=65536
Comment 1 Mikael Urankar freebsd_committer 2020-09-09 11:51:59 UTC
Why is it a FreeBSD bug? You should ask on an Ubuntu bug tracker.
Comment 2 freebsd 2020-09-15 04:24:55 UTC
I thought it was an fbsd bug related to the interplay between packer and virtualbox, based on the fact that a vagrant instance comes up fine and a virtualbox instance comes up fine.

However, an attempt to boot from the iso on bare (different) hardware exhibits the same problem -- pretty weird.  I've verified the checksum.  So checking further, will take some time.  It's obviously not a fbsd bug.