Boris Derzhavets wrote:>
*********************************************************************************
> bash-3.2# dladm show-dev
> LINK STATE SPEED DUPLEX
> rge0 up 100Mb full
> bash-3.2# svccfg -s xend listprop|grep default-nic
> config/default-nic astring rge0
>
**********************************************************************************
> bash-3.2# xm list
> Name ID Mem VCPUs State Time(s)
> Domain-0 0 3886 2 r----- 47.6
> RHEL51PVM 1024 1 0.0
>
**********************************************************************************
> bash-3.2# xm start RHEL51PVM
> bash-3.2# xm console RHEL51PVM
> rtc: IRQ 8 is not free.
> rtc: IRQ 8 is not free.
> i8042.c: No controller found.
> Red Hat nash version 5.1.19.6 starting
> Reading all physical volumes. This may take a
> while...
> Found volume group "VolGroup00" using metadata type
> lvm2
> 2 logical volume(s) in volume group "VolGroup00" now
> active
> Welcome to CentOS release 5 (Final)
> Press ''I'' to enter interactive
> startup.
> Cannot access the Hardware Clock via any known method.
> Use the --debug option to see the details of our
> search for an access method.
> Setting clock (localtime): Mon Apr 7 09:52:25 EDT
> 2008 [ OK ]
> Starting udev: [ OK ]
> Setting hostname RHL51PVM: [ OK ]
> Setting up Logical Volume Management: 2 logical
> volume(s) in volume group "VolGroup00" now active
> [ OK ]
> Checking filesystems
> Checking all file systems.
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a
> /dev/VolGroup00/LogVol00
> /dev/VolGroup00/LogVol00: clean, 164617/5227520 files,
> 1248037/5226496 blocks
> [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/xvda1
>
> /boot: clean, 36/26104 files, 16419/104388 blocks
> [ OK ]
> Remounting root filesystem in read-write mode: [ OK
> ]
> Mounting local filesystems: [ OK ]
> Enabling local filesystem quotas: [ OK ]
> Enabling /etc/fstab swaps: [ OK ]
> INIT: Entering runlevel: 3
> Entering non-interactive startup
> Applying Intel CPU microcode update: [FAILED]
> Starting monitoring for VG VolGroup00: 2 logical
> volume(s) in volume group "VolGroup00" monitored
> [ OK ]
> Starting background readahead: [ OK ]
> Checking for hardware changes [ OK ]
> Bringing up loopback interface: [ OK ]
> Bringing up interface eth0: [ OK ]
> Starting auditd: [ OK ]
> Starting system logger: [ OK ]
> Starting kernel logger: [ OK ]
> Starting irqbalance: [ OK ]
> Starting portmap: [ OK ]
> Starting NFS statd: [ OK ]
> Starting RPC idmapd: [ OK ]
> Starting system message bus: [ OK ]
> [ OK ] Bluetooth services:[ OK ]
> Mounting other filesystems: [ OK ]
> Starting PC/SC smart card daemon (pcscd): [ OK ]
> Starting hidd: [ OK ]
> Starting autofs: Loading autofs4: [ OK ]
> Starting automount: [ OK ]
> [ OK ]
> Starting hpiod: [ OK ]
> Starting hpssd: [ OK ]
> Starting sshd: [ OK ]
> Starting cups: [ OK ]
> Starting xinetd: [ OK ]
> Starting console mouse services: [ OK ]
> Starting crond: [ OK ]
> Starting xfs: [ OK ]
> Starting VNC server: 1:root
> New ''RHL51PVM:1 (root)'' desktop is RHL51PVM:1
>
> Starting applications specified in /root/.vnc/xstartup
> Log file is /root/.vnc/RHL51PVM:1.log
>
> [ OK ]
> Starting anacron: [ OK ]
> Starting atd: [ OK ]
> Starting yum-updatesd: [ OK ]
> Starting Avahi daemon... [ OK ]
> Starting HAL daemon: [ OK ]
> Starting smartd: [ OK ]
>
> CentOS release 5 (Final)
> Kernel 2.6.18-53.el5xen on an x86_64
>
> RHL51PVM login: root
> Password:
> Last login: Mon Apr 7 01:27:59 from 192.168.1.35
> [root@RHL51PVM ~]# uname -a
> Linux RHL51PVM 2.6.18-53.el5xen #1 SMP Mon Nov 12
> 02:46:57 EST 2007 x86_64 x86_64 x86_64 GNU/Linux
> [root@RHL51PVM ~]#
> ****************************
> From another window:-
> ****************************
> bash-3.2# xm list -l RHEL51PVM
> (domain
> (domid 1)
> (on_crash restart)
> (uuid c88e36b5-3684-4a7c-94bf-5b4dde6a8ab8)
> (bootloader_args )
> (vcpus 1)
> (name RHEL51PVM)
> (on_poweroff destroy)
> (on_reboot restart)
> (bootloader /usr/lib/xen/bin/pygrub)
> (maxmem 1024)
> (memory 1024)
> (shadow_memory 0)
> (cpu_weight 256)
> (cpu_cap 0)
> (features )
> (on_xend_start ignore)
> (on_xend_stop shutdown)
> (start_time 1207565532.56)
> (cpu_time 13.152320513)
> (online_vcpus 1)
> (image
> (linux
> (kernel )
> (notes
> (FEATURES
>
>
''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel''
> )
> (VIRT_BASE 18446744071562067968)
> (GUEST_VERSION 2.6)
> (PADDR_OFFSET 18446744071562067968)
> (GUEST_OS linux)
> (HYPERCALL_PAGE 18446744071564189696)
> (LOADER generic)
> (ENTRY 18446744071564165120)
> (XEN_VERSION xen-3.0)
> )
> )
> )
> (status 2)
> (state -b----)
> (store_mfn 1182319)
> (console_mfn 1182314)
> (device
> (vif
> (mac 00:16:3e:72:f0:c1)
> (script vif-vnic)
> (uuid
> 092552fd-9f72-34dd-be5e-922b98b238c2)
> (backend 0)
> )
> )
> (device
> (vbd
> (uname
> phy:/dev/zvol/dsk/vmpool/snv85-disk)
> (uuid
> c857483e-39d8-bed1-7dc7-3e3b70e2b583)
> (mode w)
> (dev xvda:disk)
> (backend 0)
> (bootable 1)
> )
> )
> (device
> (console
> (protocol vt100)
> (location 2)
> (uuid
> 83794170-fe91-696a-736a-81e24b5c8236)
> )
> )
> )
> *******************************************************
>
>
>
>
> --- Mark Johnson <Mark.Johnson@Sun.COM> wrote:
>
>>
>> Boris Derzhavets wrote:
>>> Why any TCP application layer protocol like
>>> ssh,vncviewer,http cannot get in Linux (or SNV)
>> DomU
>>> at SNV85 Dom0 if it comes from any machine on the
>> LAN
>>> different from SNV85 Dom0 ?
>>> At the same time CentOS 5.1 DomU is pingable from
>>> anywhere on the LAN.
>>> I have to ssh to SNV85 Dom0 and then ssh to Linux
>>> DomU,
>>> then it works. However direct ssh connection to
>> DomU
>>> will hang.
>>> I can ssh with X11 forwarding from Cygwin/X
>> Windows PC
>>> to SNV Dom0 and the run :-
>>> $ vncviewer IP-DomU:1
>>> but attempt :-
>>> C:>vncviewer IP-DomU:1
>>> from the same Windows PC will fail.
>>> I didn''t notice such kind of problems accessing
>> any
>>> kinds of DomUs at Linux Dom0s.
>> I''m not sure. We don''t see those problems? What nic
>> does this system have? If you login to the Linux
>> domU
>> from the Xen console, can you ping out, etc?
> ****************
> Respond itself:-
> ****************
> That is all what i can. This is an issue:-
> DomU is ping able on the LAN (both directions :-)).
> Moreover from DomU i can ping ADSL modem and ISP''s DNS
> servers, but cannot trace route them , trace route
> times out ??
> ******
> Modem
> ******
> [root@RHL51PVM ~]# ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> 64 bytes from 192.168.1.1: icmp_seq=1 ttl=254
> time=0.594 ms
> 64 bytes from 192.168.1.1: icmp_seq=2 ttl=254
> time=0.661 ms
> 64 bytes from 192.168.1.1: icmp_seq=3 ttl=254
> time=0.570 ms
>
> --- 192.168.1.1 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss,
> time 1998ms
> rtt min/avg/max/mdev = 0.570/0.608/0.661/0.043 ms
> ******************
> First DNS server
> ******************
> [root@RHL51PVM ~]# ping 80.254.111.254
> PING 80.254.111.254 (80.254.111.254) 56(84) bytes of
> data.
> 64 bytes from 80.254.111.254: icmp_seq=1 ttl=61
> time=11.9 ms
> 64 bytes from 80.254.111.254: icmp_seq=2 ttl=61
> time=11.8 ms
> 64 bytes from 80.254.111.254: icmp_seq=3 ttl=61
> time=12.3 ms
> 64 bytes from 80.254.111.254: icmp_seq=4 ttl=61
> time=12.4 ms
>
> --- 80.254.111.254 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss,
> time 3002ms
> rtt min/avg/max/mdev = 11.808/12.136/12.434/0.305 ms
> ******************************
> Attempt traceroute DNS Server
> ******************************
> [root@RHL51PVM ~]# traceroute 80.254.111.254
> traceroute to 80.254.111.254 (80.254.111.254), 30 hops
> max, 40 byte packets
> 1 (192.168.1.1) 0.917 ms 1.289 ms 1.757 ms
> 2 (87.117.48.1) 13.656 ms 15.079 ms 16.926 ms
> 3 (80.254.108.189) 18.276 ms 19.282 ms 21.217 ms
> 4 * * *
> 5 * * *
> 6 * * *
> 7 * * *
> 8 * * *
> Same box is hosting F8 Dom0 (64-bit), Xen 3.2 CentOS51
> Dom0 (64-bit) and SNV85(84) DomUs at mentioned Dom0s.
> SNV85(84) DomUs are working just fine on the Internet
> and on the LAN.
strange.. I have the same NIC in my dom0.. I do not see
any problems with my Centos 5.1 domU.
[root@centos5-1 ~]# bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
rge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500
index 2
inet 192.168.0.70 netmask ffffff00 broadcast 192.168.0.255
ether 0:1a:4d:4b:64:37
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
bash-3.2# xm console centos5-1
[root@centos5-1 ~]#
[root@centos5-1 ~]# traceroute 192.168.100.1
traceroute to 192.168.100.1 (192.168.100.1), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.428 ms 0.377 ms 0.414 ms
2 192.168.100.1 (192.168.100.1) 0.966 ms 0.998 ms 1.041 ms
[root@centos5-1 ~]# uname -a
Linux centos5-1 2.6.18-53.1.4.el5xen #1 SMP Fri Nov 30 01:21:23 EST 2007 x86_64
x86_64 x86_64 GNU/Linux
[root@centos5-1 ~]#
[root@centos5-1 ~]# traceroute www.cnet.com
traceroute to www.cnet.com (216.239.122.220), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.278 ms 0.279 ms 0.412 ms
[CUT]
11 att-level3-oc192.NewYork1.Level3.net (4.68.127.150) 17.239 ms 16.767 ms
15.822 ms
12 tbr2.n54ny.ip.att.net (12.123.0.94) 55.576 ms 55.535 ms 56.573 ms
13 cr2.n54ny.ip.att.net (12.122.16.213) 55.410 ms 55.328 ms 58.667 ms
14 cr2.wswdc.ip.att.net (12.122.3.38) 59.721 ms 59.728 ms 60.081 ms
15 tbr1.wswdc.ip.att.net (12.122.16.62) 58.121 ms 58.053 ms 59.511 ms
16 tbr1.sl9mo.ip.att.net (12.122.10.30) 73.523 ms 73.789 ms 73.805 ms
17 tbr2.dlstx.ip.att.net (12.122.10.90) 56.855 ms 55.869 ms 55.693 ms
18 12.122.100.97 (12.122.100.97) 54.329 ms * 12.122.100.97 (12.122.100.97)
54.314 ms
19 12.87.121.22 (12.87.121.22) 55.538 ms 55.324 ms 55.473 ms
20 c18-ssa-xw-lb.cnet.com (216.239.122.220) 71.740 ms 71.680 ms 72.023 ms
[root@centos5-1 ~]#
I am running an older kernel..
[root@centos5-1 ~]# uname -a
Linux centos5-1 2.6.18-53.1.4.el5xen #1 SMP Fri Nov 30 01:21:23 EST 2007 x86_64
x86_64 x86_64 GNU/Linux
[root@centos5-1 ~]#
I''m updating it to 2.6.18-53.1.14.el5xen right now...
MRJ