9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Parallels Vesa driver question
Date: Tue,  4 Aug 2009 08:25:53 -0700	[thread overview]
Message-ID: <3e1162e60908040825p2e9ac95exbb777019b6c80a55@mail.gmail.com> (raw)
In-Reply-To: <20090804152009.A55295B76@mail.bitblocks.com>

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

On Tue, Aug 4, 2009 at 8:20 AM, Bakul Shah
<bakul+plan9@bitblocks.com<bakul%2Bplan9@bitblocks.com>
> wrote:

> On Tue, 04 Aug 2009 05:47:25 PDT David Leimbach <leimy2k@gmail.com>
>  wrote:
> >
> > On Tue, Aug 4, 2009 at 12:25 AM, Bakul Shah
> > <bakul+plan9@bitblocks.com <bakul%2Bplan9@bitblocks.com><
> bakul%2Bplan9@bitblocks.com <bakul%252Bplan9@bitblocks.com>>
> > > wrote:
> >
> > > On Mon, 03 Aug 2009 20:12:08 PDT David Leimbach <leimy2k@gmail.com>
> > >  wrote:
> > > > Wow....  Where's parallels 4.  I doubt I qualify for a free one.  And
> > > VMWare
> > > > Fusion really sucks with Plan 9 at the moment :-(
> > >
> > > qemu works well enough for me on FreeBSD & Linux but not on a
> > > Mac.  VirtualBox doesn't run plan9 but it runs FreeBSD, Linux
> > > and Windows fairly well so may be there is hope.  There is an
> > > open source version of VirtualBox that might be worth
> > > tinkering with.
> > >
> > > I was considering giving qemu a try on the mac. I believe there's a mac
> > centric front-end for it even.
>
> It's called Q. Don't bother.
>
> > In fact, how much of virtualbox is using qemu?
>
> I think vbox devices and recompiler are based on qemu but I
> don't really know.  IIRC early qemu did seem to have similar
> issues with plan9.
>
> Since other OSes run pretty well, my guess is something plan9
> depends on heavily has to be emulated (due to memory layout
> assumptions or something).
>

I've also tried Minix and QNX and both have problems on Virtual Box.  Which
other OSes did you try?  Linux and windows work but they're like necessary
to even claim you can do anything virtualization wise.

Dave

[-- Attachment #2: Type: text/html, Size: 2286 bytes --]

  reply	other threads:[~2009-08-04 15:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-02  9:36 Daniel Lyons
2009-08-02 17:06 ` erik quanstrom
2009-08-02 19:14   ` Daniel Lyons
2009-08-02 20:41     ` Steve Simon
2009-08-02 21:41     ` erik quanstrom
2009-08-03  6:57       ` Daniel Lyons
2009-08-03  9:26         ` Richard Miller
2009-08-03 11:20           ` erik quanstrom
2009-08-04  2:36             ` geoff
2009-08-04  3:12               ` David Leimbach
2009-08-04  7:18                 ` Daniel Lyons
2009-08-04  7:25                 ` Bakul Shah
2009-08-04 12:47                   ` David Leimbach
2009-08-04 15:20                     ` Bakul Shah
2009-08-04 15:25                       ` David Leimbach [this message]
2009-08-04 16:24                         ` Bakul Shah
2009-08-04 17:46                           ` erik quanstrom
2009-08-12  6:18                             ` Bakul Shah
2009-08-04  8:54             ` Daniel Lyons
2009-08-04  9:04               ` erik quanstrom
2009-08-03 16:30           ` ron minnich
2009-08-04  7:15             ` Daniel Lyons
2009-08-04 15:26               ` ron minnich
2009-08-03  9:13 ` Balwinder S Dheeman

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=3e1162e60908040825p2e9ac95exbb777019b6c80a55@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@9fans.net \
    /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).