9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Deepak Chawla <dchawla@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] VMware and 9atom
Date: Wed,  9 Oct 2013 14:02:32 -0700	[thread overview]
Message-ID: <CAPCGcM_kQKBZe0h2XikRma+KZ+CcJdHiYJHKuFScCOTtgorYQA@mail.gmail.com> (raw)
In-Reply-To: <CAD_JZaqb6N8PNYv9tv2WKp4pXLhFx=N-_qmctBdk9YnZbrSKqw@mail.gmail.com>

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

In the past, I've had problems installing 9atom/plan9 on the latest version
of VirtualBox, but I could install it on a VM from an older (4.1.24?) rev
of VirtualBox. I have since updated to the latest VirtualBox and my VMs
have continued to work. I haven't tried an install on a new VM since I
updated.


On Wed, Oct 9, 2013 at 1:34 PM, Terry Wendt <silicon.penguin67@gmail.com>wrote:

> I read in the  plan9 google groups archive that plan9-20120703.iso was
> known to work with vbox... I thought at the time I had the right version of
> vbox, but the minor version number may have been different.  I also wasn't
> aware that qemu could work with out the support from the proc.  Is that
> version dependent also, or only on a Microsquish OS version of qemu?
>
> Cheers,
> Terry.
>
>
>
> On Wed, Oct 9, 2013 at 3:13 PM, erik quanstrom <quanstro@labs.coraid.com>wrote:
>
>> > 9front works in virtualbox.
>>
>> i don't think it's that simple.  9atom runs in at least one install of
>> vbox, but i have also seen it fail.  the reports on the list have been
>> that
>> it takes a little magic, and the right vbox version.
>>
>> - erik
>
>
>

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

  reply	other threads:[~2013-10-09 21:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 19:33 Christopher Nielsen
2013-10-06 19:49 ` Matthew Veety
2013-10-06 19:56   ` Christopher Nielsen
2013-10-06 20:21     ` Jacob Todd
2013-10-06 20:35       ` Christopher Nielsen
2013-10-06 20:42         ` Jacob Todd
2013-10-06 20:44         ` cinap_lenrek
2013-10-06 20:32   ` erik quanstrom
2013-10-06 20:48     ` Christopher Nielsen
2013-10-06 21:02       ` erik quanstrom
2013-10-06 21:02       ` erik quanstrom
2013-10-06 21:08         ` Christopher Nielsen
2013-10-06 21:10           ` Jacob Todd
2013-10-06 21:14             ` erik quanstrom
2013-10-06 21:15             ` Christopher Nielsen
2013-10-07  4:43             ` Jens Staal
2013-10-09 19:52               ` Terry Wendt
2013-10-09 20:08                 ` Matthew Veety
2013-10-09 20:10                   ` Shane Morris
2013-10-09 20:13                   ` erik quanstrom
2013-10-09 20:25                     ` Matthew Veety
2013-10-09 20:34                     ` Terry Wendt
2013-10-09 21:02                       ` Deepak Chawla [this message]
2013-10-09 22:15                         ` Bakul Shah
2013-10-09 23:07                           ` Terry Wendt
2013-10-09 23:19                             ` Kurt H Maier
2013-10-10 15:08                             ` David du Colombier
2013-10-10 15:54                               ` Richard Miller
2013-10-10 16:03                                 ` Aram Hăvărneanu
2013-10-10 16:16                                   ` Bakul Shah
2013-10-10 20:05                                   ` Steffen Daode Nurpmeso
2013-10-09 22:19                         ` Christopher Nielsen
2013-10-09 22:51                           ` erik quanstrom
2013-10-10  0:02                       ` blstuart
2013-10-06 21:13           ` Aram Hăvărneanu
2013-10-06 21:20             ` Christopher Nielsen
2013-10-06 21:43       ` erik quanstrom

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=CAPCGcM_kQKBZe0h2XikRma+KZ+CcJdHiYJHKuFScCOTtgorYQA@mail.gmail.com \
    --to=dchawla@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).