linux-kernel - Re: KVM guest lockup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20081222105738.GA27409@squirrel.roonstrasse.net>
Date:	Mon, 22 Dec 2008 11:57:38 +0100
From:	Max Kellermann <max@...mpel.org>
To:	Jan Niehusmann <jan@...dor.com>
Cc:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: KVM guest lockup

On 2008/12/21 12:55, Jan Niehusmann <jan@...dor.com> wrote:
> As I observed such behaviour only when the host has frequency
> scaling activated: Could it be that in this case,
> clocksource_read(clock) on the guest is misbehaving?

Indeed, the host had governor=ondemand.  After the switch to
"performance", the guest seems to run stable.

So this is a bug in the guest kernel, by making wrong assumptions on
the clock values retrieved from the host, right?

Max
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/