Comment 1 for bug 1665798

Particularly, this issue causes the connectivity problem between two VMs on two different hosts when they are based on a VxLAN private network. In this case, the default MTU size of 1500 bytes is not working due to the overhead of VxLAN header size.

Here is an example of the problem.

VM A runs on host B and VM C runs on host D. Each VM has a VxLAN-based private network interface. VM A has its own floating IP as well.

From a laptop, a user logins to VM A via its floating IP. And then, when s/he logins from VM A to VM B using the private IP of VM B, it fails due to the VxLAN overhead when MTU is 1500 bytes.

Only after manually increasing the MTU size of the tap interfaces of VM A and VM B to a jumbo frame, it is possible to login from VM A to VM B via their private IPs.

I think this is a serious bug.