CentOS virt - Jan 2015 - Using network-script with Xen 4.4.1 (aka what will I do without xend?)

I have seen those documents, I did not see anything that indicates how
_automatic_ bridge configuration could be enabled with xl.

For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 ->
peth1).  If I have to configure this manually with ifcfg scripts I will,
but if an automatic method is provided or is possible with xl I'd prefer to
use that.

-Gene

On Thu, Jan 29, 2015 at 4:07 AM, Lars Kurth <lars.kurth.xen at gmail.com>
wrote:
> Gene,
> I think you should find the answers in
> * http://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt (bottom of
> page)
> * http://wiki.xenproject.org/wiki/Migration_Guide_To_Xen4.1%2B
> <http://wiki.xenproject.org/wiki/Migration_Guide_To_Xen4.1+>
> *
>
http://wiki.xenproject.org/wiki/Network_Configuration_Examples_%28Xen_4.1%2B%29
>
<http://wiki.xenproject.org/wiki/Network_Configuration_Examples_(Xen_4.1+)>
> * http://wiki.xenproject.org/wiki/XL_vs_Xend_Feature_Comparison may also
> be relevant
> If not, circle back to the list and I am sure someone else will be able to
> answer
> Regards
> Lars
>
> On 29 Jan 2015, at 08:39, Gene <gh5046 at gmail.com> wrote:
>
> I normally use the network-script parameter in the
> '/etc/xen/xend-config.sxp' configuration file to configure network
> bridges.  However, the latest release of Xen4CentOS (which comes with Xen
> 4.4.1) has xend disabled by default.
>
> Can I continue to use network-script without xend?  If not what is the
> recommended method for automatically configuring network bridges with the
> latest release of Xen4CentOS?
>
> I know I can just enable xend to continue using this script, but since Xen
> 4.5 is apparently dropping xend altogether I figure I should change my
> standard configuration starting now.
>
> Thanks in advance for your time.
>
> -Gene
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20150129/88d94a0c/attachment-0002.html>

On Thu, Jan 29, 2015 at 11:28 AM, Gene <gh5046 at gmail.com>
wrote:
> I have seen those documents, I did not see anything that indicates how
> _automatic_ bridge configuration could be enabled with xl.
>
> For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1
->
> peth1).  If I have to configure this manually with ifcfg scripts I will,
but
> if an automatic method is provided or is possible with xl I'd prefer to
use
> that.
Thanks Gene -- I'll add a note about the transition to network-scripts
in the CentOS "migrating to xl" document.

 -George

On Fri, Jan 30, 2015 at 4:39 PM, George Dunlap <dunlapg at umich.edu>
wrote:
> On Thu, Jan 29, 2015 at 11:28 AM, Gene <gh5046 at gmail.com> wrote:
>> I have seen those documents, I did not see anything that indicates how
>> _automatic_ bridge configuration could be enabled with xl.
>>
>> For my specific set up I have two bridges (xenbr0 -> peth0 &
xenbr1 ->
>> peth1).  If I have to configure this manually with ifcfg scripts I
will, but
>> if an automatic method is provided or is possible with xl I'd
prefer to use
>> that.
>
> Thanks Gene -- I'll add a note about the transition to network-scripts
> in the CentOS "migrating to xl" document.
And coming around again: if you need pair bonding and VLAN tagging,
the best guideline is probably my old one: for KVM at
https://wikis.uit.tufts.edu/confluence/display/TUSKpub/Configure+Pair+Bonding,+VLANs,+and+Bridges+for+KVM+Hypervisor

The more recent versions of NetworkManager for RHEL 7 and Fedora
apparently support VLAN tagging and pair bonding, but the interface is
poor. If you want it to be robust and reliable for virtualization
server, I'll urge you to set "NM_CONTROLLED=no" in
/etc/sysconfig/network, so it's inherited by default for all network
ports.

I'e some long rants about the unsuitability of NetworkManager for
servers we could expolore some time if you need it. But especially for
a virtualizaton server as opposed to a guest VM, It's dangerously
destabilizing