From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] eepro100 multicast
Date: Wed, 29 Sep 2010 21:03:31 +0200 [thread overview]
Message-ID: <4CA38D83.9040106@mail.berlios.de> (raw)
In-Reply-To: <4C9E4952.3080108@lemonia.org>
Am 25.09.2010 21:11, schrieb Dunc:
> Hi all,
>
> I've been trying to set up some olives running inside qemu to practice
> for Juniper exam. I came across the multicast issue when enabling VRRP
>
> After lots of googling and reading forums, where people have being doing
> hacky patches, I found a page that suggests this has been fixed now,
> just not in a formal release
>
> (here for reference)
> http://www.internetworkpro.org/wiki/Using_QEMU_with_Olive_to_emulate_Juniper_Routers#Getting_and_Installing_QEMU
>
> I had a look through gitweb and can see there has indeed been a commit
> to fix multicast in eepro100 and so I've built a qemu based on latest
> git (as of yesterday). Unfortunately it doesn't seem to fix things for
> me, however I do have a different error now....
>
> eepro100: feature is missing in this emulation: Multiple IA bit
>
>
> The setup of this link is quite simple, I have 2 qemus running using tap
> mode for network, and I have bridged them together on my host (Linux)
> When I configure the network I can successfully ping across the link
> with no problems, but as soon as I enable VRRP on either end, I start to
> get the above error at regular intervals (I assume it's each time VRRP
> sends a multicast hello), and also my link stops pinging altogether.
> When I remove VRRP config, the link pings again.
>
> Does anyone know what's going on, or if I'm doing anything wrong?
>
> Thanks in advance,
>
> Dunc
The OS which was used here is based on FreeBSD.
I reviewed the latest sources of Linux, FreeBSD and NetBSD.
They all reset the multiple IA bit (multi_ia in BSD) to zero,
but I did not find code which sets this bit to one
(like it is done by Juniper routers).
Running Windows guests also does not set this bit.
Intel's Open Source Software Developer Manual does not
give much information on the semantics related to this bit,
so I had to guess how it works.
My patch could help Dunc, but if anybody has more information
or driver code which makes use of this bit, that would be
really helpful.
Regards
Stefan
next prev parent reply other threads:[~2010-09-29 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 19:11 [Qemu-devel] eepro100 multicast Dunc
2010-09-29 19:03 ` Stefan Weil [this message]
2010-09-29 19:59 ` [Qemu-devel] [PATCH] eepro100: Add support for multiple individual addresses (multiple IA) Stefan Weil
2010-09-29 20:30 ` Edgar E. Iglesias
2010-09-30 16:45 ` Stefan Weil
2010-09-30 17:04 ` Edgar E. Iglesias
2010-10-03 9:56 ` Michael S. Tsirkin
2010-10-03 10:11 ` Stefan Weil
2010-10-03 11:16 ` Michael S. Tsirkin
2010-10-03 11:47 ` Stefan Weil
2010-10-03 13:20 ` Michael S. Tsirkin
2010-10-04 12:57 ` Stefan Weil
2010-10-04 12:53 ` Michael S. Tsirkin
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=4CA38D83.9040106@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
/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).