When you showed the output of brctl show earlier only eth0 showed up. Does the VM NIC showed up attached to br0 when the VM is running?
If so, then you can ping the VM from your host? That wouldn't involve the university switches so it would be a good first step before digging into packet dumping arp traffic...
Sent from my mobile phone
On Fri, Jul 15, 2011 at 6:24 PM, Emmanuel Noobadmin <centos.admin@xxxxxxxxx>
Could you try creating a new VM using the GUI tool, then check if the
On 7/16/11, Trey Dockendorf <treydock@xxxxxxxxx
> 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.
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
I did try another VM (CentOS 6) via virt-manager with the same results. However I setup a test server at home, and am able to get both bridging and NAT to work so this may be an issue with the network on my server. It's a University network and their switches tend to play havoc with virtual servers even though I've been assured enough MAC addresses have been allowed on my port.
How does one troubleshoot or provide debug information on a correctly or incorrectly functioning network bridge? As I contact my University's helpdesk I'd like to be able to point out the fault is not with my KVM server.
CentOS-virt mailing list