search

divx118 / crouton-packages

Kernel-headers packages to use with crouton
56 stars 16 forks source link

Cannot create host-only adapter #22

Closed Asuza closed 7 years ago

Asuza commented 8 years ago

When running vboxmanage hostonlyif create (which is being called from running vagrant up in my Homestead folder), I receive the following error:

⟩ vboxmanage hostonlyif create
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: VBoxNetAdpCtl: ioctl failed for /dev/vboxnetctl: Invalid argument
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterface, interface IHostNetworkInterface
VBoxManage: error: Context: "int handleCreate(HandlerArg*, int, int*)" at line 66 of file VBoxManageHostonly.cpp

Does this indicate I did something wrong during the linux header and virtualbox installation? Is something else wrong? I tried restarting virtualbox, which seems to fix the problem for most people... however, nothing I do seems to get it to work.

I don't know if this is helpful, but here is the end of the dmesg output:

[   52.834395] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,data=ordered
[   53.501255] systemd-logind[17761]: Failed to enable subscription: Launch helper exited with unknown return code 1
[   53.501305] systemd-logind[17761]: Failed to fully start up daemon: Input/output error
[   53.545913] systemd-logind[17793]: Failed to enable subscription: Launch helper exited with unknown return code 1
[   53.545945] systemd-logind[17793]: Failed to fully start up daemon: Input/output error
[   53.647329] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.10.18/updates/dkms/vboxdrv.ko" pid=17815 cmdline="modprobe vboxdrv"
[   53.653689] vboxdrv: Found 2 processor cores.
[   53.653917] vboxdrv: fAsync=0 offMin=0x514 offMax=0x854
[   53.654060] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[   53.654068] vboxdrv: Successfully loaded version 4.3.18_Debian (interface 0x001a0008).
[   53.656027] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.10.18/updates/dkms/vboxpci.ko" pid=17817 cmdline="modprobe vboxpci"
[   53.656782] vboxpci: pci-stub module not available, cannot detach PCI devices
[   53.656792] vboxpci: IOMMU not found (not compiled)
[   53.658276] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.10.18/updates/dkms/vboxnetadp.ko" pid=17818 cmdline="modprobe vboxnetadp"
[   53.663607] Chromium OS LSM: init_module locking-ignored module="/lib/modules/3.10.18/updates/dkms/vboxnetflt.ko" pid=17824 cmdline="modprobe vboxnetflt"
[   53.698307] systemd-logind[17841]: Failed to enable subscription: Launch helper exited with unknown return code 1
[   53.698339] systemd-logind[17841]: Failed to fully start up daemon: Input/output error
[  668.173831] systemd-logind[20107]: Failed to enable subscription: Launch helper exited with unknown return code 1
[  668.173864] systemd-logind[20107]: Failed to fully start up daemon: Input/output error
[  673.308267] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,data=ordered
[  673.701878] systemd-logind[20571]: Failed to enable subscription: Launch helper exited with unknown return code 1
[  673.701921] systemd-logind[20571]: Failed to fully start up daemon: Input/output error
[  673.778024] systemd-logind[20603]: Failed to enable subscription: Launch helper exited with unknown return code 1
[  673.778072] systemd-logind[20603]: Failed to fully start up daemon: Input/output error
[  673.907524] systemd-logind[20652]: Failed to enable subscription: Launch helper exited with unknown return code 1
[  673.907572] systemd-logind[20652]: Failed to fully start up daemon: Input/output error
[  749.551059] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)

Thank you!

divx118 commented 8 years ago

No, you didn't do anything wrong. hostonly adapter does not work. I think it has something to do with the kernel config chromeos is using, but am not sure. I never had to use it, so didn't dive to deep into it.

Asuza commented 8 years ago

Alright, thanks, @divx118! I searched online for far too long and couldn't find an answer, and you've put my mind at ease. I'll have to check into whether Vagrant can use some other type of networking with VirtualBox.