Opened 9 years ago
Closed 9 years ago
#14308 closed defect (fixed)
Can not modify nic while the vm is running via cli [Fixed in SVN]
Reported by: | carmark | Owned by: | |
---|---|---|---|
Component: | VM control | Version: | VirtualBox 5.0.0 |
Keywords: | vboxmanage controlvm nat | Cc: | |
Guest type: | Linux | Host type: | all |
Description
Hello everyone,
I can not subscribe the virtualbox user mailing list, so I have to send to this alias to report an issue. When I did some tests on Mac via command line, I found an error while the vm was running by the following command:
vboxmanage controlvm vm-xxxx nic1 nat
It reported that "VBoxManage: error: The machine is not mutable (state is Running)", however the GUI can work well to change the network mode.
My environment is latest virtualbox(5.0, released in 9th. July), both of Mac version and Linux version will fail. I could run that command with virtualbox 4.3.x, so I think I am right to run that command.
So could you please check that?
Change History (6)
comment:1 by , 9 years ago
Summary: | Can not modify nic while the vm is running via cli → Can not modify nic while the vm is running via cli [Fixed in SVN] |
---|
comment:3 by , 9 years ago
I'm using VBox 5.0.2 and I still can not do one of the supposedly supported 'controlvm nic<n>' commands:
VBoxManage controlvm <machine> nic3 null (still doesn't work in 5.0.2) VBoxManage controlvm <machine> nic3 nat (works in 5.0.2)
I have used the above sequence to force my guest OS to understand changes in the host networks (Wire->WLAN and WLAN->Wire).
Should I write a new ticket?
comment:4 by , 9 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
No thanks, I will reopen this ticket. We will have another look...
comment:5 by , 9 years ago
Oops, my bad, missed the "null" case. Should be fixed in the next dot-dot release.
The fix will be in the next dot release.