Re: [opensuse-virtual] OS 11.1 xen boot fails if xend-config.sxp configured to use non-default "(network-script )"
On 12/29/2008 at 11:56 PM, in message <dbd51810812292256t32d895fbwe1f9ea7677189b34@mail.gmail.com>, PGNet <pgnet.trash@gmail.com> 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
Hi Jason, On Tue, Dec 30, 2008 at 9:20 AM, Jason Douglas <jdouglas@novell.com> wrote:
I don't know if any official documentation exists yet.
Fair enough. Unfortunate when things have changed -- seemingly significantly -- at an actual release. Nonetheless ...
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
Thanks for the reference. Unfortunately, even though logged in to bugzilla, I get: You are not authorized to access bug #432709 I'm guessing it's tagged as 'internal only'?
That's correct. It works the same with or without the GUI.
Ok.
To understand the reasons for the change (snip)
... all clear ...
results in numerous potential problems such as a complete breakdown when restarting the network ("rcnetwork restart"),
yup. been there, done that :-)
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.
Aha. So it'll be 'in' SLES 11 as well. Important to know.
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.
This makes some sense -- though I'm unclear as to how separate networking setups for, e.g., xen- and non-xen- boot instances are handled.
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.
This seems the right first step ...
Sorry I don't know of any place that this is documented.
...eventually ...
Let me know if you have any other questions.
Will do as they arise. Thanks very much. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hi Jason,
Let me know if you have any other questions.
Prior to receiving your email replies, I'd dropped back to OS v11.0 so as to have a working 'multi-bridged' Xen setup ... Considering your instructions/advice, I did come across "11.1, Xen, Yast2 and Bridging Failed Setup" http://forums.opensuse.org/install-boot-login/402426-11-1-xen-yast2-bridging... Iiuc, the OP's doing specifically what we're talking about here/above ... and is having problems, subsequently dropping back to 11.0. Can you verify that this scenario -- under OS 11.1 -- has, in fact, been tested & demonstrated to work? If so, what's going on for the user in the post? Thanks. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On 12/31/2008 at 11:37 AM, in message <dbd51810812311037x33735e7eud79ddea67cd60249@mail.gmail.com>, PGNet <pgnet.trash+osvm@gmail.com> wrote: Considering your instructions/advice, I did come across
"11.1, Xen, Yast2 and Bridging Failed Setup"
http://forums.opensuse.org/install-boot-login/402426-11-1-xen-yast2-bridging... d-setup.html
Iiuc, the OP's doing specifically what we're talking about here/above ... and is having problems, subsequently dropping back to 11.0.
Can you verify that this scenario -- under OS 11.1 -- has, in fact, been tested & demonstrated to work? If so, what's going on for the user in the post?
The post-install automated bridge configuration has been tested in some fashion, but only on a limited scale and certainly not across all possible network configurations. I would not be shocked to learn that problems exist in that code as the majority of XEN testing was done on machines where the XEN pattern was selected at OS install time, which sets up a bridged network configuration right from the start. Since bridge setup is not difficult when using YaST, I'd recommend doing the setup manually and avoid the possibility of running into errors with the "Install Hypervisor and Tools" automated method. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hi Jason, On Wed, Dec 31, 2008 at 11:01 AM, Jason Douglas <jdouglas@novell.com> wrote:
Since bridge setup is not difficult when using YaST, I'd recommend doing the setup manually and avoid the possibility of running into errors with the "Install Hypervisor and Tools" automated method.
For stability reasons, I've dropped back to OS 11.0 + Xen 321. Still, having taken your advice to heart -- & for eventual compat with migration to OS 11.{X>1} -- I'm manually setting up my bridges etc via yast &/or direct edits in /etc/sysconfig/network/. So far, so goood -- all's working as expected. In this scenario, what should be done with the still-resident Xen scripts, so as not to attempt tear-down/re-build of bridges? In particular, should (at least) /etc/xen/xend-config.sxp be rm'd, or edited to comment out, #(network-script network-bridge) #(vif-script vif-bridge) ? Thanks. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On 1/6/2009 at 11:07 AM, in message <dbd51810901061007i329e6159n7ae1b149761e90c4@mail.gmail.com>, PGNet <pgnet.trash+osvm@gmail.com> wrote: Hi Jason,
On Wed, Dec 31, 2008 at 11:01 AM, Jason Douglas <jdouglas@novell.com> wrote: ... In this scenario, what should be done with the still-resident Xen scripts, so as not to attempt tear-down/re-build of bridges?
In particular, should (at least) /etc/xen/xend-config.sxp be rm'd, or edited to comment out,
#(network-script network-bridge) #(vif-script vif-bridge)
The vif-script line needs to remain in place (unchanged from default), and the network script line can simply have network-bridge removed: (network-script ) HTH, Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
participants (2)
-
Jason Douglas -
PGNet