Custom Query (16363 matches)
Results (376 - 378 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3824 | obsolete | .vdi appears more than once in filenames | ||
| Description |
Sometimes when creating new virtual harddisks, the .vdi extension is added twice. however, at the moment, I cannot reproduce the problem, although I experienced it twice tonight. (if I could have reproduced it, I would have added printscreens to this ticket.) maybe you can add a check right before the final creation, to make sure the .vdi extension is not twice in the filename. i.e.: virtualharddisk1.vdi.vdi (should be virtualharddisk1.vdi) |
|||
| #3829 | obsolete | Feature Request: Handling of virtual CD/DVD media | ||
| Description |
Many users just need the virtual CD/DVD media only one time (i.e. for installing the guest) - therefore adding/removing cd-media to the virtual media manager/ the guest instance creates some overhead work for the user. Just add a new option to the cdrom management property named "Ask if hard-disks are empty" (This option should be the dfault). The behavior of this function can be like that: If the vbox guest does not find a bootable media a popup window is opened which asks which media should be booted. In this popup you can select one of the cd/dvd media of the hostsystem to boot or open a file selector to select a iso-image. Iso images selected in this dialogue are not added to the virtual media manager. |
|||
| #3834 | obsolete | OpenSolaris guest has high system time overhead | ||
| Description |
We created an image using OpenSolaris 2008.11 (32-bit), MySQL, OpenDS, Glassfish to support applications. After the image boots, the apps have started and "steady state" is reached, the image has 30-35% system time constantly being consumed. We've seen this on vbox 2.0.x, 2.1.x, and 2.2.x. We've seen this happen on the following Host OS platforms: OpenSolaris on Sun Ultra40 (AMD) Mac OS X on MacBookPro (Intel) Linux (Ubuntu 8.10) on Toshiba Laptop (Intel) Windows XP on Acer Laptop (AMD)
I "profiled the kernel" using a dtrace script and the kernel is calling: unix I'll attach the output of the script and the dtrace script This might be related to bug # 894 |
|||

