Re: new Vagrant boxes for OpenBSD 6.3

On 06/20/2018 08:40 AM, Alceu R. de Freitas Jr. via cpan-testers-discuss 
wrote:
> Hello folks,
> 
> For those interested, I released a new Vagrant box for OpenBSD:
> 
> https://app.vagrantup.com/arfreitas/boxes/openbsd-6.3-cpan-smoker
> 
> Besides the OpenBSD version upgrade, the project now uses Packer to 
> build the VM and install OpenBSD 6.3 automatically (pretty neat stuff!).
> 
> At this moment only Virtualbox is supported, but supporting other 
> providers should be much easier now.
> 
> Regards,
> Alceu
> 

Alceu,

My colleague Andrew Villano has been experimenting with an OpenBSD-6.3 
VM sitting on a FreeBSD-11.1 host.  He reported problems with vagrant 
up.  I was away at TPC::NA most of this week.  I just now tried to get 
into that VM.  I got the same errors as Andrew.  Here's what I got:

#####
$ vagrant up && vagrant ssh
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'arfreitas/openbsd-6.3-cpan-smoker' is up 
to date...
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
     default: Adapter 1: nat
==> default: Forwarding ports...
     default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e1b82515-c71a-40ae-adb3-2e26e110ab65", "--type", 
"headless"]

Stderr: VBoxManage: error: RawFile#0 failed to create the raw output 
file 
/home/alceu/Projetos/RabbitMQ-in-Depth/Vagrant/base/ubuntu-xenial-16.04-cloudimg-console.log 
(VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), 
component ConsoleWrap, interface IConsole
#####

When I looked closely, I inferred that this box was your creation.

Can you suggest what's going wrong?

Thank you very much.
Jim Keenan