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] newbie: suse 10.1b6 domU network problem

Subject: Re: [Xen-users] newbie: suse 10.1b6 domU network problem
From: "Stephan A. Rickauer" <stephan.rickauer@xxxxxxxxxxxxxxxx>
Date: Thu, 09 Mar 2006 10:55:48 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Mar 2006 12:58:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <440EC492.4070303@xxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: ETH/University ZH, Institute of Neuroinformatics
References: <440EC492.4070303@xxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (X11/20060111)
Stephan A. Rickauer wrote:
> playing with SuSE 10.1 beta 6 on a x86_64 system reveals no creation of
> a vif0.0 during the boot process. After the start of xend I only see the
> bridge xenbr0 along with eth0 (and apart from eth1 and eth2 which are
> not in use at all). Networking of Dom0 is fine.
> 
> Starting a domU produces a vifX.0 successfully, but with/out touching
> the scripts in /etc/xen/ I can't make the domU to ping anything except
> itself.
> 
> 
> Here is what I have after fresh Dom0 boot:
> 
>   lvs01:~ # brctl show xenbr0
>   bridge name     bridge id               STP enabled     interfaces
>   xenbr0          8000.000000000000       no
> 
> And this after starting DomU:
> 
>   lvs01:~ # brctl show xenbr0
>   bridge name     bridge id               STP enabled     interfaces
>   xenbr0          8000.feffffffffff       no              vif1.0
> 
> 
> Since I am new to xen I assume I miss something crucial here. Or beta6
> has a bug? Any hint for enlightment is welcome.
> 
> Thanks,

I received one private reply recommending not using SuSE. However, I am
kind of sceptical here since Kurt Garloff from SuSE explicitely writes
Xen RPM's for SuSE.

However, I wrote him an email explaining the problem and to share the
gained knowledge I'll translate his German reply here:


"To make everything work with SuSE you have to set up your network as
follows:
1) choose the 'classic' way of setting up network (no 'NetworkManager'
as offered by Yast)
2) put STARTMODE of ifplugd to 'onboot' (defaults to 'on connect')
3) turn off SuSEfirewall2 or configure it properly
4) enable ip_forward (either by using Yast or sysctl.conf)"

In my case 2, 3, 4 and a reboot fixed it. I have full network of Dom0
and DomU now. I'll put Kurt Garloffs hints into the wiki on

   http://en.opensuse.org/Installing_Xen3


Thanks Kurt!

-- 

 Stephan A. Rickauer

 -----------------------------------------------------------
 Institut für Neuroinformatik          Tel: +41 44 635 30 50
 Universität / ETH Zürich              Sek: +41 44 635 30 52
 Winterthurerstrasse 190               Fax: +41 44 635 30 53
 CH-8057 Zürich                        Web:  www.ini.ethz.ch

 RSA public key: https://www.ini.ethz.ch/~stephan/pubkey.asc
 -----------------------------------------------------------

Attachment: signature.asc
Description: OpenPGP digital signature

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