...

...

On 12/29/2008 at 11:56 PM, in message , PGNet wrote: Hi Jason, As a 1st step, I'd best clearly understand what's changed. Can you perhaps point to whatever documents that fact, &/or details the changes & preferred method? I certainly haven;t found it yet :-/

I don't know if any official documentation exists yet. There was a bug opened to get documentation created for this, but it is still open. However, there is some explanation in the bug: https://bugzilla.novell.com/show_bug.cgi?id=432709

So only via the yast gui (curses based, I'd gather, as I'm on a text-only, headless install ...) ?

That's correct. It works the same with or without the GUI.

Ideally, I'd like to understand the "new, right way" to configure multiple bridges using some sort of gui-less script ... even if it requires some customization.

To understand the reasons for the change, you need to understand a little about how the xen network-bridge script works. When that script is being used, openSUSE boots up and configures the networking in its usual way. Then, xend comes along and calls the network-bridge script which proceeds to examine the network configuration, rip it out, and set it up again using a bridge. With this method, the distributions networking scripts know nothing about the changes that network-bridge made as those changes were made outside of the distros networking framework. This results in numerous potential problems such as a complete breakdown when restarting the network ("rcnetwork restart"), for example. Therefore, beginning with openSUSE 11.1 and SLES 11, the xen networking scripts are disabled by default, and functionality has been added to yast to handle bridged network configurations. This way the networking is setup correctly the first time (no rip and replace after boot time) and functionality such as restarting the network works as expected. There is no need for any sort of special script because you configure the networking once, just like you normally would when installing openSUSE without XEN. The difference is that you either a) accept the default bridged networking proposal, or b) make customizations that more closely mirror your needs. In your case, where you already have a non-bridge network configuration, you might want to try running the "Install Hypervisor and Tools" yast module. This will setup the default bridged networking configuration and you could use it as a reference for how things should look. Sorry I don't know of any place that this is documented. Let me know if you have any other questions. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org