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] domU network problem SOLVED

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU network problem SOLVED
From: Jimmy Pierre <jpierre@xxxxxxxxxxx>
Date: Mon, 23 Jan 2006 04:36:32 -0600
Cc: jpierre@xxxxxx
Delivery-date: Mon, 23 Jan 2006 10:45:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200601231101.19289.schueffler@xxxxxxxxxxxxx>
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>
References: <200601051755.30585.schueffler@xxxxxxxxxxxxx> <200601231101.19289.schueffler@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) H3 (4.0.3)
Hallo Stefan

Great! Now, is it at all possible to share wityh us the steps to your success?

I have tried http://www.opensuse.org/Installing_Xen3 all this week end, to no
avail!

Maybe you've got the correct recipe :-)

Cheers,
Jimmy
nui.fr

Quoting Stefan Schueffler <schueffler@xxxxxxxxxxxxx>:

Hi all,

thanks for your help, i got it working.

The solution to the problem is that suse linux has a
udev-rule to create persistent names for hotplug-devices enabled by
default.

using the xen-feature to set a random mac-address for the interface leads
to the situation, that suse must give a new device-id on every boot, as
the network card appears to be a "new" one (new unseen mac-address) and
the old device-ids are locked by suse for the old mac-address.

the solution is either
a) to remove the udev-rule for persistent device-ids or
b) to set a fixed mac-address so that suse can use the same interface-id
on each boot.

Some informations:
on suse linux 10 (and probably 9.3 als) the udev-rules are located in
/etc/udev/rules.d/
the rule to set a new device-id (eth0, eth1, ethxx...) is located in
31-net_create_names.rules
old assignment (mac-address-to-device-id) are stored in
30-net_persistent_names.rules
there you should delete the assignments set by suse on your first hundred
reboots while trying to solve the problem :-)

regards
Stefan Schueffler

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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