Custom Query (16363 matches)
Results (2446 - 2448 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| #2508 | duplicate | crash (Guru meditation / PF) while installing Windows NT4 | ||||||||||||||||||||||
| Description |
Host: MacOS X 10.5.5 Guest: Windows NT 4 |
|||||||||||||||||||||||
| #2509 | obsolete | Microchip mpasm.exe assembly puts VB into an infinite loop | ||||||||||||||||||||||
| Description |
If you run mpasm.exe 4.11 from Microchip (basically a text mode MSDOS program) VirtualBox goes into an infinite loop. The MS Windows XP SP 3 session does not respond at all. the VirtualBox session in the Linux host space run all out. It will not respond to a kill, but kill -9 works. The MS Windows session and the Virtual Box application are completely unresponsive. |
|||||||||||||||||||||||
| #2510 | fixed | Snapshot fails if SATA port > 1 | ||||||||||||||||||||||
| Description |
I have observed that it is impossible to take snapshots of a VirtualBox machine if it has any disk images attached to SATA ports 2 and higher. This condition results in an error message that the VDI file is is use by another task. I have reliably been able to reproduce this in a new VirtualBox VM by attaching any hard drives to any SATA port with the exception of 0 and 1 with Windows Vista Ultimate and Windows XP host operating systems and a variety of guest operating systems. Although I have not set up a development environment for working on VirtualBox, I believe the problem can be traced to /trunk/src/VBox/Devices/PC/BIOS/rombios.c in the lines between 5392 and 5404 as it can be found in revision [13190]. I believe these lines are causing the checks for isBusy() (/trunk/src/VBox/Main/HardDiskImpl.cpp) to fail.
|
|||||||||||||||||||||||

