VirtualBox

Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#9740 closed defect (fixed)

"Cable connected" option is not persisted with "Paravirtualized Network"

Reported by: danf84 Owned by:
Component: network Version: VirtualBox 4.1.4
Keywords: Cc:
Guest type: Windows Host type: Windows

Description (last modified by Frank Mehnert)

Before starting the VM, set "Adapter 1" to NAT, set adapter type to "Paravirtualized Network", and untick "Cable connected".

Start the VM, when logged on, while the VM is running, tick "Cable connected" in Network settings. Restart the VM - the cable is reported as unplugged in the OS, despite the new settings showing that "Cable connected" option is ticked.

The only solution is to shutdown the VM, then start it (there's no need to change the settings, just a shutdown and start again).

The same problem will occur if you start with "Cable connected" ticked", and when the VM starts, untick "Cable connected", and when you restart the VM, the OS reported that the cable is still plugged in.

Guest: XP, host Windows 7 x64.

Attachments (1)

TEST-2012-07-20-12-17-18.log (74.9 KB ) - added by danf84 12 years ago.

Download all attachments as: .zip

Change History (4)

comment:1 by Frank Mehnert, 12 years ago

Please attach a VBox.log file for such a VM session. I don't have a Windows XP guest with paravirtualized network drivers available but I couldn't reproduce this problem with a Linux guest.

comment:2 by Frank Mehnert, 12 years ago

Description: modified (diff)
Resolution: fixed
Status: newclosed

No response, closing.

by danf84, 12 years ago

comment:3 by danf84, 12 years ago

Same problem with 4.1.18; attached the log file from a clean vm, I ran it for the first time with cable unplugged, when booted into the OS, set cable to plugged in, then restarted the guest, the cable became unplugged again.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use