rcxend status breaks network setup on SLES10SP2 VM on Hyper-V

This document (7002902) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 10 Service Pack 2
Microsoft 2008 Server with Hyper-V

Situation

Running 'rcxend status' on SLES10SP2 as guest VM on Microsoft Server 2008 with Hyper-V causes the first ethernet device to get renamed and lose network connectivity. /var/log/messages show entries like the following:

Apr  2 11:11:09 sles10sp-w2k8 kernel: Bridge firewalling registered
Apr  2 11:12:06 sles10sp-w2k8 ifup:     tmpbridge 
Apr  2 11:12:06 sles10sp-w2k8 ifup:               No configuration found for tmpbridge
Apr  2 11:12:06 sles10sp-w2k8 ifdown:     seth0     
Apr  2 11:12:06 sles10sp-w2k8 ifdown:     seth0     configuration: eth-id-00:15:5d:42:09:02
Apr  2 11:12:07 sles10sp-w2k8 kernel: seth0 renamed to pseth0
Apr  2 11:12:07 sles10sp-w2k8 kernel: tmpbridge renamed to seth0
Apr  2 11:12:07 sles10sp-w2k8 kernel: device pseth0 entered promiscuous mode
Apr  2 11:12:07 sles10sp-w2k8 ifup:     seth0     
Apr  2 11:12:07 sles10sp-w2k8 ifup:               No configuration found for seth0
Apr  2 11:12:17 sles10sp-w2k8 kernel: pseth0: no IPv6 routers present

Resolution

An update addressing this issue has been released. Please use the online update to patch the related packages to at least version 3.2.0_16718_24-0.4 of XEN.

Additional Information

The 'rcxend status' command is triggered by e.g. 'yast2 runlevel' or 'supportconfig' command.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.