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/
Home Products Support Community News


[Xen-users] SuSE 9.3 domU /sbin/ifup workaround

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] SuSE 9.3 domU /sbin/ifup workaround
From: Robbie Dinn <robbie@xxxxxxxxxxxx>
Date: Mon, 13 Jun 2005 16:23:45 +0100
Delivery-date: Mon, 13 Jun 2005 15:22:54 +0000
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/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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.8 (X11/20040913)
Hi all

I have a SuSE 9.3 domU. It has a eth0 interface, corresponding
to some vif interface in the dom0. Running

  ifup eth0

doesn't seem to work. This means I don't get any network.

It seems that /sbin/ifup relies upon /sbin/getcfg but getcfg
does not seem to find the right configuration for the eth0 device.

A attached a patch below with a work around for this. It's
only a work around, because it patches ifup, but I think the
real problem might be with getcfg.

If you want to try this patch, I suggest keeping the original
file around, like so

  mv /sbin/ifup /sbin/ifup.orig
  cp /sbin/ifup.orig /sbin/ifup
  cat patch-ifup | patch /sbin/ifup

hope that helps someone.
--- /sbin/ifup.orig     2005-03-21 16:03:50.000000000 +0000
+++ /sbin/ifup  2005-06-13 14:34:29.000000000 +0000
@@ -127,6 +127,17 @@
 case $SCRIPTNAME in
+               # XXX HACK STARTS
+               case $INTERFACE in
+                       eth[0-9])
+                               if [ -z "$HWD_CONFIG_0" \
+                                       -a -e 
/sys/class/net/${INTERFACE}/address ] ; then
+                                       HWD_CONFIG_0="eth-id-$(cat 
+                               fi
+                               ;;
+                        *) ;;
+               esac
+               # XXX HACK ENDS
                if [ -z "$CONFIG" -a "$DHCP" = yes ] ; then
                        # This time we were called from dhcpcd just to finish 
setup (hooks,
                        # routes) and thus must use for sure the same config as 
in the first
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>