Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

[Li Ge <lge@xxxxxxxxxx>]

Here are some more information :

1. Yes. The problem is reproducible. But the weird thing is if I start xend using" xend trace_start", the problem goes away and I can get the new domain created. I've tried both "xend start" and "xend trace_start" a couple of times. It always works with "xend trace_start" but not with "xend start".
2. The domain config file: (See attached file: xen-sarge.config)
3: /var/log/xend.log file: (See attached file: xend.log)
4. The /var/log/xend.trace file is quite big (2+MB), so I am not putting it here. If you still think it might help, I can send it to you.


Thanks,
Li Ge

Linux Technology Center, IBM


Mike Wray <mike.wray@xxxxxx>

Mike Wray <mike.wray@xxxxxx>
Sent by: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

05/16/2005 03:29 PM

To	Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
cc	Li Ge/Austin/IBM@IBMUS, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject	Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

Ian Pratt wrote:
>  
> Mike, please can you take a look at this.
> Thanks,
> Ian
> 
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Li Ge
> Sent: 16 May 2005 20:16
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Creating domain crashes xend with the latest
> xenunstable tree
> 
> I was able to build and boot Xen using May 16 unstable tree. But the
> xend crashes when I create new domain on Fedora Core 3:

See comments below. Will need more info to diagnose this.

> [root@bl3-2 ~]# xm create /images/xen-sarge/xen-sarge.config -c Using
> config file "/images/xen-sarge/xen-sarge.config".
> Traceback (most recent call last):
> File "/usr/sbin/xm", line 10, in ?
> main.main(sys.argv)
> File "/usr/lib/python/xen/xm/main.py", line 901, in main
> xm.main(args)
> File "/usr/lib/python/xen/xm/main.py", line 133, in main
> self.main_call(args)
> File "/usr/lib/python/xen/xm/main.py", line 151, in main_call
> p.main(args[1:])
> File "/usr/lib/python/xen/xm/main.py", line 286, in main
> create.main(args)
> File "/usr/lib/python/xen/xm/create.py", line 623, in main (dom,
> console) = make_domain(opts, config) File
> "/usr/lib/python/xen/xm/create.py", line 578, in make_domain dominfo =
> server.xend_domain_create(config) File
> "/usr/lib/python/xen/xend/XendClient.py", line 192, in
> xend_domain_create {'op' : 'create', File
> "/usr/lib/python/xen/xend/XendClient.py", line 141, in xendPost return
> self.client.xendPost(url, data) File
> "/usr/lib/python/xen/xend/XendProtocol.py", line 80, in xendPost return
> self.xendRequest(url, "POST", args) File
> "/usr/lib/python/xen/xend/XendProtocol.py", line 151, in xendRequest
> resp = conn.getresponse() File "/usr/lib/python2.3/httplib.py", line
> 778, in getresponse
> response.begin()
> File "/usr/lib/python2.3/httplib.py", line 273, in begin version,
> status, reason = self._read_status() File
> "/usr/lib/python2.3/httplib.py", line 237, in _read_status raise
> BadStatusLine(line) httplib.BadStatusLine
> [root@bl3-2 ~]# ps -ef|grep xend
> root 3833 1 0 13:33 ? 00:00:00 python /usr/sbin/xend start root 3834
> 3833 0 13:33 ? 00:00:00 python /usr/sbin/xend start root 3835 3834 0
> 13:33 ? 00:00:00 python /usr/sbin/xend start root 3836 3834 0 13:33 ?
> 00:00:00 python /usr/sbin/xend start root 4523 3834 0 13:35 ? 00:00:00
> python /usr/sbin/xend start root 4525 4478 0 13:35 ttyS0 00:00:00 grep
> xend
> [root@bl3-2 ~]# xm list
> (111, 'Connection refused')
> Error: Error connecting to xend, is xend running?
> [root@bl3-2 ~]# xend start
> 4547 [DBG] XFRD>main>
> 4547 [DBG] XFRD>xfrd_main>
> 4547 [DBG] XFRD>xfrd_listen_socket>
> 4547 [DBG] XFRD>create_socket>
> 4547 [DBG] XFRD>create_socket> port=8002
> 4547 [DBG] XFRD>create_socket< err=0
> 4547 [DBG] XFRD>xfrd_listen_socket> listen...
> 4547 [DBG] XFRD>xfrd_listen_socket< err=0
> 4547 [DBG] XFRD>xfrd_select> socks: 3
> [xend] INFO (__init__:988) Xend Daemon started [xend] INFO
> (__init__:988) Virq 0 on port 3 [xend] INFO (__init__:988) Virq 1 on
> port 6 [xend] INFO (__init__:988) Virq 2 on port 5 [xend] INFO
> (__init__:988) Virq 3 on port 10 [xend] INFO (__init__:988) Virq 4 on
> port 11 vm_recreate> savedinfo= (domain (id 0) (name Domain-0) (memory
> 495)) info= {'vcpu_to_cpu': [0, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
> -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
> -1, -1, -1], 'cpu_time': 28740382934L,
> 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'running': 1, 'maxmem_kb':
> -4096,
> 'paused': 0, 'crashed': 0, 'vcpus': 1, 'shutdown': 0, 'mem_kb': 506952,
> 'cpumap': [-1,
> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0, 0], 'blocked': 0} 


The stuff below here shows that xend found domain-1 in the list from xc,
but had no saved info for it. So showing 2 domains in the xm list is correct.
Something bad probably happened during domain create though.

Need to see the config used for the domain and the output from /var/log/xend.log.
If the problem is reproducible then starting 'xend trace_start'
and posting /var/log/xend.trace would also help.

> [xend] INFO (__init__:988) Creating
> entry for unknown domain: id=1 vm_recreate> savedinfo= 'None'
> info= {'vcpu_to_cpu': [3, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
> -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
> -1, -1], 'cpu_time': 0L, 'shutdown_reason': 0,
> 'dying': 0, 'dom': 1, 'running': 0, 'maxmem_kb': 268435456, 'paused': 1,

               ^^^^^^^^^^

> 'crashed': 0, 'vcpus': 1, 'shutdown': 0, 'mem_kb': 262144, 'cpumap':
> [-1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0} unix path=
> /var/lib/xend/xend-socket network start bridge=xen-br0 netdev=eth1
> antispoof=no [xend] INFO (__init__:988) EVENT> xend.domain.create
> ['Domain-1', '1'] [xend] INFO (__init__:988) EVENT> xend.start 0
> [root@bl3-2 ~]# xm list
> Name Id Mem(MB) CPU VCPU(s) State Time(s) Console Domain-0 0 495 0 1
> r---- 29.6
> Domain-1 1 256 3 1 --p-- 0.0
> 
> Another problem I see here is just after I restarted xend, it showed
> there were
> two domains (Domain-0 and Domain-1) in the list which should be only one
> (Domain-0).		 
> 
> 
> Thanks,
> 
> Li Ge
> 
> Linux Technology Center, IBM

Mike

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

xen-sarge.config
Description: Binary data

xend.log
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel