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

[Xen-users] xen on openSUSE

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen on openSUSE
From: Németh Tamás <nice@xxxxxxxxxxxxxxx>
Date: Tue, 16 Sep 2008 19:10:06 +0200
Delivery-date: Tue, 21 Oct 2008 09:22:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Organization: Nyugat-Magyarországi Egyetem
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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

<Prev in Thread] Current Thread [Next in Thread>