From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] network connection on virtualbox
Date: Thu, 3 Feb 2011 08:06:03 -0500 [thread overview]
Message-ID: <4f10ae56dbf8eede14099074459d9be7@brasstown.quanstro.net> (raw)
In-Reply-To: <df8af61a-8923-4145-aa53-1bd833810182@s11g2000yqh.googlegroups.co>
> > > Hi, Running plan 9 on virtual box 4.0.2, I've configured network
> > > adaptaters as below.
> > > Attached to NAT
> > > Adapter type: PCnet-FAST 3(Am79C973)
> > > check cable connected.
> >
> > > After booting plan 9, I typed ip/ipconfig, after waiting some time,
> > > ipconfig: no success with DHCP.
> > > I don't know what's wrong??
> > > Please help.
> >
> > virtualbox is finicky and what works depends a lot on the
> > version of vb and it seems to depend on your own hardware.
> >
> > the 79c973 driver doesn't track link state currently, so there's
> > limited ways i can think of to remotely help. did you happen
> > to see a message that looks like this on the console?
> >
> > print("#l%d: unknown PCnet card version 0x%.7ux\n",
> > ether->ctlrno, x&0xFFFFFFF);
> >
> > can you verify a /net/ether0 exists? if the answers are no and yes,
> > then it might be worth running snoopy in another window
> > to verify that you can see any packets.
> >
> > you might also try another emulated chipset.
> >
> > - erik
>
> I tried on Qemu, still same problem even though now ip/ipconfig and
> ndb/dns -r seems ok,
i don't understand the problem, then. i thought it was that ip/ipconfig
didn't work. what is it?
- erik
next prev parent reply other threads:[~2011-02-03 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3f60b9b0-81a6-419e-9bf9-b36d512c90d0@o39g2000prb.googlegroups.co>
2011-02-02 13:06 ` erik quanstrom
2011-02-02 13:53 ` Fernan Bolando
2011-02-03 9:58 ` Nyan Htoo Tin
[not found] ` <df8af61a-8923-4145-aa53-1bd833810182@s11g2000yqh.googlegroups.co>
2011-02-03 13:06 ` erik quanstrom [this message]
2011-02-02 10:01 Nyan Htoo Tin
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=4f10ae56dbf8eede14099074459d9be7@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).