Opened 10 years ago
Closed 10 years ago
#14107 closed defect (invalid)
Kernel 4.0: no host-only adapter anymore (vboxnet0)
| Reported by: | oracnick | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 4.3.26 |
| Keywords: | host-only, vboxnet0 | Cc: | |
| Guest type: | Linux | Host type: | Linux |
Description
the client VM has a host-only adapter (vboxnet0), which is working with kernel 3.9. But with kernel 4.0 the adapter vboxnet0 isn't available anymore and therefore the VM cannot start.
Attachments (2)
Change History (7)
by , 10 years ago
| Attachment: | VBox.log.1 added |
|---|
comment:1 by , 10 years ago
Can you also provide dmesg from the 4.0 kernel after the failed attempt to start the vm?
comment:2 by , 10 years ago
| Component: | network → network/hostif |
|---|
comment:3 by , 10 years ago
here is the error message when I try to create a new host-only network: Menu->File->Global settings...->network->host-only network
Es konnte kein Host-Netzinterface erzeugt werden.
VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory.
Fehlercode:NS_ERROR_FAILURE (0x80004005) Komponente:HostNetworkInterface Interface:IHostNetworkInterface {f6e556f9-d598-409b-898c-8ba99d9b05ae}
comment:4 by , 10 years ago
after re-compiling the kernel modules with - /etc/init.d/vboxdrv setup - the issue disappears. I was able to create vboxnet0 manually via the menu. (see comment 3)
Strange, I had the problem on two machines (laptop and desktop), both after switching the Linux 4.0 and both could be fixed now.
I have no idea, why the vboxnet0 disappears. However, it's working now. IMHO, bug report could be closed.
comment:5 by , 10 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Yes, you were probably missing the modules. You should see
VBoxNetFlt: Successfully started. VBoxNetAdp: Successfully started.
in your dmesg now - which is not in the dmesg you attached.
kernel 4.0