Bug 171533

Summary:	"rcnetwork restart" makes networking in domain0 unusable
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Reinhard Max <max>
Component:	Xen	Assignee:	Kirk Allan <kallan>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	suse-beta
Version:	RC 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Reinhard Max 2006-05-02 12:29:18 UTC

I didn't find a way to restart the network in domain0 without screwing it complely to the point that only a reboot helped getting it back.

It seems that the scripts that take care of the networking stuff for Xen aren't integrated with the normal networking scripts, so that the Xen stuff isn't rolled back before the normal networking is shut down and applied again when it comes back up.

Comment 1 Lynn Bendixsen 2006-05-02 15:33:59 UTC

I think this is true for all "bridged" networking schemes and not just xen. We probably just need to find some bridging doc and post it sopmewhere so that users become more familiar with it.  Is this true Kirk?

Comment 2 Kirk Allan 2006-05-02 15:50:27 UTC

Currently in Xen using bridge mode, if you want to reconfigure the network interface that is used in conjunction with the bridge, you must undo the bridging setup first.  To undo the bridging the network-bridge script is used as follows

/etc/xen/scripts/network-bridge stop netdev=<ethX>

where ethX is the interface used with the bridge e.g. eth0.  You can then configure or restart the network as needed.  To start the bridging again enter

/etc/xen/scripts/network-bridge start netdev=<ethX>

Comment 3 Kirk Allan 2006-05-02 15:52:07 UTC


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

Comment 4 Reinhard Max 2006-05-02 16:05:03 UTC

Kirk, I think what you've written in Comment #2 should be part of /usr/share/doc/packages/xen/README.SuSE . It currently only explains what is being done for the bridge setup, but it doesn't explain that this interfers with the regular network scripts and how it can be undone and redone if needed without rebooting the machine.

Or is that already documented elsewhere and I just haven't found it yet?