Custom Query (16363 matches)
Results (2086 - 2088 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11962 | fixed | creating new virtual disk detects host free disk space incorrectly => Fixed in SVN | ||
| Description |
The free-disk-space is checked on the drive where "VirtualBox VMs" folder resides instead of inside this folder. The folder is in my case a directory symlink to another drive so the free space inside this folder is different than in any of the parent folders or the drive where the symlink resides. to create such symlink use: symlink /d "VirtualBox VMs" "d:\somedir\VirtualBox VMs" (while in the folder c:\Users\user\ where user is some admin user on windows; this assumes you moved "c:\Users\user\VirtualBox VMs\" folder to "d:\somedir\" before executing the symlink command) I'll add some screenshots illustrating the free disk space differences and the error I get from virtualbox in this case (trying to make a 20gig virtual disk) |
|||
| #10405 | fixed | creating hostonlyifs segfaults | ||
| Description |
running vboxmanage hostonlyif create returns: VBoxManage: error: Argument *aHostNetworkInterface is NULL VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component Host, interface IHost, callee nsISupports Context: "CreateHostOnlyNetworkInterface (hif.asOutParam(), progress.asOutParam())" at line 64 of file VBoxManageHostonly.cpp Segmentation fault We are unable to create the interface. Only manually adding it to the VirtualBox.xml solves the issue. |
|||
| #2035 | obsolete | creating fixed size images is slow | ||
| Description |
When a fixed size image is created the OS first writes the image (the progress bar is empty and lots of disk writes are reported) and then the disk manager writes it again at about half the rate of the OS (now the progress bar shows the progress). Both passes are very slow and there is no need to duplicate the writes. |
|||

