Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #733416 +++
Xen drops the MTU of a guest's netfront interface to 1500 after migration.
For now I'm attaching the bug to kernel-xen, but I am still not really sure whether this is the right component.
Test info for QE:
- connect two machines with a crossover cable so that eth0 is the crossover cable and eth1 is the public network
- configure Xen so that you'll be able to migrate between the machines (shared storage, relocation server, etc.)
- configure the cross link on one machine like
# Intel Corporation 82574L Gigabit Network Connection
DEVICE=eth0
HWADDR=00:21:5E:6E:F0:29
ONBOOT=yes
HOTPLUG=no
IPADDR=169.254.100.200
NETMASK=255.255.0.0
NETWORK=169.254.0.0
MTU=9000
and similarly on the other machine
- on both machines, ensure the Xen bridge connects the right devices, for example by changing the network-script line in /etc/xen/xend-config.sxp to this:
(network-script 'network-bridge netdev=eth0 bridge=xenbr0')
- on both machines, ensure the Xen bridge has its MTU set to 9000, for example by adding this (huge hack) to /etc/init.d/xend at the end of function await_daemons_up
sleep 5
ip link set mtu 9000 dev vif0.1
ip link set mtu 9000 dev peth0
ip link set mtu 9000 dev xenbr0
- install a guest in one of the machines. ensure the guest has also a static IP configuration in the same subnet, and also has MTU=9000 in its /etc/sysconfig/network-scripts/ifcfg-eth0. Also, ensure that the guest is using xenbr0 and not virbr0.
- run ifconfig around "xm create"
ifconfig > before
xm create test1
# wait a few seconds
ifconfig | diff before -
The diff should show that the new vif interface has MTU=9000. Similarly, "ifconfig" in the guest should show MTU=9000.
- ensure that you can ping the guest from both hosts.
- migrate the guest from one host to the other. before migrating, run
ifconfig > before
on the guest and *destination* host and after migration run
ifconfig | diff before -
For both the guest and the destination host, the diff should show that the virtual network interface (vifN.0 on the host, eth0 on the guest) has MTU=9000.
- ensure that you can ping the guest from both hosts
--- Additional comment from pm-rhel on 2011-08-26 04:49:40 EDT ---
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
release.
Created attachment 520373[details]
forward port of the RHEL5 patch
Upstream did the same using the hw_features field (and ndo_fix_features/ndo_set_features; see commits fb50793 and later) that is not in RHEL6, so I'm instead forward porting the RHEL5 changes.
Comment 2RHEL Program Management
2011-08-29 14:10:39 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
> - on both machines, ensure the Xen bridge has its MTU set to 9000, for example
> by adding this (huge hack) to /etc/init.d/xend at the end of function
> await_daemons_up
>
> sleep 5
> ip link set mtu 9000 dev vif0.1
> ip link set mtu 9000 dev peth0
> ip link set mtu 9000 dev xenbr0
This is not necessary if you have the patch for bug 733417.
Verified with RHEL6.2-20111005.1 (kernel-2.6.32-206.el6, both 32 and 64 bit PV guests), host is kernel-xen-2.6.18-274.5.1.el5.x86_64 + xen-3.0.3-132.el5_7.1.x86_64 which has the fixes for bug 738389, bug 738608 and bug 738610.
Test setup as bug 738608 comment 6. After migrate guest from source to destination, the MTU of vif in guest can keep the value of 9000. Change bug to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2011-1530.html