It turns out the vxlan offloading does get enabled. One host did not show it getting enabled in the syslog. But when I went to try a test on the 2nd compute host which I had not checked, I could see expecting log message about offloading getting enabled:
Nov 23 20:19:59 maero kernel: [18302.839361] be2net 0000:08:00.1: Only one UDP port supported for VxLAN offloads
Nov 23 20:19:59 maero kernel: [18302.839367] be2net 0000:08:00.1: Disabling VxLAN offloads
But I am still a bit confused about the MTU size change. I now see that the MTU size for GRE was done specifically to address the possibility of fragmentation and AFAICT the document states that instance-mtu ought to be less than network-device-mtu. Also, I would expect a small difference between the GRE and VXLAN headers... so need to dig into this further.
It turns out the vxlan offloading does get enabled. One host did not show it getting enabled in the syslog. But when I went to try a test on the 2nd compute host which I had not checked, I could see expecting log message about offloading getting enabled:
Nov 23 20:19:59 maero kernel: [18302.839361] be2net 0000:08:00.1: Only one UDP port supported for VxLAN offloads
Nov 23 20:19:59 maero kernel: [18302.839367] be2net 0000:08:00.1: Disabling VxLAN offloads
https:/ /pastebin. canonical. com/144654/
But I am still a bit confused about the MTU size change. I now see that the MTU size for GRE was done specifically to address the possibility of fragmentation and AFAICT the document states that instance-mtu ought to be less than network-device-mtu. Also, I would expect a small difference between the GRE and VXLAN headers... so need to dig into this further.