Opened 13 years ago
Closed 8 years ago
#9433 closed defect (obsolete)
"IDE controller hotplug error" while connecting network cables
Reported by: | pepak | Owned by: | |
---|---|---|---|
Component: | GUI | Version: | VirtualBox 4.1.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description (last modified by )
I have a virtual machine (Windows on Windows, though the problem is universal) created with a network adapter installed but its cable disconnected. After I run this machine, I open the "Devices -> Network adapters" menu, check the "cable connected" option and click OK. This should connect the virtual machine to the network, and did just that in 4.0 and older versions. In 4.1, however, I get a "Failed to save the settings of the virtual machine ... Controller 'IDE Controller' does not support hotpluggin". Which is entirely correct, the IDE controller is not hot-pluggable, but why am I getting this message while changing tne network settings??
This happens for all of my virtual machines.
Attachments (2)
Change History (6)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Sure I can. I don't see anything relevant written into it, but I can do it. I am also attaching the machine setup. The error message given is:
Failed to save the settings of the virtual machine Windows XP Lite to C:\...\Windows XP Lite.vbox. Controller 'IDE Controller' does not support hotplugging.
Details: Result Code: VBOX_E_INVALID_VM_STATE (0x80BB0002) Component: SessionMachine Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}
by , 13 years ago
Log of the session. Powered off right after the error appeared.
comment:3 by , 12 years ago
I note that I was experiencing this error in one VM but not another. On investigating, I found the problem went away if I choose 'Enable USB 2.0 controller' under Ports > USB in Settings. So it seems to be associated only with the basic USB 1 controller.
comment:4 by , 8 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
This is not reproducible here, can you attach a log of the VM please?