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] Re: Cannot ping newly created XEN client running SLES10

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: Cannot ping newly created XEN client running SLES10
From: Christian Tramnitz <chris.ace@xxxxxxx>
Date: Wed, 30 Sep 2009 11:19:41 +0200
Delivery-date: Wed, 30 Sep 2009 02:21:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1068920728@xxxxxx>
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: <1068920728@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20090812)
c.monty@xxxxxx wrote:

I'm running multiple clients on a SLES10 server.

Is this dom0, domU or both?

These clients can be accessed in local network with ping.

Do you see the interface at all using "ifconfig -a" on domU?
Any RX/TX activity?
Any traffic when starting tcpdump on it?

When I create a new client with existing disk-files (copy of a running guest), 
I can start/boot the guest system.

Did you also copy the configuration file? If yes, did you modify the mac address?

However, I cannot ping the guest.

This would be one of the last things to check if the previous tests above indicate a working interface.

Is this related to an issue with the network bridge?
How can I resolve it?

I think this more likely related to either the config file (mac address collision) or udev in domU (if you copied the domU image udev will still reserve eth0 for the previous interface, identified by mac address)

Please note:
Displaying the network details (tab Hardware - Network), it shows
"bridge" in column Type, "-" in column Source,
"etho" in column Device

This is very Suse specific, please try to give more general information (ifconfig, brctl) and always mention if the information comes from dom0 or domU.

Best regards,

Xen-users mailing list

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