On Jan 24, 2012, at 8:31 PM, Bruce Dubbs wrote:
> My problem with kvm is that I don't know what it is trying to do. I
> would think that creating a virtual machine (VM) would create a network
> connection on both the host and VM sides, say tap0 on the host and eth0
> on the client, and connect them. Then these should be connected like
> the iptables masquerade capability if on a different network or through
> normal switching if on the same network.
Conceptually, it might work like Xen. There, the VM creates an interface,
which gets enslaved to br0. In the output below, that would be the vif*
entries. There are no iptables entries in Xen's case, and there's no
masquerading, switching, or IP forwarding.
====
host [~] $ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.001b219eef8e no eth3
vif2.0
vif4.0
br1 8000.001b219eef8f no eth2
vif2.1
vif4.1
====
That is, I'm not certain that kvm is using bridging...But, if it is, I would
expect it to look something like (output simulated):
====
bruces-box # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00cafebabe11 no eth0
tap0
====
And, neither eth0 or tap0 would have configs; just br0 (which happens to have
an IP, the outward facing config that used to be applied to eth0, so the host
can have connectivity) and "eth0" inside your VM (or whatever interface kvm
gives to the VM), which seems like it would be configured "normally"...
Were you still having issues with external connectivity on your kvm/qemu box?
Q
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
