From: David Barrett <dbarrett@quinthar.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Two taps, same IP?
Date: Tue, 15 Jul 2008 19:11:11 -0700 [thread overview]
Message-ID: <487D58BF.1070805@quinthar.com> (raw)
In-Reply-To: <487D5287.1080707@codemonkey.ws>
Anthony Liguori wrote:
> David Barrett wrote:
>> I'm considering a tap-based alternative to the -redir patch I proposed
>> earlier, but I'm just not quite getting how it works. In particular,
>> I'm able to access the webserver on one image just fine, but not the
>> other: wget fails with "Connecting to 172.20.0.3:80... failed: No
>> route to host."
>>
>> Can you explain why and set me straight?
>>
>> sudo qemu -kernel-kqemu -net nic,vlan=0 -net tap,vlan=0 image0.raw
>> sudo qemu -kernel-kqemu -net nic,vlan=0 -net tap,vlan=0 image1.raw
>
> You need to pass a unique mac address for each guest. You're probably
> getting mac address collisions.
Hm, you're right, they had the same MAC address. Unfortunately fixing
that had no effect. Now I'm launching with:
sudo qemu -kernel-kqemu -net nic,vlan=0,macaddr=00:00:00:00:00:00 -net
tap,vlan=0 image0.raw
sudo qemu -kernel-kqemu -net nic,vlan=0,macaddr=00:00:00:00:00:11 -net
tap,vlan=0 image1.raw
I'm still able to wget image0, but so long as it's operational I can't
wget image1. Like before, shutting down image0 enables wget access to
image1.
Looking at ipconfig in the both guests show that the MAC address is
being picked up correctly, so it must be something else.
Any other ideas? Thanks!
-david
next prev parent reply other threads:[~2008-07-16 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 1:38 [Qemu-devel] Two taps, same IP? David Barrett
2008-07-16 1:44 ` Anthony Liguori
2008-07-16 2:11 ` David Barrett [this message]
2008-07-16 3:04 ` Erik de Castro Lopo
2008-07-16 13:51 ` Anthony Liguori
2008-07-16 3:05 ` Erik de Castro Lopo
2008-07-16 4:25 ` David Barrett
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=487D58BF.1070805@quinthar.com \
--to=dbarrett@quinthar.com \
--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).