From: Steffen "Daode" Nurpmeso <sdaoden@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] VMware and 9atom
Date: Thu, 10 Oct 2013 22:05:31 +0200 [thread overview]
Message-ID: <20131010210531.Im1lyzSGRPApU56jY5BCnnqR@dietcurd.local> (raw)
In-Reply-To: <CAEAzY3_E7mu+J2hJNAWjOt5i0zFME72MYBKHtdFL5fE5UjFqnw@mail.gmail.com>
Richard Miller <9fans@hamnavoe.com> wrote:
|> If you want to run Plan 9 on VirtualBox, you have to use either
|> the 4.1 branch (for example 4.1.26) or 4.2.14 and later.
|
|I can confirm that standard Plan 9 runs on virtualbox 4.2.18 on MacOSX
|(tried it just now)
I have (had) no issue(s) with stock 9atom and 9front
(2941.ddc4d868272b) ISOs on VirtualBox 4.2.16, Mac OS
X SnowLeopard. (This is no "production use", though.)
Fool that i am i did not trust that it really should be "Intel
PRO/1000 MT Server (82545 EM)", but life would be too boring
without some desperation.
Aram Hăvărneanu <aram.h@mgk.ro> wrote:
|Why waste anyone's time instead of always denouncing VirtualBox...
When using qemu from MacPorts (v1.6.0), then
?0[steffen@sherwood src]$ plaw
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
steffen 73506 11.8 4.5 2990016 94728 s002 S+ 9:56pm 0:43.57 /opt/local/bin/qemu-system-i386 -hda VirtualBox VMs/9front/9front.qcow -boot d
steffen 73505 6.7 4.8 1113192 100228 ?? R 9:54pm 1:00.34 /Applications/VirtualBox.app/Contents/MacOS/../Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM --comment 9front --startvm 44dfa628-d2be-4391-8553-23436299f705 --no-startvm-errormsgbox
And i need to do
; aux/vga -m vga -l
(But it's rather due to faulty initial settings; however, it's
nonetheless fine in VirtualBox. I yet need to work on my qemu
setup. Don't mind.)
--steffen
next prev parent reply other threads:[~2013-10-10 20:05 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
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 [this message]
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=20131010210531.Im1lyzSGRPApU56jY5BCnnqR@dietcurd.local \
--to=sdaoden@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).