Custom Query (16363 matches)
Results (745 - 747 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #35 | fixed | timing probleme with AMD X2 | ||
| Description |
There are timing problems on WinXP with a AMD X2 dual core runing ubuntu dapper. Only work-a-round: selecting only one core in the task manager for "VirtualBox.exe" look at: http://www.virtualbox.org/discussion/2/41 (de) |
|||
| #7814 | fixed | time remaining estimate for >55s & < 1min = 0 minutes => Fixed in SVN | ||
| Description |
Saving/Restoring a VM (1gb of ram for the VM) results in a progress estimate which goes: 1s...55s; 0min 0min 0min 0min 1min ... The code to handle this already has access to the variables it's going to use for presentation, so instead of doing fancy (and bad) math, it should just use them. Also, the use of QDateTime is really wasteful especially as it deals in time zone magic. |
|||
| #3135 | fixed | time inside guest fluctuates | ||
| Description |
Host:
Guest: 64bit
Time is running too fast inside the guest, and vboxadd-timesync keeps bringing it back. Below is a sequence of commands ran at ~1sec interval: # date Fri Jan 23 23:55:33 CET 2009 # date Fri Jan 23 23:55:35 CET 2009 # date Fri Jan 23 23:55:37 CET 2009 # date Fri Jan 23 23:55:34 CET 2009 # date Fri Jan 23 23:55:36 CET 2009 Guest: 32bit
Here the time flows correctly only if the guest OS is busy. If the guest is idle, time flows very slowly and the time sync daemon brings it forward a lot. Other remarks: Guest additions are installed and have the same version as the host virtualbox installation. CPU frequency scaling is disabled, all cores run at full speed. |
|||

