My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

XEN: reattaching network devices after the network bridge is restarted

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

Environment

Novell SUSE Linux Enterprise Server 10 Service Pack 1
Novell SUSE Linux Enterprise Server 10 Service Pack 2

Situation

After a restart of the networking subsystem or a restart of the Xen bridge, Xen DomU's are not able to access the network.

Resolution

This issue is commonly seen where the network bridge has been shutdown or the entire network subsystem has been restarted. It is not recommended to stop and the restart the network subsystem while DomU's are running. However in the event that this is done, the recover is pretty straight forward. Alternatively, you may elect to simply restart the DomU.

Each virtual NIC essentially also has a "virtual cable." The cable is attached to a network bridge in Dom0. When the bridge is stopped, the virtual cable is unplugged. In order to reattach the cable, the bridge and the end of the cable need to be identified.

The method of re-attaching the virtual NIC to the bridge device is the same regardless of whether or not the DomU is para-virtual or fully virtual.

  1. Identify the bridge that the DomU is supposed to be attached to.  Replace "DOMU" with the name or ID of the DomU in question.
    xm list -l DOMU | grep bridge
    Example output:
    (bridge eth0)
  2. Identify what virtual NIC (cable) the DomU is attached to:
    xm network-list DOMU
    Example output:
    Idx BE     MAC Addr.     handle state evt-ch tx-/rx-ring-ref BE-path
    0   0  00:16:3e:21:7d:2a    0     4      11    520  /521     /local/domain/0/backend/vif/34/0
    The bolded part of the output defines the VIF device. In this case it would be "vif32.0". To convert it simply remove the first slash and replace the last slash with a period.
  3. Attach the VIF device identified in step 2 to the bridge identified in step 1
    syntax: brctl addif BRIDGE VIF
    example: brctl addif br0 vif34.0

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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.

  • Document ID:7001931
  • Creation Date:18-NOV-08
  • Modified Date:27-APR-12
    • SUSESUSE Linux Enterprise Server
< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center