Custom Query (16363 matches)
Results (2080 - 2082 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15971 | fixed | "VBoxManage storagectl" missing options in the documentation | ||
| Description |
The User Manual and the help for the VBoxManage command do not show all the available options for the '--add' and '--controller' options. Please see the post https://forums.virtualbox.org/viewtopic.php?f=9&t=79862&p=373416#p373416 where it is described in full detail. If necessary I can re-post the details here. |
|||
| #15972 | fixed | "VBoxManage storagectl --add sas" gets USB controller | ||
| Description |
Issue the command: VBoxManage storagectl <uuid|name> --name <name> --add sas without specifying the controller type. The command is perfectly accepted, the interface is created but the controller type is set to USB both in the tooltip and in the "VBoxManage showvminfo", but not in the GUI where it is shown as LSILogicSAS. What is a USB controller doing there? ;) |
|||
| #15999 | fixed | RamSize wrong value in VBox.log | ||
| Description |
Create a VM. Any will do. Set the memory to a non nice, binary, "round" number, for example 3043 MB (I just saw it on a test case, don't blame me). Here's what VBox.log has to say about it: RamSize <integer> = 0x00000000be300000 (3 190 816 768, 2 GB) Although the RAM is set to 2.97 GB, it is identified as 2 GB. Yes, it is correctly identified to the byte, but it is not correctly identified in the "human readable" version. Some sort of lower(), int() conversion? This should be trivial to fix. And since we're at it, it would make sense to report that value in MB, the same that it is reported everywhere else, like the total host memory or the available host memory. BTW, I left the VBox version as empty, because this is way older behavior than the current 5.1.6 |
|||

