https://bugzilla.novell.com/show_bug.cgi?id=399536
User roland.kletzing@materna.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=399536#c4
roland kletzing
Using the clock=pit solves the issue.
well known "tunable" ;) vmware timekeeping (or timekeeping in virtual machines in general) is a complex thing. neiter a suse issue nor a kernel issue, imho. see http://www.vmware.com/pdf/vmware_timekeeping.pdf excerpt: Option clock=pit is the simplest and most robust of the available algorithms. It uses only the PIT counter for interpolation. This option does not include lost tick correction code, so it does not gain time, but it does lose time when a tick is actually lost. This option is recommended for use in VMware virtual machines, together with VMware Tools time synchronization, to correct for the occasional lost ticks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.