Hi,
On 26/05/19 16:48, Michael Fritscher wrote:
Good morning,
I've uploaded the perf file from VMWare for comparison under
https://mifritscher.de/austausch/openvpn/vmware/ . Additionally, I've
uploaded the dmesg output using VMWare and Qemu.
One interesting thing: It does not always happen, and if it doesn't
happen I can provoke it playing with the priority, CPU affinity etc of
the qemu process. So it seems to be really a timing problem which can
be provoked by scheduling issues on the host?
Best regards,
Michael Fritscher
Hello again,
I've uploaded a "good" case with qemu. In this good case, I've 2
additional lines in dmesg:
[ 0.028000] tsc: Fast TSC calibration failed
[ 4.544469] tsc: Refined TSC clocksource calibration: 2808.001
And the perf log show no hpet_read call at all!
Somehow it looks like a severe timer problem...
a google search on kvm+ tsc shows other people reporting the same type
of issue.
Try adding to the Linux boot flags
clocksource=kvmclock
and/or
notsc
to explicitly disable the TSC clocksource method.
HTH,
JJK
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
