Opened 16 years ago
Closed 14 years ago
#3843 closed defect (fixed)
Network adapter disabled on every boot of VM, though settings says enabled.
Reported by: | 3vi1 | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 2.2.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
I have a WinXP guest (Ubuntu 9.10 host). Everytime I start it, the network adapter is disabled, thouth the settings show it enabled. I can right-click it and enable it using the adapter icon on the VBox window.
I used to always disable the adapter when shutting the VM down, to save time while it timesout trying to run logout scripts for a VPN connection that's not connected. This worked fine in VBox 2.1. The adapter would always be enabled on the next boot (as the machine settings indicate). Only since updating to 2.2 have I seen this odd behavior where the settings show the adapter to be enabled, but launching the VM shows otherwise. This even occurs if I don't disable the adapter when shutting the vm down.
I've tried disabling/re-enabling the adapter, and even changing the type - but the VM still always starts with the adapter disabled.
Change History (6)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
3vi1, this setting can be changed if you go into the details settings dialog of the VM network settings. I suggest you to upgrade to version 2.2.2, the dialog was improved with that version.
comment:3 by , 16 years ago
Resolution: | duplicate |
---|---|
Status: | closed → reopened |
comment:4 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
comment:5 by , 16 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
comment:6 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Please reopen if still relevant with VBox 3.2.12 / 4.0.2.
I figured out why it was showing this behavior: Somehow 'cable="false"' had made its way into the config.
I didn't see any way to change this setting through the GUI, so I edited the file manually and the VM is now behaving as expected.