Run minikube with portable VirtualBox

[jbaruteu]

The exact command to reproduce the issue:

• Run portable VirtualBox v6.0.8.
• Set environnement variable VBOX_INSTALL_PATH to point you portable VitualBox directory (containing VBoxManage).
• Run minikube start

The full output of the command that failed:

set VBOX_INSTALL_PATH=d:\Profiles\jpbaruteu\Downloads\Portable-VirtualBox\app64
minikube start

The output of the minikube logs command:

 minikube v1.1.0 on windows (amd64)
 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
E0605 14:31:22.579638     720 start.go:529] StartHost: create: creating: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

X Unable to start VM
 Error:         [VBOX_HOST_ADAPTER] create: creating: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue
 Advice:        Reboot to complete VirtualBox installation, and verify that VirtualBox is not blocked by your system
 Documentation: https://stackoverflow.com/questions/52277019/how-to-fix-vm-issue-with-minikube-start
 Related issues:
  - https://github.com/kubernetes/minikube/issues/3614
  - https://github.com/kubernetes/minikube/issues/4222

 If the above advice does not help, please let us know:
  - https://github.com/kubernetes/minikube/issues/new

The operating system version:
Windows 10

[sharifelgamal]

@jbaruteu Can you try moving your VirtualBox installation to C:? Also, can you run minikube start --alsologtostderr -v=8 and paste the output here?

[jbaruteu]

Hello sharifelgamal,

Thank you for your reply.
I made the test, mooving portable virtualbox directory to "c:". Herre is output of minikube start :

D:\>minikube start alsologtostderr -v=8
* minikube v1.1.0 on windows (amd64)
* Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
Reading certificate data from d:\Profiles\jpbaruteu\.minikube\certs\ca.pem
Decoding PEM data...
Parsing certificate...
Reading certificate data from d:\Profiles\jpbaruteu\.minikube\certs\cert.pem
Decoding PEM data...
Parsing certificate...
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe --version
STDOUT:
{
6.0.8r130520
}
STDERR:
{
}
Hyper-V is not installed.
%!(EXTRA *exec.Error=exec: "vmms.exe": executable file not found in %PATH%)COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
Downloading d:\Profiles\jpbaruteu\.minikube\cache\boot2docker.iso from file://d:/Profiles/jpbaruteu/.minikube/cache/iso/minikube-v1.1.0.iso...
Creating VirtualBox VM...
Creating SSH key...
Creating disk image...
Creating 20000 MB hard disk image...
Writing magic tar header
Writing SSH key tar header
Calling inner createDiskImage
&{c:\Portable-VirtualBox\app64\VBoxManage.exe [c:\Portable-VirtualBox\app64\VBoxManage.exe convertfromraw stdin d:\Profiles\jpbaruteu\.minikube\machines\minikube\disk.vmdk 20971520000 --format VMDK] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> <nil> false [] [] [] [] <nil> <nil>}
Starting command
Copying to stdin
Filling zeroes
Closing STDIN
Waiting on cmd
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe createvm --basefolder d:\Profiles\jpbaruteu\.minikube\machines\minikube --name minikube --register
STDOUT:
{
Virtual machine 'minikube' is created and registered.
UUID: a3f421f7-06c8-42cf-bcfd-4c04e56be9d3
Settings file: 'D:\Profiles\jpbaruteu\.minikube\machines\minikube\minikube\minikube.vbox'
}
STDERR:
{
}
VM CPUS: 2
VM Memory: 2048
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe modifyvm minikube --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 2 --memory 2048 --acpi on --ioapic on --rtcuseutc on --natdnshostresolver1 on --natdnsproxy1 off --cpuhotplug off --pae on --hpet on --hwvirtex on --nestedpaging on --largepages on --vtxvpid on --accelerate3d off --boot1 dvd
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe modifyvm minikube --nic1 nat --nictype1 virtio --cableconnected1 on
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe storagectl minikube --name SATA --add sata --hostiocache on
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe storageattach minikube --storagectl SATA --port 0 --device 0 --type dvddrive --medium d:\Profiles\jpbaruteu\.minikube\machines\minikube\boot2docker.iso
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe storageattach minikube --storagectl SATA --port 1 --device 0 --type hdd --medium d:\Profiles\jpbaruteu\.minikube\machines\minikube\disk.vmdk
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe guestproperty set minikube /VirtualBox/GuestAdd/SharedFolders/MountPrefix /
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe guestproperty set minikube /VirtualBox/GuestAdd/SharedFolders/MountDir /
STDOUT:
{
}
STDERR:
{
}
setting up shareDir '\\?\c:\Users' -> 'c/Users'
Starting the VM...
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe showvminfo minikube --machinereadable
STDOUT:
{
name="minikube"
groups="/"
ostype="Linux 2.6 / 3.x / 4.x (64-bit)"
UUID="a3f421f7-06c8-42cf-bcfd-4c04e56be9d3"
CfgFile="D:\\Profiles\\jpbaruteu\\.minikube\\machines\\minikube\\minikube\\minikube.vbox"
SnapFldr="D:\\Profiles\\jpbaruteu\\.minikube\\machines\\minikube\\minikube\\Snapshots"
LogFldr="D:\\Profiles\\jpbaruteu\\.minikube\\machines\\minikube\\minikube\\Logs"
hardwareuuid="a3f421f7-06c8-42cf-bcfd-4c04e56be9d3"
memory=2048
pagefusion="off"
vram=8
cpuexecutioncap=100
hpet="on"
cpu-profile="host"
chipset="piix3"
firmware="BIOS"
cpus=2
pae="on"
longmode="on"
triplefaultreset="off"
apic="on"
x2apic="off"
nested-hw-virt="off"
cpuid-portability-level=0
bootmenu="disabled"
boot1="dvd"
boot2="dvd"
boot3="disk"
boot4="none"
acpi="on"
ioapic="on"
biosapic="apic"
biossystemtimeoffset=0
rtcuseutc="on"
hwvirtex="on"
nestedpaging="on"
largepages="on"
vtxvpid="on"
vtxux="on"
paravirtprovider="default"
effparavirtprovider="kvm"
VMState="poweroff"
VMStateChangeTime="2019-06-07T06:43:00.344000000"
monitorcount=1
accelerate3d="off"
accelerate2dvideo="off"
teleporterenabled="off"
teleporterport=0
teleporteraddress=""
teleporterpassword=""
tracing-enabled="off"
tracing-allow-vm-access="off"
tracing-config=""
autostart-enabled="off"
autostart-delay=0
defaultfrontend=""
storagecontrollername0="SATA"
storagecontrollertype0="IntelAhci"
storagecontrollerinstance0="0"
storagecontrollermaxportcount0="30"
storagecontrollerportcount0="30"
storagecontrollerbootable0="on"
"SATA-0-0"="D:\Profiles\jpbaruteu\.minikube\machines\minikube\boot2docker.iso"
"SATA-ImageUUID-0-0"="24a1d944-5bba-4770-9561-a3d9f8bf5ac3"
"SATA-tempeject"="off"
"SATA-IsEjected"="off"
"SATA-1-0"="D:\Profiles\jpbaruteu\.minikube\machines\minikube\disk.vmdk"
"SATA-ImageUUID-1-0"="43c6cf7c-66b6-4a4a-9a23-d5983ccf71cf"
"SATA-2-0"="none"
"SATA-3-0"="none"
"SATA-4-0"="none"
"SATA-5-0"="none"
"SATA-6-0"="none"
"SATA-7-0"="none"
"SATA-8-0"="none"
"SATA-9-0"="none"
"SATA-10-0"="none"
"SATA-11-0"="none"
"SATA-12-0"="none"
"SATA-13-0"="none"
"SATA-14-0"="none"
"SATA-15-0"="none"
"SATA-16-0"="none"
"SATA-17-0"="none"
"SATA-18-0"="none"
"SATA-19-0"="none"
"SATA-20-0"="none"
"SATA-21-0"="none"
"SATA-22-0"="none"
"SATA-23-0"="none"
"SATA-24-0"="none"
"SATA-25-0"="none"
"SATA-26-0"="none"
"SATA-27-0"="none"
"SATA-28-0"="none"
"SATA-29-0"="none"
natnet1="nat"
macaddress1="08002762DAD9"
cableconnected1="on"
nic1="nat"
nictype1="virtio"
nicspeed1="0"
mtu="0"
sockSnd="64"
sockRcv="64"
tcpWndSnd="64"
tcpWndRcv="64"
nic2="none"
nic3="none"
nic4="none"
nic5="none"
nic6="none"
nic7="none"
nic8="none"
hidpointing="ps2mouse"
hidkeyboard="ps2kbd"
uart1="off"
uart2="off"
uart3="off"
uart4="off"
lpt1="off"
lpt2="off"
audio="dsound"
audio_in="off"
audio_out="off"
clipboard="disabled"
draganddrop="disabled"
vrde="off"
usb="off"
ehci="off"
xhci="off"
videocap="off"
videocapaudio="off"
capturescreens=""
capturefilename="D:\\Profiles\\jpbaruteu\\.minikube\\machines\\minikube\\minikube\\minikube.webm"
captureres="1024x768"
capturevideorate=512
capturevideofps=25
captureopts=""
GuestMemoryBalloon=0
}
STDERR:
{
}
Check network to re-create if needed...
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
Searching for hostonly interface for IPv4: 192.168.99.1 and Mask: ffffff00
Not found
Windows might ask for the permission to create a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe hostonlyif create
STDOUT:
{
}
STDERR:
{
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Could not find Host Interface Networking driver! Please reinstall
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp
}
Creating a new host-only adapter produced an error: c:\Portable-VirtualBox\app64\VBoxManage.exe hostonlyif create failed:
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Could not find Host Interface Networking driver! Please reinstall
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp

This is a known VirtualBox bug. Let's try to recover anyway...
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
COMMAND: c:\Portable-VirtualBox\app64\VBoxManage.exe list hostonlyifs
STDOUT:
{
}
STDERR:
{
}
E0607 08:43:17.307086    9220 start.go:529] StartHost: create: creating: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

X Unable to start VM
* Error:         [VBOX_HOST_ADAPTER] create: creating: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue
* Advice:        Reboot to complete VirtualBox installation, and verify that VirtualBox is not blocked by your system
* Documentation: https://stackoverflow.com/questions/52277019/how-to-fix-vm-issue-with-minikube-start
* Related issues:
  - https://github.com/kubernetes/minikube/issues/3614
  - https://github.com/kubernetes/minikube/issues/4222

* If the above advice does not help, please let us know:
  - https://github.com/kubernetes/minikube/issues/new

The problem comes from network driver which normaly creates network adapter.
Thank to this verbose output (code E_FAIL (0x80004005)), I found portable virtualbox does not work on W10 (vboxme/Portable-VirtualBox#71). It seems bridge network is not supported.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[tstromberg]

It sounds like there isn't much we can do about this - it appears to be an incompatibility with portable VirtualBox. Perhaps try the Hyper-V driver?