I have decided to migrate my latest KVM server to CentOS 6.0 and am beginning to get a little frustrated with some issues that worked perfectly in 5.6. Right now I've given up on getting virbr0 and NAT to work, but now I need networking bridging to work, but nothing seems to fix the issue. I have not had much experience with troubleshooting KVM so could really use some pointers on resolving this issue. I have successfully bridged one of the server's NICs to br0, and I can ping the IP remotely that is assigned to br0, but none of the VMs that worked in 5.6's KVM are able to access the network. Please let me know what information would be useful to troubleshoot this. Here's what I have so far... ifcfg-eth3... --------------------------------- DEVICE="eth3" HWADDR="00:1B:21:A1:CF:76" ONBOOT="yes" BRIDGE=br0 ifcfg-br0 -------------------------------- DEVICE=br0 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=.... BROADCAST=.... NETMASK=.... NETWORK=.... # brctl show bridge name bridge id STP enabled interfaces br0 8000.001b21a1cf76 no eth3 sysctl.conf has these 3 additional lines... net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 net.bridge.bridge-nf-call-arptables = 0 Again I can ping br0's IP remotely , but no VMs assigned to it can access even that network's gateway. I have disabled iptables and ip6tables for now while trying to get this to work. The VMs , worked just fine in 5.6 and I have done nothing different but import them with virsh. Thanks - Trey -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20110715/f2360936/attachment-0006.html>
No experience with 6 here, but do your virsh-imported libvirt VM configs show <devices>...<interface type=bridge>...<source bridge='br0'/> ? i.e. the bridge there matches the bridge name you're created with ifcfg scripts? Eric
On Fri, Jul 15, 2011 at 2:07 PM, Trey Dockendorf <treydock at gmail.com> wrote:> I have decided to migrate my latest KVM server to CentOS 6.0 and am > beginning to get a little frustrated with some issues that worked perfectly > in 5.6.(snip)> Here's what I have so far... > ifcfg-eth3... > --------------------------------- > DEVICE="eth3" > HWADDR="00:1B:21:A1:CF:76" > ONBOOT="yes" > BRIDGE=br0 > ifcfg-br0 > -------------------------------- > DEVICE=br0 > TYPE=Bridge > BOOTPROTO=static > ONBOOT=yes > IPADDR=.... > BROADCAST=.... > NETMASK=.... > NETWORK=....I do not see GATEWAY=.... in your ifcfg-br0. Do you actually have it?> Again I can ping br0's IP remotely , but no VMs assigned to it can access > even that network's gateway.Akemi
On 7/16/11, Trey Dockendorf <treydock at gmail.com> wrote:> I have successfully bridged one of the server's NICs to br0, and I can ping > the IP remotely that is assigned to br0, but none of the VMs that worked in > 5.6's KVM are able to access the network. Please let me know what > information would be useful to troubleshoot this.Could you try creating a new VM using the GUI tool, then check if the networking works from it? I was having problems with KVM and part of the troubleshooting process got me to try it on SL6, which finally led me to discover that the command line tool generated XML doesn't work as well as the GUI tool for some reason. So there's the possibility that it could be that the definitions created through virsh in 5.6 has the same issues in CentOS 6.