Custom Query (16363 matches)
Results (76 - 78 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #21301 | duplicate | Please restore 'Restore current snapshot' | ||
| Description |
This option has been removed in V7 when closing a VM and it is very inconvenient for me (and others from forum posts). Please restore it or add an option setting to do so. Thank you. |
|||
| #21297 | duplicate | Missing option to "Restore current snapshot" when close VM in VirtualBox 7 | ||
| Description |
After upgrading to VB7, the first thing I noticed on closing a VM was that the option to "restore current snapshot" was missing. This was a great feature, and removing it is very annoying! I have several VMs set up as test platforms and regularly start them, carry out a test (e.g. installing or running a program), then close the VM to restore its clean "snapshot" state. Having to go back to the main UI and restore the snapshot manually is an inconvenient extra step. After using VirtualBox for many years, this issue has prompted me to create an account and raise the issue in the hope it will be addressed. |
|||
| #21292 | invalid | Shared folders between 64 bit host and 32 bit guests corrupt data. | ||
| Description |
Writing to files shared via VirtualBox shared folders between a 64 bit host and a 32 bit linux guest leads to corrupted file contents on the opposing side.
This appears to be an issue between the upstream Creating a file on the host side and viewing it on the guest side, yields:
Please note that this also applies to files that were already present, when the folder was first mounted in the VM. Creating a file on the guest side and viewing it on the host side, yields:
Please note that when creating and later viewing a file on the guest side, its contents only appear unscathed for as long as the file stays in the cache. After executing a This issue has been observed:
Neither the VirtualBox nor the vboxsf kernel module report any problems in either case. -- People at Mageia have encountered what is probably the same issue and you can find the report including more elaborate analysis into what's happening here: https://bugs.mageia.org/show_bug.cgi?id=26214 I have discussed this problem in more detail in the context of a VirtualBox forum post that describes a similar issue, here: https://forums.virtualbox.org/viewtopic.php?f=6&t=105367&start=15#p523118 |
|||

