Custom Query (16363 matches)
Results (2014 - 2016 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12200 | fixed | Change the way "Install Guest Additions..." is handled -> fixed as of 22 October 2013 (4.3 branch and later) | ||
| Description |
I've seen a lot of people complain that after going to the "Install Guest Additions..." (IGA) menu, the Guest Additions (GAs) are not installed on their guest VMs. This is because they do not realize that the only thing that IGA does is to insert the VB GAs in their CD drive and that additional action is needed to actually install the GAs. I propose to: 1) Have a dialog box with a warning that they there are additional steps to actually have the GAs installed. Optionally a "Do not show this again" checkbox. 2) Change the wording from "Install Guest Additions..." to "Insert Guest Additions CDROM..." |
|||
| #3718 | duplicate | Change the way vdi files are created to allow for later expansion | ||
| Description |
From reading the forums it seems like I am just one of many who wants to be able to increase the size of an existing virtual disk image. After reading http://forums.virtualbox.org/viewtopic.php?t=8046 I think there is an easy solution to the underlying problem of not being able to resize a virtual disk image. As I understand it the vdi consists of a 512 byte header followed by the block image map, followed by the image blocks. Currently the block image map is sized according to how large the user has said they want the image to be. If the user later says they want the image to be larger then all the image blocks would need to be moved up in the file in order to make room for the extra blocks that are now required in the block image map. This could result in having to copy many gigabytes of data around and would be very slow. What would happen if the vdi files were always created with a minimum size of 4M for the block image map (i.e. enough blocks to access 1 terabyte of image data) ? If an extra field was added to the header to specify the current size of the simulated disk then expanding the size of an existing vdi would be as simple as updating the new header entry to reflect the new larger disk size. Obviously this would only work so long as the new size is less than 1 terabyte but that would almost certainly be good enough for the majority of users who currently hit this problem. Or have I missed something obvious here ? |
|||
| #18474 | duplicate | Change time stamp of Vbox.log to absolute date and time | ||
| Description |
I have read https://www.virtualbox.org/ticket/15949, however it is still better to log absolute date and time in release logs since it is quite difficult to calculate time based on relative time. |
|||

