You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by GitBox <gi...@apache.org> on 2020/12/09 19:29:31 UTC

[GitHub] [hbase] saintstack commented on pull request #2754: HBASE-25375 Provide a VM-based release environment

saintstack commented on pull request #2754:
URL: https://github.com/apache/hbase/pull/2754#issuecomment-741997273

FYI @ndimiduk

```
$ vagrant up
Bringing machine 'rmvm' up with 'virtualbox' provider...
==> rmvm: Checking if box 'ubuntu/bionic64' version '20201207.0.0' is up to date...
==> rmvm: Clearing any previously set forwarded ports...
==> rmvm: Clearing any previously set network interfaces...
==> rmvm: Preparing network interfaces based on configuration...
rmvm: Adapter 1: nat
==> rmvm: Forwarding ports...
rmvm: 22 (guest) => 2222 (host) (adapter 1)
==> rmvm: Running 'pre-boot' VM customizations...
==> rmvm: 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", "e3d1d940-168e-4eb4-9fc8-ff4e46d02203", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'rmvm' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
```

I'd started virtualbox ...

I updated it, and got this:

$ vagrant up
The provider 'virtualbox' that was requested to back the machine
'rmvm' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant has detected that you have a version of VirtualBox installed
that is not supported by this version of Vagrant. Please install one of
the supported versions listed below to use Vagrant:

4.0, 4.1, 4.2, 4.3, 5.0, 5.1, 5.2, 6.0

A Vagrant update may also be available that adds support for the version
you specified. Please check www.vagrantup.com/downloads.html to download
the latest version.

(I'd started it and see the rmvm as stopped in listing of machines).

Updated vagrant... brew upgrade vagrant. 2.2.4 to 2.2.14.

Then it did this again...

```
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e3d1d940-168e-4eb4-9fc8-ff4e46d02203", "--type", "headless"]

Reinstalled (because net says might work...)

brew reinstall virtualbox

... hmm... still same complaint.

This is enough comment for one text box.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org