Custom Query (16363 matches)
Results (1960 - 1962 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12473 | obsolete | Full cloning does not clone when floppy disk is present | ||
| Description |
A full clone is never created. The error states that the same UUID exists for the original .img file and the cloned .img file. As far as I know, there is no way in VBoxManage to assign a UUID or clone a .img file to get a different UUID. From my simple testing, it appears that one can use the OS to copy a floppy .img file to another file name and there is no UUID conflict -- the Virtual Media Manager will not complain. Consequently, the only way to do a full clone of a VM with a floppy attached is to first detach the floppy .img file, perform the full clone, manually copy the original floppy .img to the clone with another file name, re-attach the original floppy .img to the original VM, and attach the copied and renamed floppy .img to the cloned VM. |
|||
| #13532 | worksforme | NAT#0: Configuration error: network '10.0.%octet1%/8' describes not a valid IPv4 network | ||
| Description |
This occurs in the log when starting a VM defined with NIC1 using NAT. There are many VMs using NAT at the time on different VMs; the actual message the user saw when using "VBoxManage startvm" is: VBoxManage: error: NAT#0: Configuration error: network '10.0.30400107640ctet18' describes not a valid IPv4 network (VERR_INVALID_PARAMETER). VBoxManage: error: Failed to attach the network LUN (VERR_INVALID_PARAMETER) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Consol e, interface IConsole I had this happen for two different VM users and two different guest OSes. |
|||
| #17653 | obsolete | VERR_NO_LOW_MEMORY | ||
| Description |
# VBoxManage startvm win10a --type headless Waiting for VM "win10a" to power on... VBoxManage: error: VM creation failed (GVMM) (VERR_NO_LOW_MEMORY) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole This message has been appearing for the first time, perhaps since an upgrade to 5.2.8. There are 16 running VMs on other login accounts. Total virtual RAM allocated to VMs is no more than 64GB of 256GB physical RAM. |
|||

