it’s kinda hard to understand your network config from just an interfaces-file… some background about it comes in handy when other people want to understand what’s going on
Anyway, if you cant ping outside the IP block, maybe the gateway can’t be reached.
You specified a /27 with subnetmask 255.255.255.224, but you didnt add GATEWAY and NETWORK_ADDRESS, maybe those are outside your IP block ?
Can you reach the gateway from the VM ?
what do you want to achieve by bonding eth2+eth3 and then dividing them with subinterfaces, into bond0.528 and bond0.11 ? Your life would be a lot easier if you use eth2 for the 192.168.11.X IPs and then use eth3 for the bridge to the VM network. If that works ok, you can do the bonding afterwards. Then you know your opennebula virtual network is usable.
For the virtual network, you specify a 27, which makes you use a netmask of 255.255.255.224 and gives you 32 IPs.
If your defined gateway is outside that IP block, you cant reach it. Could you specify what you used in the X.X.X.X. for:
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: fast
Min links: 0
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 17
Partner Key: 5
Partner Mac Address: 00:18:b1:e4:d0:00
Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:24:81:a7:f4:67
Aggregator ID: 1
Slave queue ID: 0
Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:24:81:a7:f4:66
Aggregator ID: 2
Slave queue ID: 0
I think the problem is in the driver or virtual network configuration…