Re: [9fans] Networking in VirtualBox (DNS problem?)

["Rubén Berenguel" <ruben@mostlymaths.net>]

Hi Ingo,

I had perused that thread already (almost all Google results, in
fact.) But your answer made me realise something: I wasn't using qemu
because I could not install a fresh Plan9 in a Qemu image from within
Qemu (I don't remember the problem now.) But now I can boot the qemu
image I have created with VirtualBox and I'm happy with Qemu :)

Now problem is that although the dns server is configured correctly
(dnsquery google.com ip returns a bunch of ips for google) ip/ping
answers with corrupted reply. But abaco browses correctly so... I
won't bother. Thanks!

Ruben

On Wed, Aug 7, 2013 at 3:48 PM,  <ikrabbe.ask@gmail.com> wrote:
> Hey Ruben,
>
> from my past times using VirtualBox I found this quote:
>
> “This one: It took me over a day of sweat, blood and tears to get the network running. Actually the PCNet adapters don't seem to work at all. I found just this one Network setting to be good:
> Adapter 1: Intel PRO/1000 MT Server (Bridged adapter, eth0)
> where the `MT Server' version is absolutely essential, as the MT Desktop version does not work!”
>
> from
>
> http://www.plan9.bell-labs.com/wiki/plan9/installing_plan_9_in_a_virtualbox/index.html
>
> I would recommend using qemu these days, though.
>
> Cheers,
>
> ingo
>
> ---------- Forwarded message ----------
> From: "Rubén Berenguel" <ruben@mostlymaths.net>
> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
> Cc:
> Date: Wed, 7 Aug 2013 15:39:00 +0200
> Subject: [9fans] Networking in VirtualBox (DNS problem?)
> Hi all,
>
> The newest version of VirtualBox (4.2.16) works with Plan9 (at last!)
> but I can't figure out how to set up networking (I had no trouble
> setting it up with qemu before.) For reference, I'm using VirtualBox
> (the version described) in a MacBook. I have tried bridget and NAT for
> all adapters, and the only instance I got something working was
>
> NAT,
> Intel PRO MT/1000 Desktop
>
> on bootup the card was detected, ip/ipconfig didn't complain with this
> setting (it complained with most bridged setups with Airport.)  cat
> /net/dnb gave me 127.0.0.1 as my IP (hmmm) but Google's DNS servers,
> which sounds okay. ndb/dns -r didn't complain either, but ip/ping
> google.com did: cs problem, dns problem. I thought it was just that
> the network didn't work, but ip/ping 212.106.221.227 (that's
> google.com) or ip/ping 88.221.15.26 (that's reddit.com) did work
> without any problems. So my best guess is that dns (or cs) are the
> culprits. dnsquery does nothing (complains about anything I get to
> ask) and the same goes for dnsdebug ("crapped" error messages for all
> queries.)
>
> Any setup hint?
>
> Ruben