VBoxManage list hdds
VBoxManage modifymedium PATH/TO/TARGET.vdi --compact
hdiutil eject /dev/diskXsX
hdiutil compact PATH/TO/TARGET.sparsebundle

sudo installer -package /Volumes/VirtualBox/VirtualBox.pkg -target /

hdiutil compact TARGET.sparsebundle

VBoxManage modifyhd list
VBoxManage modifyhd PATH/TO/TARGET.vdi --compact
hdiutil eject /dev/diskXsX
hdiutil compact PATH/TO/TARGET.sparsebundle

> sdelete.exe -z c:

$ dd if=/dev/zero of=zero bs=4k; \rm zero

$ VBoxManage list hdds

$ VBoxManage modifyhd [UUID] --compact

$ VBoxManage clonehd --format VDI /path/to/disk.vmdk /tmp/disk.vdi
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Clone medium created in format 'VDI'. UUID: ffffffff-ffff-ffff-ffff-ffffffffffff

$ brew cask install virtualbox

$ sudo VBoxManage extpack install --replace /opt/homebrew-cask/Caskroom/virtualbox-extension-pack/5.0.2-102096/Oracle_VM_VirtualBox_Extension_Pack-5.0.2-102096.vbox-extpack

$ ovftool --acceptAllEulas /path/to/example.vmwarevm/example.vmx /tmp/example.ova

Failed to import appliance /Users/yoshiki/windows10.ova.

Error reading "/Users/yoshiki/windows10.ova": Host resource of type "Other Storage Device (20)" is supported with SATA AHCI controllers only, line 47.

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: ApplianceWrap
Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}

$ tar xvf windows10.ova
$ windows10.ovf
$ windows10.mf
$ windows10-disk1.vmdk

<!--
  <Item>
    <rasd:Address>0</rasd:Address>
    <rasd:Description>SATA Controller</rasd:Description>
    <rasd:ElementName>sataController0</rasd:ElementName>
    <rasd:InstanceID>3</rasd:InstanceID>
    <rasd:ResourceSubType>vmware.sata.ahci</rasd:ResourceSubType>
    <rasd:ResourceType>20</rasd:ResourceType>
  </Item>
-->

$ sha1sum windows10.ovf
8f5a3bd15ea17829ac76cbbcdb57c9a4ee3a7ab5  windows10.ovf

SHA1(windows10.ovf)= <.ovfのSHA1ハッシュ>
SHA1(windows10-disk1.vmdk)= <.vmdkのSHA1ハッシュ> 

$ CBoxManage import windows10.ovf

$ sudo usermod -aG vboxsf $(whoami)

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p /vagrant

Stdout from the command:



Stderr from the command:

sudo: no tty present and no askpass program specified

# aptitude install build-essential module-assistant
# aptitude install linux-headers-amd64
# export KERN_DIR=/usr/src/linux-headers-X.X.X-X-amd64
# /etc/init.d/vboxadd setup
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.

Building the main Guest Additions module ...done.
Building the shared folder support module ...done.
Building the OpenGL support module ...done.
Doing non-kernel setup of the Guest Additions ...done.
You should restart your guest to make sure the new modules are actually used

[default] The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.

Guest Additions Version: 4.1.8
VirtualBox Version: 4.2

$ sudo mount /dev/cdrom /media/cdrom
[sudo] password for vagrant:
mount: block device /dev/sr0 is write-protected, mounting read-only

$ cd /media/cdrom0
$ ./VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.2.18 Guest Additions for Linux............
This program must be run with administrator privileges.  Aborting
vagrant@debian:/media/cdrom0$ sudo ./VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.2.18 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 4.1.8 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.

Building the main Guest Additions module ...done.
Building the shared folder support module ...done.
Building the OpenGL support module ...done.
Doing non-kernel setup of the Guest Additions ...done.
You should restart your guest to make sure the new modules are actually used

Installing the Window System drivers ...fail!
(Could not find the X.Org or XFree86 Window System.)

$ ls /opt
VBoxGuestAdditions-4.2.18
$ /opt/VBoxGuestAdditions-4.2.18/bin/VBoxControl --version
4.2.18r88780