Opened 17 years ago
Closed 16 years ago
#781 closed defect (invalid)
SIGSEGV when using attaching to host network interface
| Reported by: | IsakovAN | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.5.0 |
| Keywords: | tap | Cc: | |
| Guest type: | other | Host type: | other |
Description
When network interface type set to "Host interface", vboxsdl aborting during the startup.
Attachments (2)
Change History (3)
by , 17 years ago
| Attachment: | vbox.log.bz2 added |
|---|
by , 17 years ago
| Attachment: | Umnik.tar.bz2 added |
|---|
~/.VirtualBox/Machines/Umnik directory(config+log)
comment:1 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Your strace log did not show a SIGSEGV but the usual error when another session of that VM is open. The VBox log file contains the error code VERR_HOSTIF_INIT_FAILED which results from not being able to setup the tap0 device properly. I assume that this device does either not exists or was not reserved for the VBox user. Please refer to the user manual to find out how to set up a tap device properly to make it work with VirtualBox.
Should you really encounter a SIGSEGV with the current version (1.5.4), reopen this report and provide an strace which actually contains that abort reason.
"strace -f vboxsdl -vm Umnik" output