WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xen on openSUSE

To: Németh Tamás <nice@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] xen on openSUSE
From: Danilo Godec <danilo.godec@xxxxxxxxx>
Date: Wed, 22 Oct 2008 09:20:31 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Oct 2008 00:21:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1221585006.2183.19.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1221585006.2183.19.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.17 (X11/20080922)
Take a look at this -
http://www.novell.com/communities/node/5071/sles-10-sp2-networking-under-xen-troubleshooting-and-recommendations

Novell recommends a manual bridging setup using 'standard' SuSE scripts
and disable Xen 'network-bridge' scripts. The document describes SLES,
but I use the same approach on several OpenSuSE based Xen servers, some
of then featuring three network cards and VLAN's (that's where things
got complicated with Xen scripts).

OTOH I never had a problem with OpenSuSE and Xen scripts when only one
network card was used.

 Best regards, Danilo


Németh Tamás pravi:
> Dear developers!
>
> I've found that recent xen releases cannot be simly run on openSUSE! The
> script /etc/xen/scripts/xen-network-common.sh makes some incorrect
> assumptions on the SuSE ifup script. Bridged xen networking only works
> if the script executes this branch:
>
> preiftransfer()
> {
>   true
> }
>
> ifup()
> {
>   false
> }
>
> ifdown()
> {
>   false
> }
>
> Otherwise the xen networking scripts fail to put the main bridge (called
> eth0 on my servers) into the up state, because it thinks that it's
> already up, but it's down in fact! So, I think the mentioned script
> should choose the branch above, if it finds the file /etc/SuSE-release.
>
> Or something like that.
>
> Best regards:
>
> Tamas Nemeth
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>   


-- 
Danilo Godec, sistemska podpora

Predlog! Obiscite prenovljeno spletno stran http://www.agenda.si

ODPRTA KODA IN LINUX
STORITVE : POSLOVNE RESITVE : UPRAVLJANJE IT : INFRASTRUKTURA IT : 
IZOBRAZEVANJE : PROGRAMSKA OPREMA

Visit our updated web page at http://www.agenda.si

OPEN SOURCE AND LINUX
SERVICES : BUSINESS SOLUTIONS : IT MANAGEMENT : IT INFRASTRUCTURE : TRAINING : 
SOFTWARE 

Attachment: danilo_godec.vcf
Description: Vcard

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>