unxmaal / booterizer

Ansible-based bootstrap environment for old UNIXes
MIT License
79 stars 14 forks source link

add vdi using vbox 6.xxx #19

Open dillera opened 5 years ago

dillera commented 5 years ago

adding the VDI fails, even in fix-vfi branch....

==> default: Running 'pre-boot' VM customizations...
A customization command failed:

["createhd", "--filename", "/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi", "--size", 51200]

The following error was experienced:

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

Command: ["createhd", "--filename", "/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi", "--size", "51200"]

Stderr: 0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to create medium
VBoxManage: error: Could not create the medium storage unit '/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi'.
VBoxManage: error: VDI: cannot create image '/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi' (VERR_ALREADY_EXISTS)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCreateMedium(HandlerArg *)" at line 450 of file VBoxManageDisk.cpp
>

Please fix this customization and try again.

virtualbox: 6.0.12,133076

dillera commented 5 years ago

commands to clean env:

dillera@massiveprime ~/code/booterizer-2019 (fix_vdi) $ rm installdisk.vdi 
dillera@massiveprime ~/code/booterizer-2019 (fix_vdi) $ rm -rf .vagrant
dillera@massiveprime ~/code/booterizer-2019 (fix_vdi) $ vagrant up
dillera commented 5 years ago

full output:

dillera@massiveprime ~/code/booterizer-2019 (fix_vdi) $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'debian/contrib-jessie64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'debian/contrib-jessie64' version '8.11.0' is up to date...
==> default: Setting the name of the VM: booterizer-2019_default_1571690750945_43866
==> default: Clearing any previously set network interfaces...
==> default: Specific bridge 'en0' not found. You may be asked to specify
==> default: which network to bridge to.
==> default: Available bridged network interfaces:
1) en0: Ethernet 1
2) en1: Ethernet 3
3) en2: Wi-Fi 2 (AirPort)
4) p2p0
==> default: When choosing an interface, it is usually the one that is
==> default: being used to connect to the internet.
    default: Which interface should the network bridge to? 1
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: bridged
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
A customization command failed:

["createhd", "--filename", "/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi", "--size", 51200]

The following error was experienced:

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

Command: ["createhd", "--filename", "/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi", "--size", "51200"]

Stderr: 0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to create medium
VBoxManage: error: Could not create the medium storage unit '/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi'.
VBoxManage: error: VDI: cannot create image '/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi' (VERR_ALREADY_EXISTS)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCreateMedium(HandlerArg *)" at line 450 of file VBoxManageDisk.cpp
>

Please fix this customization and try again.