VMs cannot communicate with Compute Node. Cannot access Data network. [closed]

asked 2013-05-29 18:13:26 -0600

jamski gravatar image

updated 2013-05-31 15:11:19 -0600

I have a 3 Node set up:

  • 1 Controller
  • 1 Network
  • 1 Compute

This is on a flat network design with no DHCP. I used these instructions to configure my cloud.

With the exception of these instructions to make it a flat network:

I have installed 1 Windows 7 VM.

I had this cloud up and running with no problems until I tried to configure a second physical interface on my Windows VM. I blew up my compute box so I re-built it from scratch.

Now, I can build my VM and everything is up and running the same as before. But this time, I cannot ping anything from the VM, I cannot even ping the compute box. The compute box can reach the Data network, the Internet, and also the management network.

I believe its an issue with the communication between my VM and my Compute box over the br-int interface. When I checked my ova-vswitchd.log, I get this:

May 28 06:54:14|00079|vlog|INFO|opened log file /var/log/openvswitch/ovs-vswitchd.log
May 28 14:23:23|00001|vlog|INFO|opened log file /var/log/openvswitch/ovs-vswitchd.log
May 28 14:23:23|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
May 28 14:23:23|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
May 28 14:23:23|00004|bridge|INFO|created port br-eth0 on bridge br-eth0
May 28 14:23:23|00005|bridge|INFO|created port eth0 on bridge br-eth0
May 28 14:23:23|00006|bridge|INFO|created port qvobb86dcf6-8a on bridge br-int
May 28 14:23:23|00007|bridge|INFO|created port qvoc9f07b8e-25 on bridge br-int
May 28 14:23:23|00008|bridge|INFO|created port qvoa383b061-a9 on bridge br-int
May 28 14:23:23|00009|bridge|INFO|created port br-int on bridge br-int
May 28 14:23:23|00010|bridge|INFO|created port qvob7f885db-03 on bridge br-int
May 28 14:23:23|00011|ofproto|INFO|using datapath ID 0000002320ac9972
May 28 14:23:23|00012|ofproto|INFO|using datapath ID 0000002320f607fb
May 28 14:23:23|00013|bridge|WARN|could not open network device qvobb86dcf6-8a (No such device)
May 28 14:23:23|00014|bridge|WARN|qvobb86dcf6-8a port has no interfaces, dropping
May 28 14:23:23|00015|bridge|INFO|destroyed port qvobb86dcf6-8a on bridge br-int
May 28 14:23:23|00016|bridge|WARN|could not open network device qvoc9f07b8e-25 (No such device)
May 28 14:23:23|00017|bridge|WARN|qvoc9f07b8e-25 port has no interfaces, dropping
May 28 14:23:23|00018|bridge|INFO|destroyed port qvoc9f07b8e-25 on bridge br-int
May 28 14:23:23|00019|bridge|WARN|could not open network device qvoa383b061-a9 (No such device)
May 28 14:23:23|00020|bridge|WARN|qvoa383b061-a9 port has no interfaces, dropping
May 28 14:23:23|00021|bridge|INFO|destroyed port qvoa383b061-a9 on bridge br-int
May 28 14:23:23|00022|bridge|WARN|could not open network device qvob7f885db-03 (No such device)
May 28 14 ...
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by jamski
close date 2013-08-13 16:28:07.117144

1 answer

Sort by ยป oldest newest most voted

answered 2013-05-31 10:19:46 -0600

smaffulli gravatar image

I have just read today this great blog post about networking issues. It may not have the direct answer for your troubles but I hope it at least gives you some suggestions on how to dive deeper in it: The challenge of the network.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-05-29 18:13:26 -0600

Seen: 1,785 times

Last updated: May 31 '13