...

...

On Mon, May 26, 2008 at 3:24 AM, in message <web-389767@speedy.tutby.com>, alex <alshu@tut.by> wrote: Hello List, Why last Xen package for OpenSUSE haven't network-multinet script from Ron Terry? What is the reasons that it was excluded and have OpenSUSE plans to use it in future?

There are several reasons why the network-multinet script is not included in the xen package: 1. A large number of problems were found that came as a result of fundamental networking changes in Xen. No longer is netloop used to setup veths (we used to link pethX to xenbrX to ethX in dom0). Instead, the physical interface is renamed to peth0 and the bridge is moved to eth0 and it is the bridge that has the mac/ip addresses, and that acts as the interface in dom0. All of the issues we found can be resolved, but they require manual configuration, and are not documented. Therefore, if you want to use network-multinet, you are making that decision consciously, and it is assumed that you can deal with whatever issues arise. 2. There were several aspects of network-multinet that worked differently than the maintainers of the openSUSE networking stack wanted them to. After approximately a dozen changes that did not align with the way that Ron Terry (and other network-multinet proponents) wanted things to work, it was determined that by removing the script from the distro, it would be free to evolve unencumbered. 3. The goal for openSUSE 11.1 (and SLES 11) is to remove all xen networking scripts, and instead to move all the configuration into the sysconfig framework as part of the distro's regular networking. Right now, if you boot into Xen, the SUSE networking scripts run, completely configuring the network, and then xend starts the xen networking scripts which completely tear down the SUSE networking and rebuild it completely without notifying the SUSE networking infrastructure. Not only does this seem ridiculous, but it also prevents fundamental networking commands (such as rcnetwork restart) from being run when Xen networking is configured. It is also evident that other virtualization solutions (such as KVM) could benefit from a centralized networking configuration.

Have current Xen's network scripts all functionality that offered 'network-multinet'?

Anything that is done with network-multinet can also be done by calling the existing xen networking scripts with the correct parameters, or through the sysconfig networking scripts. These methods are not as easy or intuitive as network-multinet, but it's possible. Also, you are always welcome to download and use network-multinet if it's a better fit for your setup. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org