Opened 13 years ago
Closed 13 years ago
#9188 closed defect (fixed)
VBoxManage Minor Issues => Fixed in SVN
Reported by: | TheShiv | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.0.10 |
Keywords: | VBoxManage | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description
These are two small issues that I think would help users who rely solely on the VBoxManage utility.
1: When you create a VM through the GUI vs VBoxManage, the default settings are not 100% the same. I first noticed this when creating a RedHat guest through the GUI, then another through VBoxManage and saw that the GUI created VM had PAE and UTC enabled by default whereas the VBoxManage one did not. It's trivial but I would think the default settings should be the same regardless how the VM is created.
2: When using storagectl/storageattach in VBoxManage it requires you to use --port and --device for SATA controllers; I understand this for IDE controllers where you would have, for instance, port 0 device 1, however, shouldn't the SATA controller only require port since device should always be 0?
Thanks!
Change History (4)
comment:1 by , 13 years ago
comment:3 by , 13 years ago
Summary: | VBoxManage Minor Issues → VBoxManage Minor Issues => Fixed in SVN |
---|
comment:4 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Your issue 1 is expected behavior - the GUI sets up a relatively fancy VM config as part of the wizard. VBoxManage creates a VM, nothing else. No storage controllers, no VM settings changed relative to the "everything disabled" default.
Issue 2 is valid, and should make it into the next release.