Hi folks, Debian Etch Guests created with xen-create-image can be pinged on Host either on hostname or on local ip. They can also be ssh-connected on both. But Guests cloned on existing Guests can''t be pinged on hostname. It can be pinged on local ip. Also can only be ssh-connected on local ip. Please advise where I have to check and how to fix the problem. TIA B.R. satimis Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi! Please send the config file (or running config extracted by "xm list --long DOMAINNAME" of both the original and the cloned domU, and the the output of the following commands from the dom0 and both the original and the cloned domU: 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 2008. 09. 17, szerda keltezéssel 15.24-kor Stephen Liu ezt írta:> Hi folks, > > > Debian Etch > > > Guests created with xen-create-image can be pinged on Host either on > hostname or on local ip. They can also be ssh-connected on both. > > But Guests cloned on existing Guests can''t be pinged on hostname. It > can be pinged on local ip. Also can only be ssh-connected on local ip. > > Please advise where I have to check and how to fix the problem. TIA > > > B.R. > satimis > > Send instant messages to your online friends http://uk.messenger.yahoo.com > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Nemeth,> Please send the config file (or running config extracted by "xm list > --long DOMAINNAME" of both the original and the cloned domU, and the > the > output of the following commands from the dom0 and both the original > and > the cloned domU: > > 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 -nvOriginal Guest $ sudo xm list --long xen2.satimis.com (domain (domid 2) (on_crash restart) (uuid 611e874c-f5b7-7af5-fa93-fcb4fe7eb264) (bootloader_args ) (vcpus 1) (name xen2.satimis.com) (on_poweroff destroy) (on_reboot restart) (bootloader ) (maxmem 32) (memory 32) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (start_time 1221625721.15) (cpu_time 0.045730597) (online_vcpus 1) (image (linux (kernel /boot/vmlinuz-2.6.18-xen) (args ''root=/dev/hda1 ro '') (rtc_timeoffset 0) (notes (HV_START_LOW 4227858432) (FEATURES ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'' ) (VIRT_BASE 3221225472) (GUEST_VERSION 2.6) (PADDR_OFFSET 3221225472) (GUEST_OS linux) (HYPERCALL_PAGE 3222278144) (LOADER generic) (SUSPEND_CANCEL 1) (PAE_MODE no) (ENTRY 3222274048) (XEN_VERSION xen-3.0) ) ) ) (status 2) (state -b----) (store_mfn 893581) (console_mfn 893573) (device (vif (uuid 9c953621-e12c-ccd6-d335-f739dd8d99b1) (script vif-bridge) (ip 192.168.0.112) (mac 00:16:3e:41:39:04) (type netfront) (backend 0) ) ) (device (vbd (uname file:/vserver/domains/xen2.satimis.com/disk.img) (uuid d26e20bf-7fe9-45bd-0cfa-5fbab7dd25ea) (mode w) (dev hda1:disk) (backend 0) (bootable 1) ) ) (device (vbd (uname file:/vserver/domains/xen2.satimis.com/swap.img) (uuid 48af2e20-a9c3-25ea-3665-9273861aaabd) (mode w) (dev hda2:disk) (backend 0) (bootable 0) ) ) (device (console (protocol vt100) (location 2) (uuid e72dbb9f-5099-e2d4-b895-c8cd09086a26) ) ) ) * end * Cloned Guest $ sudo xm list --long xen3.satimis.com (domain (domid 3) (on_crash restart) (uuid 40c04719-1611-a1f3-6594-3a3607a209b2) (bootloader_args ) (vcpus 1) (name xen3.satimis.com) (on_poweroff destroy) (on_reboot restart) (bootloader ) (maxmem 32) (memory 32) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (start_time 1221631158.82) (cpu_time 0.048315668) (online_vcpus 1) (image (linux (kernel /boot/vmlinuz-2.6.18-xen) (args ''root=/dev/hda1 ro '') (rtc_timeoffset 0) (notes (HV_START_LOW 4227858432) (FEATURES ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'' ) (VIRT_BASE 3221225472) (GUEST_VERSION 2.6) (PADDR_OFFSET 3221225472) (GUEST_OS linux) (HYPERCALL_PAGE 3222278144) (LOADER generic) (SUSPEND_CANCEL 1) (PAE_MODE no) (ENTRY 3222274048) (XEN_VERSION xen-3.0) ) ) ) (status 2) (state -b----) (store_mfn 25550) (console_mfn 25542) (device (vif (uuid a790390f-4558-c3b7-d8ba-be7dad66ba35) (script vif-bridge) (ip 192.168.0.113) (mac 00:16:3e:53:a9:68) (type netfront) (backend 0) ) ) (device (vbd (uname file:/vserver/domains/xen3.satimis.com/disk.img) (uuid d44e14b3-e543-4ec3-0026-9d4f16ef917f) (mode w) (dev hda1:disk) (backend 0) (bootable 1) ) ) (device (vbd (uname file:/vserver/domains/xen3.satimis.com/swap.img) (uuid b3d78288-1b45-0789-3aee-d46c0e5ad364) (mode w) (dev hda2:disk) (backend 0) (bootable 0) ) ) (device (console (protocol vt100) (location 2) (uuid e1cb689a-585f-5427-0cc2-ca2231b7df6f) ) ) ) * end * 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 # 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 Sorry I can''t read the other 3 command lines. Original Guest ============= Console-1 # xm console xen2.satimis.com netfront: device eth0 has copying receive path. Hanging here Console-2 $ ssh 192.168.0.112 satimis@192.168.0.112''s password: satimis@xen2:~$ su # 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 # cat /etc/resolv.conf # generated by NetworkManager, do not edit! nameserver 202.14.67.14 nameserver 192.168.0.1 Cloned guest =========== Console-3 # xm console xen3.satimis.com netfront: device eth0 has copying receive path. also hanging. Console-4 $ ssh 192.168.0.113 -p 50505 satimis@192.168.0.113''s password: $ su # 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 # 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 B.R. Stephen L> 2008. 09. 17, szerda keltezéssel 15.24-kor Stephen Liu ezt Ãrta: > > Hi folks, > > > > > > Debian Etch > > > > > > Guests created with xen-create-image can be pinged on Host either > on > > hostname or on local ip. They can also be ssh-connected on both. > > > > But Guests cloned on existing Guests can''t be pinged on hostname. > It > > can be pinged on local ip. Also can only be ssh-connected on local > ip. > > > > Please advise where I have to check and how to fix the problem. > TIA > > > > > > B.R. > > satimis > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > >Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
--- "Nemeth, Tamas" <nice@titanic.nyme.hu> 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 -nvHi 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@lists.xensource.com http://lists.xensource.com/xen-users
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@titanic.nyme.hu> 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@titanic.nyme.hu> 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@lists.xensource.com > > http://lists.xensource.com/xen-users > >Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Nemeth, I found the cause. To make "xm console hostname" work it must be executed following "xm create /path/to/hostname.cfg" On starting PC I found; # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3417 2 r----- 40.7 xen1.satimis.com 1 32 1 -b---- 0.0 xen3.satimis.com 2 32 1 -b---- 0.0 xen4.satimis.com 3 32 1 -b---- 0.0 They are already running. Why and How? I have no idea. # ls -l /etc/xen/auto total 0 There is no symbolic link. To make them work I must run; # xm shutdown xen1.satimis.com # xm shutdown xen3.satimis.com # xm shutdown xen4.satimis.com and restart them # xm create /etc/xen1.satimis.com # xm create /etc/xen3.satimis.com # xm create /etc/xen4.satimis.com respectively. Then run # xm console xen1.satimis.com # xm console xen3.satimis.com # xm console xen4.satimis.com All of them work. Please shed me some light how to prevent them start at boot. TIA B.R. Stephen --- Stephen Liu <satimis@yahoo.com> wrote:> Date: Wed, 17 Sep 2008 23:12:12 +0800 (CST) > From: Stephen Liu <satimis@yahoo.com> > Subject: Re: [Xen-users] Unable to ping guest hostname > To: "Nemeth, Tamas" <nice@titanic.nyme.hu> > > > --- "Nemeth, Tamas" <nice@titanic.nyme.hu> wrote: > > > Have you solved your problem? > > Yes. > > Problem re: > > "ping hostname" > > and > > "ssh user@hostname" > > > are now working. > > > Just found another problem on running the guest (all guests); > > > # xm console xen3.satimis.com > netfront: device eth0 has copying receive path. > > > Running all guests popup the same warning. > > > B.R. > Stephen L > > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com >Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I really don''t know, but perhaps they are in the xenstore I see mentioned every so often (maybe xm new can put them in there where xm create doesn''t, I don''t know). In this case, according to another ticket that may be wrong, xm delete should remove them. If it doesn''t, you might try xm shutdown before xm delete (or do they disappear when you do xm shutdown?). Did you install them using virt-install? Perhaps some command from the same package as virt-install would remove them in that case. These are stabs in the dark, but perhaps one of them will get you where you''re looking to go. Dustin -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Stephen Liu Sent: Wednesday, September 17, 2008 12:34 To: xen-users@lists.xensource.com Subject: Re: [Xen-users] Unable to ping guest hostname Hi Nemeth, I found the cause. To make "xm console hostname" work it must be executed following "xm create /path/to/hostname.cfg" On starting PC I found; # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3417 2 r----- 40.7 xen1.satimis.com 1 32 1 -b---- 0.0 xen3.satimis.com 2 32 1 -b---- 0.0 xen4.satimis.com 3 32 1 -b---- 0.0 They are already running. Why and How? I have no idea. # ls -l /etc/xen/auto total 0 There is no symbolic link. To make them work I must run; # xm shutdown xen1.satimis.com # xm shutdown xen3.satimis.com # xm shutdown xen4.satimis.com and restart them # xm create /etc/xen1.satimis.com # xm create /etc/xen3.satimis.com # xm create /etc/xen4.satimis.com respectively. Then run # xm console xen1.satimis.com # xm console xen3.satimis.com # xm console xen4.satimis.com All of them work. Please shed me some light how to prevent them start at boot. TIA B.R. Stephen --- Stephen Liu <satimis@yahoo.com> wrote:> Date: Wed, 17 Sep 2008 23:12:12 +0800 (CST) > From: Stephen Liu <satimis@yahoo.com> > Subject: Re: [Xen-users] Unable to ping guest hostname > To: "Nemeth, Tamas" <nice@titanic.nyme.hu> > > > --- "Nemeth, Tamas" <nice@titanic.nyme.hu> wrote: > > > Have you solved your problem? > > Yes. > > Problem re: > > "ping hostname" > > and > > "ssh user@hostname" > > > are now working. > > > Just found another problem on running the guest (all guests); > > > # xm console xen3.satimis.com > netfront: device eth0 has copying receive path. > > > Running all guests popup the same warning. > > > B.R. > Stephen L > > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com >Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
--- Dustin Henning <Dustin.Henning@prd-inc.com> wrote:> I really don''t know, but perhaps they are in the xenstore I see > mentioned every so often (maybe xm new can put them in there where xm > create > doesn''t, I don''t know). In this case, according to another ticket > that may > be wrong, xm delete should remove them. If it doesn''t, you might try > xm > shutdown before xm delete (or do they disappear when you do xm > shutdown?). > Did you install them using virt-install? Perhaps some command from > the same > package as virt-install would remove them in that case. These are > stabs in > the dark, but perhaps one of them will get you where you''re looking > to go.Hi Dustin, I solved my problem already. Before switching off the PC OR rebooting PC all running Guests must be stopped with; # xm shutdown xen1... # xm shutdown xen2... etc. If without running above step on next boot/reboot all previous running Guest will be started automatically. It is NOT necessary creating a symbolic link; # ln -s /etc/xen/xen1.example.com.cfg /etc/xen/auto etc. to start the Guests at boot. I have 4 Guests created on the PC, xen1, xen2, xen3 and xen4. xen1 and xen2 were built with "xen-create-image". xen3 was cloned on xen2 after its creation. xen4 was also cloned on xen2 but after building a mail server on it. All of them are working and can be ssh-connected on IP and hostname except xen4 which can be ssh-connected on IP but NOT on domain, complaining domain not found. I don''t know its cause. I''ll leave it for the time being. The problem, I suppose, is caused by cloning a running mail server. Are you aware is there a Xen command to update and upgrade globally, i.e. running the Xen command on Host will automatically update/upgrade guests of same Linux distro, similar to "vapt-get" on "Vserser". Thanks B.R. Stephen L> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Stephen > Liu > Sent: Wednesday, September 17, 2008 12:34 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Unable to ping guest hostname > > Hi Nemeth, > > > I found the cause. > > > To make "xm console hostname" work it must be executed following "xm > create /path/to/hostname.cfg" > > > On starting PC I found; > > # xm list > Name ID Mem VCPUs State Time(s) > Domain-0 0 3417 2 r----- 40.7 > xen1.satimis.com 1 32 1 -b---- 0.0 > xen3.satimis.com 2 32 1 -b---- 0.0 > xen4.satimis.com 3 32 1 -b---- 0.0 > > > They are already running. Why and How? I have no idea. > > > # ls -l /etc/xen/auto > total 0 > > There is no symbolic link. > > > To make them work I must run; > > # xm shutdown xen1.satimis.com > # xm shutdown xen3.satimis.com > # xm shutdown xen4.satimis.com > > > and restart them > > # xm create /etc/xen1.satimis.com > # xm create /etc/xen3.satimis.com > # xm create /etc/xen4.satimis.com > > respectively. > > > Then run > > # xm console xen1.satimis.com > # xm console xen3.satimis.com > # xm console xen4.satimis.com > > > All of them work. > > > Please shed me some light how to prevent them start at boot. TIA > > > B.R. > Stephen > > > > --- Stephen Liu <satimis@yahoo.com> wrote: > > > Date: Wed, 17 Sep 2008 23:12:12 +0800 (CST) > > From: Stephen Liu <satimis@yahoo.com> > > Subject: Re: [Xen-users] Unable to ping guest hostname > > To: "Nemeth, Tamas" <nice@titanic.nyme.hu> > > > > > > --- "Nemeth, Tamas" <nice@titanic.nyme.hu> wrote: > > > > > Have you solved your problem? > > > > Yes. > > > > Problem re: > > > > "ping hostname" > > > > and > > > > "ssh user@hostname" > > > > > > are now working. > > > > > > Just found another problem on running the guest (all guests); > > > > > > # xm console xen3.satimis.com > > netfront: device eth0 has copying receive path. > > > > > > Running all guests popup the same warning. > > > > > > B.R. > > Stephen L > > > > > > > > > > Send instant messages to your online friends > > http://uk.messenger.yahoo.com > > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users