9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Douglas Guptill <dguptill@accesswave.ca>
To: 9front@9front.org
Cc: moody@posixcafe.org
Subject: Re: [9front] qemu clock/timer issue
Date: Tue, 16 Apr 2024 14:07:01 -0300	[thread overview]
Message-ID: <Zh6wNS8rY8e+a9KQ@blackscram> (raw)
In-Reply-To: <9f91383e-c9f5-4cfa-8065-494cfffdebc1@posixcafe.org>

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

Hello moody:

On Tue, Apr 16, 2024 at 08:32:42AM -0500, Jacob Moody wrote:

> 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.

Ahhh.. That is a big help.  

> If you do not feel comfortable debugging

I'm a programmer. :)

I can look at the code, build and insert write statements, in qemu and
the kvm module of linux.  Cannot yet do anything like that with
9front.

> but would still be interested in helping

For sure.

> 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,

Assuming that you mean a nightly iso of 9front, I just did that with
9front-10501.amd64.iso.gz.  No noticable change; but then I don't yet
understand 9front.  I stopped it quickly.  Attached is a jpg of what I
saw.

> then move back through the releases going back.

Sorry, I don't understand.  Releases of...qemu?  9front?

There is a newer qemu (9.0.0-rc3) out; I will make a build of that,
and then start looking at its code, and the kvm module code, to see if
I can find, and maybe understand, the offending code.

Thank you for the reply,
Douglas.
-- 
Bold character derived from stubborn patience and adversity.
==
Douglas Guptill, B.Sc., CCP, M.Comp.Sci., THB

[-- Attachment #2: 9front-10501.amd64.iso_boot-screen.jpg --]
[-- Type: image/jpeg, Size: 118357 bytes --]

  reply	other threads:[~2024-04-16 17:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05  2:04 Michael Forney
2022-02-05 17:04 ` hiro
2022-02-05 18:14 ` Nick Owens
2022-02-18  3:25   ` Michael Forney
2022-02-21 22:35     ` cinap_lenrek
2024-04-16  5:40       ` Douglas Guptill
2024-04-16 13:32         ` Jacob Moody
2024-04-16 17:07           ` Douglas Guptill [this message]
2024-04-16 17:34             ` Jacob Moody
2024-04-16 18:46           ` Michael Forney
2024-04-16 18:56             ` Jacob Moody

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zh6wNS8rY8e+a9KQ@blackscram \
    --to=dguptill@accesswave.ca \
    --cc=9front@9front.org \
    --cc=moody@posixcafe.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).