https://bugzilla.novell.com/show_bug.cgi?id=745603
https://bugzilla.novell.com/show_bug.cgi?id=745603#c2
Wolfgang Rosenauer
For fully virtualized guests, each one needs to point at a common NTP server in order to stay in sync. Para-virtualized guests get their time from dom0 unless someone has set /proc/sys/xen/independent_wallclock within the guest.
Sorry, I didn't mention that. I only use para-virtualized openSUSE guests and had independent_wallclock set to 0 (disabled / default). In exactly that setup the time was off around 7 minutes in every guest compared to the Dom0.
If the fully virtualized guests still have a problem even pointing at an NTP server, then trying the following may solve the problem.
I've setup NTP on every guest now because I needed a correct time. Does your following description only apply to full virtualization?
1. Edit the guests menu.lst file and on the kernel line add: notsc divider=10 Reboot the guest after making the change.
2. The openSUSE 11.4 dom0 uses Xen 4.0.x which has a new guest configuration file option called tsc_mode. This can be used on a per domain basis and allows for the following values. The non-default choices for tsc_mode are: - tsc_mode=1 (always emulate). All rdtsc instructions are emulated; - tsc_mode=2 (never emulate). This is the same as prior to Xen 4.0. - tsc_mode=3 (PVRDTSCP). High-TSC-frequency apps may be paravirtualized (modified) to obtain both correctness and highest performance. If tsc_mode is left unspecified (or set to tsc_mode=0), a hybrid algorithm is utilized to ensure correctness while providing the best performance possible.
Please report your results.
As written above I only have para-virtualized guests so should I try anything with the tsc_modes at all? -- 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.