From: Bill Davidsen <davidsen@tmr.com>
To: Stuart Jansen <sjansen@gurulabs.com>
Cc: kvm@vger.kernel.org
Subject: Re: Simple way of putting a VM on a LAN
Date: Sat, 26 Jul 2008 13:26:16 -0400 [thread overview]
Message-ID: <488B5E38.8010802@tmr.com> (raw)
In-Reply-To: <1217025085.7587.2.camel@simplicity.buscaluz.org>
Stuart Jansen wrote:
> On Fri, 2008-07-25 at 12:44 -0400, Bill Davidsen wrote:
>> But when the host is really on the network, it uses DHCP to set the IP,
>> while in a VM it never sends any DHCP packets, the setting of the IP
>> times out, and I wind up with no IP until I set it. I have checked with
>> tcpdump, the DHCP requests for IP appear on the bridge, but not on the
>> eth0 NIC, and so are never seen by the DHCP server.
>>
>> Do you see this problem, or have any information about it? Obviously
>> suggestions on fixing this are needed, since the dhcp server is a
>> candidate for virtualization in the future.
>
> Just to be certain of the obvious, you added eth0 to the bridge, right?
>
> brctl addif br0 eth0
Yes, everything works except the DHCP discovery. Once I bring up the VM
NIC by hand and set the default route everything works really well with
TCP, UDP, and ICMP, as well as the usual ARP packets, etc.
>
> And the tap device is active, right?
>
> ifconfig tap0 up
UP and based on something I saw in another script is tried adding
promiscuous, which really didn't change anything.
>
> Assuming it isn't something so obvious, I'm suspecting spanning tree.
>
> brctl stp br0 off
It was never on (unless it was turned on by something more automated
than my fingers, but it's definitely off now, and make no difference.
For a test I modified the network setup to a static IP and routing. That
did work, although it is undesirable, since it invites having the DNS
wrong. I moved to DHCP to be sure that the IPs are always right, a
master list gets turned into entries in both dhchd.conf and the
appropriate DNS files (forward and reverse lookeps are always right,
too). Shot myself in that foot way back in ARPAnet days :-(
Thanks for the ideas, I have one more, but I have to do a little
research before I can ask an intelligent question.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-07-26 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 1:54 Simple way of putting a VM on a LAN Bill Davidsen
2008-06-27 4:46 ` Mike Snitzer
2008-06-27 7:04 ` Chris Lalancette
2008-07-09 16:28 ` Bill Davidsen
2008-07-09 17:23 ` Javier Guerra
2008-07-24 4:15 ` Bill Davidsen
2008-07-24 14:22 ` Javier Guerra
2008-07-25 16:44 ` Bill Davidsen
2008-07-25 22:31 ` Stuart Jansen
2008-07-26 17:26 ` Bill Davidsen [this message]
2008-06-27 22:44 ` Freddie Cash
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=488B5E38.8010802@tmr.com \
--to=davidsen@tmr.com \
--cc=kvm@vger.kernel.org \
--cc=sjansen@gurulabs.com \
/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