9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Peter Hull <peterhull90@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: How do I run plan9 in virtualbox?
Date: Thu, 17 Aug 2023 08:07:42 +0100	[thread overview]
Message-ID: <CAK9Gx1eq_6OHyorv7wjd+mAH-vXTLFBUn9Vbv9QoB4-G02zQVg@mail.gmail.com> (raw)
In-Reply-To: <CAL_X0tDF8PkfUh9_V3OehsrVJatrQxM-e9yDomZxQwcAT8KWfw@mail.gmail.com>

On Thu, 17 Aug 2023 at 03:18, Don Bailey <don.bailey@gmail.com> wrote:
> forgot to respond to this but fwiw, running plan9 on virtualbox seems to work peachy. Hiro what was the bug(s) you were running into before? I've never ran into an issue with it, but I've only used vbox on Linux; maybe it's a host/CPU issue?

My experience is that I ran 9front mostly successfully for a long
time, but sometimes versions of either 9front or VB would conflict.
Recently it stopped working for me:
I think the issue is that, due to the way it works (it's
virtualisation, not an emulator), some aspects of the host CPU 'leak
through' and that isn't always handled correctly. I had another issue
with valgrind and Fedora linux which was down to the same thing.
Someone once told me that QEMU always works, but last time I tried,
QEMU is not very nice to use on Windows.

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tce33a832621fe5a5-M97a03bb958eb078b1fa470f0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2023-08-17  7:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 18:06 [9fans] " yourlitlen1g
2023-08-02 19:07 ` hiro
2023-08-02 19:13 ` [9fans] " redhatuser
2023-08-02 19:23   ` Don A. Bailey
2023-08-02 20:49     ` Robert W. Baskette
2023-08-17  2:17       ` Don Bailey
2023-08-17  7:07         ` Peter Hull [this message]
2023-08-17 10:08           ` hiro
2023-08-17 10:13         ` hiro
2023-08-02 20:13   ` hiro

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:

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

  git send-email \
    --in-reply-to=CAK9Gx1eq_6OHyorv7wjd+mAH-vXTLFBUn9Vbv9QoB4-G02zQVg@mail.gmail.com \
    --to=peterhull90@gmail.com \
    --cc=9fans@9fans.net \


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