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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-users] Unable to ping guest hostname

from [Stephen Liu] [Permanent Link][Original]
To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Unable to ping guest hostname
From: Stephen Liu <satimis@xxxxxxxxx>
Date: Wed, 17 Sep 2008 22:55:18 +0800 (CST)
Cc:
Delivery-date: Wed, 17 Sep 2008 07:56:00 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=kjBSWa/ADizYRpYpqu2pVtA1g3bO+8cMpICioTj4Yxat31qKgZejQZFBjOcLF/DtvTj99UbGvV10jVCZcZw/Zwlgruj0SpDh184Gllz7OO0OqojCiiVwWpXmw64fyqDCnioRdhrvNPKLcCqnUpmD4PaBWi5yxt9fgQnXWcbyTKQ=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1221657988.4727.63.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
Hi Nemeth,


I discover the cause of my problem.  It is an old file
"/etc/xen/xen1.example.com" which hasn't been deleted.  Its disk.img
and swap.img have been removed. After changing its name as
xen1.example.com.old problem disappears.  Host can ping Guest names and
Guest can ping each other's name and Host's name.  ssh connect Guest on
hostname works as well.


But there is still a problem remaining behind.  I can't run Guest;


# xm console xen1.satimis.com
netfront: device eth0 has copying receive path.

# xm console xen2.satimis.com
netfront: device eth0 has copying receive path.

# xm console xen3.satimis.com
netfront: device eth0 has copying receive path.

Please advise.  TIA


B.R.
Stephen L


--- "Nemeth, Tamas" <nice@xxxxxxxxxxxxxxx> wrote:

> It seemss to be much simpler, I tought before. Where do you try the
> pinging from. From which host? From dom0? Or from each other? Or from
> external hosts? What are the hostnames, and where are they stored? In
> DNS, or in /etc/hosts files on all hosts? DNS may not be updated,
> which
> is a totally Xen-independent problem.
> 
> BTW please do the following command on dom0 and both domUs:
> 
> cat /etc/hosts
> 
> 2008. 09. 17, szerda keltezéssel 21.04-kor Stephen Liu ezt írta:
> > --- "Nemeth, Tamas" <nice@xxxxxxxxxxxxxxx> wrote:
> > 
> > > So, here are the commands again:
> > > 
> > > brctl show
> > > ip route show
> > > ip address show
> > > cat /etc/resolv.conf
> > > for i in /proc/sys/net/bridge/* ; do echo "$i $(<$i)" ; done
> > > iptables -t filter -L -nv
> > 
> > 
> > Hi Nemeth,
> > 
> > 
> > Here again
> > 
> > 
> > Host
> > ====
> > 
> > # brctl show
> > bridge name     bridge id               STP enabled     interfaces
> > xenbr0          8000.feffffffffff       no              vif0.0
> >                                                         peth0
> >                                                         vif1.0
> >                                                         vif2.0
> >                                                         vif3.0
> >                                                         vif4.0
> > 
> > 
> > # ip route show
> > 192.168.0.0/24 dev eth0  proto kernel  scope link  src
> 192.168.0.110
> > default via 192.168.0.1 dev eth0
> > server1:/home/satimis# ip address show
> > 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
> >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     inet 127.0.0.1/8 scope host lo
> >     inet6 ::1/128 scope host
> >        valid_lft forever preferred_lft forever
> > 2: vif0.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> >     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
> >        valid_lft forever preferred_lft forever
> > 3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
> >     link/ether 00:0e:a6:f9:a3:5b brd ff:ff:ff:ff:ff:ff
> >     inet 192.168.0.110/24 brd 192.168.0.255 scope global eth0
> >     inet6 fe80::20e:a6ff:fef9:a35b/64 scope link
> >        valid_lft forever preferred_lft forever
> > 4: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> > 5: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> > 6: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> > 7: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> > 8: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> > 9: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> > 10: peth0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast
> qlen
> > 1000
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> >     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
> >        valid_lft forever preferred_lft forever
> > 11: sit0: <NOARP> mtu 1480 qdisc noop
> >     link/sit 0.0.0.0 brd 0.0.0.0
> > 12: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> > 13: vif1.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast
> qlen
> > 32
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> >     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
> >        valid_lft forever preferred_lft forever
> > 14: vif2.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast
> qlen
> > 32
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> >     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
> >        valid_lft forever preferred_lft forever
> > 15: vif3.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast
> qlen
> > 32
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> >     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
> >        valid_lft forever preferred_lft forever
> > 16: vif4.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast
> qlen
> > 32
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> >     inet6 fe80::fcff:ffff:feff:ffff/64 scope link
> >        valid_lft forever preferred_lft forever
> > 
> > 
> > # cat /etc/resolv.conf
> > # generated by NetworkManager, do not edit!
> > 
> > nameserver 202.14.67.14
> > nameserver 192.168.0.1
> > nameserver 192.168.0.110
> > nameserver 192.168.0.111
> > nameserver 192.168.0.112
> > nameserver 192.168.0.113
> > 
> > 
> > # for i in /proc/sys/net/bridge/* ; do echo "$i $(<$i)" ; done
> > /proc/sys/net/bridge/bridge-nf-call-arptables 1
> > /proc/sys/net/bridge/bridge-nf-call-ip6tables 1
> > /proc/sys/net/bridge/bridge-nf-call-iptables 1
> > /proc/sys/net/bridge/bridge-nf-filter-vlan-tagged 1
> > 
> > 
> > # iptables -t filter -L -nv
> > Chain INPUT (policy ACCEPT 1376 packets, 1616K bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> > 
> > Chain FORWARD (policy ACCEPT 2596 packets, 1748K bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> >     0     0 ACCEPT     0    --  *      *       192.168.0.111       
> > 0.0.0.0/0           PHYSDEV match --physdev-in vif1.0
> >     0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
> > 0.0.0.0/0           PHYSDEV match --physdev-in vif1.0 udp spt:68
> dpt:67
> >     0     0 ACCEPT     0    --  *      *       192.168.0.112       
> > 0.0.0.0/0           PHYSDEV match --physdev-in vif2.0
> >     0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
> > 0.0.0.0/0           PHYSDEV match --physdev-in vif2.0 udp spt:68
> dpt:67
> >     0     0 ACCEPT     0    --  *      *       192.168.0.113       
> > 0.0.0.0/0           PHYSDEV match --physdev-in vif3.0
> >     0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
> > 0.0.0.0/0           PHYSDEV match --physdev-in vif3.0 udp spt:68
> dpt:67
> >     0     0 ACCEPT     0    --  *      *       192.168.0.114       
> > 0.0.0.0/0           PHYSDEV match --physdev-in vif4.0
> >     0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
> > 0.0.0.0/0           PHYSDEV match --physdev-in vif4.0 udp spt:68
> dpt:67
> > 
> > Chain OUTPUT (policy ACCEPT 1189 packets, 130K bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> > 
> > 
> > 
> > Original Guest
> > ==============
> > 
> > # brctl show
> > bridge name     bridge id               STP enabled     interfaces
> > 
> > 
> > # ip route show
> > 192.168.0.0/24 dev eth0  proto kernel  scope link  src
> 192.168.0.112
> > default via 192.168.0.1 dev eth0
> > 
> > 
> > # ip address show
> > 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
> >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     inet 127.0.0.1/8 scope host lo
> >     inet6 ::1/128 scope host
> >        valid_lft forever preferred_lft forever
> > 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast
> qlen
> > 1000
> >     link/ether 00:16:3e:41:39:04 brd ff:ff:ff:ff:ff:ff
> >     inet 192.168.0.112/24 brd 192.168.0.255 scope global eth0
> >     inet6 fe80::216:3eff:fe41:3904/64 scope link
> >        valid_lft forever preferred_lft forever
> > 3: sit0: <NOARP> mtu 1480 qdisc noop
> >     link/sit 0.0.0.0 brd 0.0.0.0
> > 
> > 
> > # cat /etc/resolv.conf
> > # generated by NetworkManager, do not edit!
> > nameserver 202.14.67.14
> > nameserver 192.168.0.1
> > 
> > 
> > # for i in /proc/sys/net/bridge/* ; do echo "$i $(<$i)" ; done
> > /proc/sys/net/bridge/bridge-nf-call-arptables 1
> > /proc/sys/net/bridge/bridge-nf-call-ip6tables 1
> > /proc/sys/net/bridge/bridge-nf-call-iptables 1
> > /proc/sys/net/bridge/bridge-nf-filter-vlan-tagged 1
> > 
> > 
> > # iptables -t filter -L -nv
> > Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> > 
> > Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> > 
> > Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> > 
> > 
> > 
> > Cloned Guest
> > ============
> > 
> > # brctl show
> > bridge name     bridge id               STP enabled     interfaces
> > 
> > 
> > # ip route show
> > 192.168.0.0/24 dev eth0  proto kernel  scope link  src
> 192.168.0.113
> > default via 192.168.0.1 dev eth0
> > 
> > 
> > # ip address show
> > 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
> >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     inet 127.0.0.1/8 scope host lo
> >     inet6 ::1/128 scope host
> >        valid_lft forever preferred_lft forever
> > 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast
> qlen
> > 1000
> >     link/ether 00:16:3e:53:a9:68 brd ff:ff:ff:ff:ff:ff
> >     inet 192.168.0.113/24 brd 192.168.0.255 scope global eth0
> >     inet6 fe80::216:3eff:fe53:a968/64 scope link
> >        valid_lft forever preferred_lft forever
> > 3: sit0: <NOARP> mtu 1480 qdisc noop
> >     link/sit 0.0.0.0 brd 0.0.0.0
> > 
> > 
> > # cat /etc/resolv.conf
> > # generated by NetworkManager, do not edit!
> > nameserver 202.14.67.14
> > nameserver 192.168.0.1
> > nameserver 192.168.0.2
> > nameserver 192.168.0.3
> > 
> > 
> > # for i in /proc/sys/net/bridge/* ; do echo "$i $(<$i)" ; done
> > /proc/sys/net/bridge/bridge-nf-call-arptables 1
> > /proc/sys/net/bridge/bridge-nf-call-ip6tables 1
> > /proc/sys/net/bridge/bridge-nf-call-iptables 1
> > /proc/sys/net/bridge/bridge-nf-filter-vlan-tagged 1
> > 
> > 
> > # iptables -t filter -L -nv
> > Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> > 
> > Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> > 
> > Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> > 
> > 
> > 
> > B.R.
> > Stephen L
> > 
> > Send instant messages to your online friends
> http://uk.messenger.yahoo.com 
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> 
> 


Send instant messages to your online friends http://uk.messenger.yahoo.com 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-users] is it possible to mount a domU's LVM partition in dom0 ?, Rudi Ahlers
Next by Date:  [Xen-users] xm delete - Error: <Fault 3: 'machine1'>, Stefan Bauer
Previous by Thread:  Re: [Xen-users] Unable to ping guest hostname, Stephen Liu
Next by Thread:  Re: [Xen-users] Unable to ping guest hostname, Stephen Liu
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy