Custom Query (16363 matches)
Results (1072 - 1074 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8014 | fixed | Automount shared folder does not work in Solaris => Fixed in SVN | ||
| Description |
Auto mounting shared folders does not actually mount anything. It creates the /mnt/sf_<share> but is empty. User is in vboxsf group and GAs are installed. I can however manually mount shared folder on both of the Solaris guests. Solaris 10u9, Solaris 11 Express. If you leave the auto-mount enabled even without it actually working it does seem to cause a load on the system as if it is trying to work, but nothing ever shows. |
|||
| #126 | invalid | Autorun virtual machine on (system) startup | ||
| Description |
Another enhancement i'd like to see is the option to run VirtualBox as a service, and be able to configure that some guest machines would automatically run when VirtualBox starts running, as well as to start VB automatically with the host system. I'm sure this can accomplished with scripts and the console interface, but having this option build in into the program would definitively be a plus for servers environment. |
|||
| #119 | fixed | Availability of settings info to restrictive | ||
| Description |
When a VM is running or saved in a snapshot state, settings cannot be modified. This is understandable because those changes can only take effect when the VM is actually booted. Most info about settings is available in the read only tab sheet "Details" in the VirtualBox GUI. However, detailed info like connected virtual disks cannot be reached because the option dialog is not opened. My suggestion: make this info available (as if the VM is switched off), i.e. open the options dialog, but grey out all fields, indicating that all options are not writeable. |
|||

