Re: new Vagrant boxes for OpenBSD 6.3

[email protected] (Alceu Rodrigues de Freitas Junior via cpan-testers-discuss)
Newsgroups perl.cpan.testers.discuss
Message-ID <[email protected]>
Hello guys,

I did some more fixes that might workaround in what it seems is a bug 
with Vagrant and/or Virtualbox and release a new version for the box:

https://app.vagrantup.com/arfreitas/boxes/openbsd-6.3-cpan-smoker/versions/0.0.2

Please let me know if that fixes this issue. It seems this console log 
is causing problems elsewhere too.

In worst case scenarios... I also fixed bugs with the Packer 
configuration, so you should be able to build the box yourselves. Once 
the box is created and you add it to your local cache, you can hit 
"vagrant up" and see what happens.

Please let me know of the results.

Thanks,

Alceu



Em 22/06/2018 23:06, James E Keenan escreveu:
> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.