From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id D48D323EDD for ; Tue, 16 Apr 2024 15:33:57 +0200 (CEST) Received: from mail.posixcafe.org ([45.76.19.58]) by 9front; Tue Apr 16 09:32:44 -0400 2024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posixcafe.org; s=20200506; t=1713274318; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SdLTR6zAHpqJY2vxKQsVTnz09pEA6tp7DQVNmznVZqk=; b=Gt+eQ2TuQhSg3pEAiaKp1p5bg5Hvi3Bz2agCfFFNStrGxR3mXfAuJuOy6XPNir7bfuTYtA 9T0Fe6FtjoiIlS7w68LBJR7G8HvRUSdb+EXLHgGGGYOQPQkY6e9kSburTQl7dNuKextYq4 4brEQLm/ZcgXyeV4Yb4XZlIJeJlaiSU= Received: from [192.168.168.200] ( [207.45.82.38]) by mail.posixcafe.org (OpenSMTPD) with ESMTPSA id bf4ea675 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for <9front@9front.org>; Tue, 16 Apr 2024 08:31:57 -0500 (CDT) Message-ID: <9f91383e-c9f5-4cfa-8065-494cfffdebc1@posixcafe.org> Date: Tue, 16 Apr 2024 08:32:42 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: 9front@9front.org References: Content-Language: en-US From: Jacob Moody In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: social lossless cache ACPI over WEB2.0 storage-based realtime-java control Subject: Re: [9front] qemu clock/timer issue Reply-To: 9front@9front.org Precedence: bulk It is understood that this bug only happens with intel kvm virtual machines. From all that has been tested it was currently understood to affect newer intel machines. It seems however that your machine is a bit older(10+ years) and still triggering this. I've certainly run 9front in kvm on intel machines before so it is likely either something that changed with us or something that has changed with QEMU. My money is on some QEMU change. If you do not feel comfortable debugging but would still be interested in helping perhaps you can help bisect 9front and qemu (one side at a time) to see if you can narrow down what has changed to get more information to fix these things. I would start with the nightly iso just to double check, then move back through the releases going back. Give that a go for a couple of them, then maybe try some older qemu. Thanks, moody