From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] problems with dual ethernet networking
Date: Tue, 2 Nov 2004 21:45:31 -0500 [thread overview]
Message-ID: <20041103024531.GA19904@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <20041102184443.GB18735@circolab.net>
On Tue, Nov 02, 2004 at 07:44:43PM +0100, marco ghidinelli wrote:
> i'm unable to get a running configuration with a dual ethernet card with
> qemu and vdeq.
>
> i try with this commands:
>
> vde_switch -daemon -sock /tmp/vde1.ctl
> chmod 777 /tmp/vde1.ctl
> vde_switch -daemon -sock /tmp/vde2.ctl
> chmod 777 /tmp/vde2.ctl
>
> vdeq qemu -sock /tmp/vde1.ctl,/tmp/vde2.ctl -nics 2 -hda vivian.img
>
> and i got this message:
>
> qemu: invalid fd for network interface 0
>
> running:
>
> vdeq echo -sock /tmp/vde1.ctl,/tmp/vde2.ctl -nics 2 -hda vivian.img
>
> i got:
>
> -tun-fd 3,5 -nics 2 -hda images/vivian.img
>
> and looking in vl.c seems that qemu doesn't like very much the option
> -tun-fd 3,5
>
> is this option implemented? where i am wrong?
No it is not implemented. vdeq is meant for only one sock at a time.
You may be able to get qemu to work by using -tun-fd 3 -tun-fd 5 tho (not sure),
but vdeq won't support that unless you change it.
> let me know.
>
> bye!
>
> --
> BOFH excuse #10:
>
> hardware stress fractures
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2004-11-03 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 18:44 [Qemu-devel] problems with dual ethernet networking marco ghidinelli
2004-11-03 2:45 ` Jim C. Brown [this message]
2004-11-03 9:35 ` Renzo Davoli
2004-11-03 12:40 ` [Qemu-devel] [patch] " Renzo Davoli
2004-11-03 13:48 ` marco ghidinelli
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=20041103024531.GA19904@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.