Custom Query (16363 matches)
Results (2452 - 2454 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5042 | fixed | Crashes on save machine state and resume machine state => Fixed in SVN/3.0.8 | ||
| Description |
MacOS 10.5.8 host WindowsXP SP3 guest VirtualBox 3.0.6 (guest disk and installation created under VirtualBox 3.0.5) 15 out of all attempts (17 total) to "Save machine state" resulted in a VM crash and a status listed as "Aborted", which must is followed by a cold boot, windows chkdsk, and occasionally guest data loss from files open during the failed state save. 2 out of the 17 attempts successfully saved state, showing status as "Saved", but in both cases were followed by a VM crash on attempting to resume that state, again leaving the status listed as "Aborted" and requiring a cold start up. Uploading examples of a log from each of the two types of state-related crash... |
|||
| #12491 | duplicate | Crashes running Ubuntu_64. | ||
| Description |
Virtual Box crashes after installing Ubuntu_64. |
|||
| #9238 | fixed | Crashes when any VDI files are deleted | ||
| Description |
If you manually delete any VDI whether it be a hard disk or any snapshot then VirtualBox will show E_ACCESSDENIED error message but it'll then crash. If you manually delete a hard disk VDI then it'll crash when VirtualBox opens or when you open the Virtual Media Manager window. If you manually delete a snapshot image then it'll crash when you view snapshots. The only remedy was to manually modify the XML to exclude the stuffed VM and then reinstall. Running Windows 7 x64. Stu |
|||

