Re: [Xen-users] xm create - Xend has probably crashed! Invalid or missing HTTP status code.

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

Hi there,

> > Anything interesting in /var/log/xen/xend.log or /var/log/xen/xend-
> > debug.log?
>
>     /var/log/xen/xend.log
>     Near the top:
> *    (Its recreating some domain)*
>     [2007-12-02 17:37:05 6495] DEBUG (XendDomainInfo:126)
> XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 141296484314L,
> 'ssidref': 65537, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0,
> 'online_vcpus': 1, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1,
> 'maxmem_kb': 1048576L, 'shutdown': 0, 'mem_kb': 954796L, 'handle': [0, 0,
> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name':
> 'Domain-0'}) [2007-12-02 17:37:05 6495] INFO (XendDomainInfo:143)
> Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at
> /local/domain/0
>    .....
>    .....


Is this next bit where you create your new domain?

>
> > [2007-12-02 17:37:32 6495] DEBUG (XendDomainInfo:1517)
> > XendDomainInfo.initDomain: 17 256
> > [2007-12-02 17:37:32 6495] DEBUG (XendDomainInfo:1549)
> > _initDomain:shadow_memory=0x0, memory_static_max=0x40000000,
> > memory_static_min=0x0.
> > [2007-12-02 17:37:32 6494] CRITICAL (SrvDaemon:231) *Xend died due to
> > signal 11!*  Restarting it[2007-12-02 17:37:32 6530] INFO (SrvDaemon:331)
> > Xend Daemon started

OK.

The fact that Xend died here due to Signal 11 (segfault) is quite worrying in 
itself.  It juggests that some kind of bug has just happened...  weird.

I guess that suggests that whatever bit you skipped above might have had 
something to do with it.  Sorry, it's not the direct cause of the error 
you're seeing, so I understand why you skipped it.  But I suspect it has 
something to do with the root cause.

>
>    *(The same recreation doesnt work below)*
>
> > [2007-12-02 17:37:32 6530] INFO (SrvDaemon:335) Xend changeset: Thu Nov
> > 29 19:30:33 2007 +0000 16491:3057f813da14.
> > [2007-12-02 17:37:32 6530] INFO (SrvDaemon:342) Xend version: Unknown.
> > [2007-12-02 17:37:32 6530] DEBUG (XendDomainInfo:126)
> > XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 142499085675L,
> > 'ssidref': 65537, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0,
> > 'online_vcpus': 1, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1,
> > 'maxmem_kb': 1048576L, 'shutdown': 0, 'mem_kb': 954796L, 'handle': [0, 0,
> > 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name':
> > 'Domain-0'}) [2007-12-02 17:37:32 6530] INFO (XendDomainInfo:143)
> > Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at
> > /local/domain/0
> > [2007-12-02 17:37:32 6530] DEBUG (XendDomain:443) Adding Domain: 0
> > [2007-12-02 17:37:32 6530] DEBUG (XendDomainInfo:873) Storing domain
> > details: {'name': 'Domain-0', 'console/limit': '1048576', 'vm':
> > '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
> > 'cpu/0/availability': 'online', 'memory/target': '954796',
> > 'control/platform-feature-multiprocessor-suspend': '1'}
> > [2007-12-02 17:37:32 6530] DEBUG (XendDomainInfo:957)
> > XendDomainInfo.handleShutdownWatch
> > [2007-12-02 17:37:32 6530] DEBUG (XendDomain:379) number of vcpus to use
> > is 0
> > [2007-12-02 17:37:32 6530] DEBUG (XendDomainInfo:126)
> > XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 0L, 'ssidref': 0,
> > 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 0, 'domid':
> > 17, 'paused': 1, 'crashed': 0, 'running': 0, 'maxmem_kb': 1048576L,
> > 'shutdown': 0, 'mem_kb': 0L, 'handle': [247, 236, 220, 56, 215, 217, 181,
> > 31, 227, 57, 251, 99, 222, 118, 127, 58], 'blocked': 1})
> > [2007-12-02 17:37:32 6530] ERROR (XendDomain:178) Failed to create
> > reference to running domain id: 17
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line
> > 175, in _init_domains
> >     new_dom = XendDomainInfo.recreate(dom, False)
> >   File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> > line 130, in recreate
> >     xeninfo = XendConfig.XendConfig(dominfo = info)
> >   File "/usr/lib/python2.5/site-packages/xen/xend/XendConfig.py", line
> > 275, in __init__
> >     self._dominfo_to_xapi(dominfo, update_mem = True)
> >   File "/usr/lib/python2.5/site-packages/xen/xend/XendConfig.py", line
> > 420, in _dominfo_to_xapi
> >     self._memory_sanity_check()
> >   File "/usr/lib/python2.5/site-packages/xen/xend/XendConfig.py", line
> > 365, in _memory_sanity_check
> >     raise XendConfigError("memory_dynamic_max must be greater " \
> > XendConfigError: *Invalid Configuration: memory_dynamic_max must be
> > greater than zero

For some reason, maxmem_kb is 0 in the domain it's trying to recreate, so it 
seems not to have any memory.  It also says the domain is paused...  Perhaps 
Xend crashed with signal 11 part way through creating a domain for you - is 
that a possibility?

Xend seems to have got itself into a funny state, possibly due to the earlier 
crash.  Ideally, it should probably handle this sort of thing better, though.

Are you still having this problem?  Have you tried updating your pull of 
xen-unstable?

And in your setup, have you enabled any particular security policy at all?  
I'm afraid I don't understand the security policies very well, so this is 
slightly unfamiliar territory for me.

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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