From: Stanley Lieber <stanley.lieber@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] recent plan9.iso on hosted kvm/qemu
Date: Mon, 7 Mar 2011 23:37:45 -0600 [thread overview]
Message-ID: <AANLkTinjSCvCEdwoy17eJKza=X_6qTQ3i7exTdSi4gXJ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinY2etaZSbFtEjmeZ8C3dFpXN1mL5u-ZQKB6fCC@mail.gmail.com>
I'm installed.
Made a custom boot floppy with the plan9.ini from plan9.iso's
boot.img. In addition,
one of either *noe820scan=1 or *norealmode=1 were required to avoid
the freeze-up
mentioned throughout this thread. The floppy's boot menu points to
kernels on the
plan9.iso that is configured as the IDE secondary master.
Taking another cue from Jack's experiences, I asked for the NIC to be
configured as
a RTL8139. With either option (*noe820scan or *norealmode), my installed system
can't pass icmp or tcp traffic to hosts on the local network.
Networking is configured
as normal (in fact, the configuration is identical to the Plan9 in
qemu I had working on
this same hardware under KVM/qemu -> OpenBSD -> kqemu/qemu -> Plan 9). After
booting, the contents of /net/iproute, ip/ndb, etc., seem correct and
are consistent with
my other, working, Plan 9 systems.
The new system can ping it's own IP address, but cannot be pinged from
the local network.
I suspect there may be some sort of arp confusion in the ethernet
switch. This system
was previously configured with the same IP address, bridged from
kqemu/qemu to the
kqemu/qemu host's external interface (which itself was a virtual
interface hosted on
KVM/qemu). With this new configuration, the MAC address has changed.
I've submitted
a support request to check it out.
-sl
next prev parent reply other threads:[~2011-03-08 5:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10045_2495_16663b8cca278b776372dbc44b36387b57580924_6@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_5@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_4@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_3@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_2@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_7@arpnetwork>
2011-03-02 10:12 ` Stanley Lieber
2011-03-01 19:49 ` a z
2011-03-02 14:53 ` Stanley Lieber
2011-03-03 15:20 ` Stanley Lieber
2011-03-06 6:45 ` Jack
2011-03-06 14:09 ` erik quanstrom
2011-03-06 16:00 ` Jack
2011-03-06 17:15 ` erik quanstrom
2011-03-06 19:36 ` Stanley Lieber
2011-03-06 19:41 ` erik quanstrom
2011-03-06 20:42 ` Stanley Lieber
2011-03-07 3:32 ` Stanley Lieber
2011-03-07 3:45 ` erik quanstrom
2011-03-07 4:04 ` Stanley Lieber
2011-03-07 15:11 ` Jack Norton
2011-03-07 16:24 ` erik quanstrom
2011-03-07 17:04 ` Stanley Lieber
2011-03-07 17:11 ` erik quanstrom
2011-03-07 23:27 ` Federico G. Benavento
2011-03-08 5:37 ` Stanley Lieber [this message]
2011-03-08 14:40 ` Jack Norton
2011-03-09 9:41 ` Stanley Lieber
2011-03-07 18:06 ` Jack Norton
2011-03-01 20:13 erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2011-02-24 13:40 Stanley Lieber
2011-02-24 19:57 ` Eric Van Hensbergen
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='AANLkTinjSCvCEdwoy17eJKza=X_6qTQ3i7exTdSi4gXJ@mail.gmail.com' \
--to=stanley.lieber@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).