Bug 1033171

Summary: RFE: Allow MTU to be specified
Product: [Community] Virtualization Tools Reporter: David Woodhouse <dwmw2>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, clalancette, crobinso, itamar, jforbes, laine, libvirt-maint, rbalakri, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-19 20:30:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Woodhouse 2013-11-21 16:15:39 UTC 
I use libvirt to run a Windows virtual machine, which is unfortunately required for certain services that my company provides (and requires that I use).

I am connected to the company via a VPN, with an MTU of 1266.

There are pMTU black holes in our network, and HR are quite insistent that I am not permitted to visit the office location of those responsible, and apply percussive education until the problem is fixed.

Thus, I must work around it at my end. My options include MSS clamping on the NAT, or asking dnsmasq to advertise the smaller MTU in its DHCP responses. Both of those would need to be set up by libvirt.

If there is an existing facility in the network configuration where I can add verbatim options to the dnsmasq config such as 'dhcp-option=virbr0,26,1266', that would probably suffice...
Comment 1 Cole Robinson 2016-04-19 20:30:30 UTC 
Duping to another bug which has discussions about more generalized dnsmasq option passthrough

*** This bug has been marked as a duplicate of bug 666556 ***