Custom Query (16363 matches)
Results (634 - 636 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2526 | fixed | Non-uniform internal timer in guest OS | ||
| Description |
Host machine: Core 2 Duo 6600, 2 GB RAM.
Partially the problem is mentioned in the forum threads: However, I could find some more details which may be of use for reproducing and fixing the problem. Problem description
The internal timer inside VM sometimes runs non-uniformly. It looks like following:
Lengths of the periods described can be different. Sometimes, it is slow for couple of minutes, then fast for 7-10 seconds; sometimes it's slow for several seconds, then fast for 0,5-1 second. Additional factorsI wanted to record a video with this behaviour. However, each time I run video recorder (I'm using UVScreenCamera), the problem became unreproducable. Finally, I noticed that UVScreenCamera's recording process performs something that forces VirtualBox's guest clock catch up the host clock. And the more frames per second I set in the recorder's options, the more smoothly runs VirtualBox. So, it seems that each additional redraw operation (or something like that) makes VB forcibly perform that "catch up" operation, which otherwise would be delayed for the future. |
|||
| #2548 | fixed | Saved state is discarded after VERR_NO_MEMORY | ||
| Description |
Host OS: WinXP SP3 Guest OS: any I tried to load a VM which was in saved state, but there was not enough memory on my host machine (many programs loaded), so I got VERR_NO_MEMORY. After that the saved state of this VM silently disappeared: in VB Manager it was shown in "Powered Off" state, and when I tried to open it again, it started loading from scratch, as if I discarded the saved state (which of course I did not). Log file of this VM is attached. |
|||
| #3658 | fixed | Host Interface networking hangs VB | ||
| Description |
Host OS: Vista Business 32-bit Guest OS: openSUSE 11.1 32-bit If I set Host Interface networking for the VM and start using this connection intensively, first guest OS hangs completely, and when I try to do anything with it via VirtualBox GUI (reset it, or close with saving state), the VB itself hangs too. The only thing I can do after that is to kill VB process. I already reported this bug for 2.2.0 beta 2, but the beta-test forum is killed, and the bug is still present in 2.2.0 final. :-( |
|||

