Port-xen archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: debugging xen networking scripts
Brad Pitney wrote:
> On Mon, Aug 25, 2008 at 7:46 PM, Christoph Egger
> <Christoph_Egger%gmx.de@localhost> wrote:
>> I think of two reasons for that behaviour:
>>
>> a) xenbackendd is not running
>
> I have 11 other domains running: all netbsd
>
> root 250 0.0 0.9 2124 1216 ? S Sat10AM 5:49.57
> xenstored --pid-file /var/run/xenstore.pid
> root 255 0.0 11.8 2056 15444 ? ZLl Sat10AM 3:09.43
> /usr/local/bin/python2.5 /usr/local/sbin/xend start
> root 259 0.0 0.0 2056 4 ? IW Sat10AM 0:00.01
> /usr/local/bin/python2.5 /usr/local/sbin/xend start
> root 280 0.0 0.5 2064 696 ? Isl Sat10AM 0:00.29
> /usr/local/sbin/xenbackendd
> root 2336 0.0 0.8 32796 972 ? Il Sat11AM 0:08.83 xenconsoled
>
>> b) there's no bridge0 configured
>
> bridge0: flags=41<UP,RUNNING>
> Configuration:
> priority 32768 hellotime 2 fwddelay 15 maxage 20
> ipfilter disabled flags 0x0
> Interfaces:
> xvif22.0 flags=3<LEARNING,DISCOVER>
> port 26 priority 128
> xvif21.0 flags=3<LEARNING,DISCOVER>
> port 25 priority 128
> xvif20.0 flags=3<LEARNING,DISCOVER>
> port 24 priority 128
> xvif19.0 flags=3<LEARNING,DISCOVER>
> port 23 priority 128
> xvif18.0 flags=3<LEARNING,DISCOVER>
> port 22 priority 128
> xvif16.0 flags=3<LEARNING,DISCOVER>
> port 21 priority 128
> xvif15.0 flags=3<LEARNING,DISCOVER>
> port 20 priority 128
> xvif14.0 flags=3<LEARNING,DISCOVER>
> port 19 priority 128
> xvif13.0 flags=3<LEARNING,DISCOVER>
> port 18 priority 128
> xvif12.0 flags=3<LEARNING,DISCOVER>
> port 17 priority 128
> sip0 flags=3<LEARNING,DISCOVER>
> port 1 priority 128
> Address cache (max cache: 100, timeout: 1200):
>
>> Christoph
>>
>
> # xm info
> host : nxd0
> release : 4.99.72
> version : NetBSD 4.99.72 (CUSTOM_XEN3_DOM0) #0: Thu Aug
> 21 15:54:16 BST 2008
> brad@nbsd64:/usr/obj/sys/arch/amd64/compile/CUSTOM_XEN3_DOM0
> machine : amd64
> nr_cpus : 1
> nr_nodes : 1
> cores_per_socket : 1
> threads_per_core : 1
> cpu_mhz : 1799
> hw_caps :
> 078bf3ff:e3d3fbff:00000000:00000010:00000001:00000001:00000001:00000000
> virt_caps :
> total_memory : 2046
> free_memory : 363
> node_to_cpu : node0:0
> node_to_memory : node0:363
> xen_major : 3
> xen_minor : 3
> xen_extra : .0
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : unavailable
> cc_compiler : gcc version 4.1.3 20080202 prerelease (NetBSD
> nb1 20080202)
> cc_compile_by : brad
> cc_compile_domain :
> cc_compile_date : Fri Aug 22 20:51:46 BST 2008
> xend_config_format : 4
> # xm list
> Name ID Mem VCPUs State
> Time(s)
> Domain-0 0 128 1 r----- 4318.1
> nxdu01 12 64 1 -b---- 495.4
> bldr-fbsd32 45 256 1 -b---- 10.9
> bldr-nbsd32 22 336 1 -b---- 1722.5
> bldr-nbsd64 21 336 1 -b---- 472.2
> nxdu02 20 80 1 -b---- 582.0
> nxdu03 15 80 1 -b---- 519.3
> nxdu04 16 80 1 -b---- 467.5
> nxdu05 13 64 1 -b---- 479.4
> nxdu06 14 64 1 -b---- 532.2
> nxdu07 18 80 1 -b---- 548.5
> nxdu08 19 80 1 -b---- 571.5
>
Can you show the output of xentop and the output from
'tail -f /var/log/xend.log | tee xend.failingdomain' ?
(To get some content into xend.failingdomain you need to launch
the failing guest to start.
Christoph
Home |
Main Index |
Thread Index |
Old Index