xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* Bug - DomUs failing to restart - issue with maxmem_mb set to 0
@ 2012-06-08 13:48 Anthony Wright
  0 siblings, 0 replies; only message in thread
From: Anthony Wright @ 2012-06-08 13:48 UTC (permalink / raw)
  To: xen-devel@lists.xensource.com

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

I have a process that monitors DomU's, and when they shutdown it spots
it and restarts the DomU.

If I restart them immediately very frequently I get an internal error,
and the DomU fails to start. If I add a 2 second sleep before restarting
the DomU, it restarts nicely. If I restart the DomU after it has failed
to start once, it will restart nicely. The xen config for all the DomUs
is identical.

I notice that in xend.log, when a DomU fails to restart the
XendDomainInfo.recreate parameters online_vcpus, maxmem_mb and mem_kb
are all set to 0. When the DomU starts correctly these parameters have
sensible values.

I'm running Xen 4.1.2 with kernel 3.3.2 all in 32 bit mode.

I'm attaching the output from xl create and the sections from xend.log.

Anthony.

[-- Attachment #2: xl-create.log --]
[-- Type: text/plain, Size: 461 bytes --]

xc: error: do_evtchn_op: HYPERVISOR_event_channel_op failed: -1: Internal error
xc: error: do_evtchn_op: HYPERVISOR_event_channel_op failed: -1: Internal error
xc: error: panic: xc_dom_boot.c:159: xc_dom_boot_mem_init: can't allocate low memory for domain: Out of memory
libxl: error: libxl_dom.c:204:libxl__build_pv xc_dom_boot_mem_init failed: No such process
cannot (re-)build domain: -3
libxl: error: libxl.c:711:libxl_domain_destroy non-existant domain 29

[-- Attachment #3: xend.log --]
[-- Type: text/plain, Size: 2904 bytes --]

[2012-06-08 14:20:38 676] DEBUG (XendDomainInfo:151) XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 0L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 0, 'domid': 29, 'paused': 1, 'crashed': 0, 'running': 0, 'maxmem_kb': 0L, 'shutdown': 0, 'mem_kb': 0L, 'handle': [241, 186, 174, 38, 56, 252, 73, 149, 174, 115, 115, 95, 251, 69, 33, 189], 'blocked': 0, 'cpupool': 0})                                       
[2012-06-08 14:20:38 676] ERROR (XendDomain:447) Unable to recreate domain                                     
Traceback (most recent call last):                                                                             
  File "usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 445, in _refreshTxn                      
    new_dom = XendDomainInfo.recreate(dom, False)                                                              
  File "usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 155, in recreate
    xeninfo = XendConfig.XendConfig(dominfo = info)
  File "usr/lib/python2.4/site-packages/xen/xend/XendConfig.py", line 360, in __init__
    self._dominfo_to_xapi(dominfo, update_mem = True)
  File "usr/lib/python2.4/site-packages/xen/xend/XendConfig.py", line 574, in _dominfo_to_xapi
    self._memory_sanity_check()
  File "usr/lib/python2.4/site-packages/xen/xend/XendConfig.py", line 455, in _memory_sanity_check
    raise XendConfigError("memory_dynamic_max must be greater " \
XendConfigError: Invalid Configuration: memory_dynamic_max must be greater than zero
[2012-06-08 14:20:38 676] ERROR (XendDomainInfo:3085) XendDomainInfo.destroy: domain destruction failed.
Traceback (most recent call last):
  File "usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 3078, in destroy
    xc.domain_pause(self.domid)
Error: (3, 'No such process')
[2012-06-08 14:20:38 676] DEBUG (XendDomainInfo:2401) Destroying device model
[2012-06-08 14:20:38 676] DEBUG (XendDomainInfo:2408) Releasing devices
[2012-06-08 14:20:38 676] DEBUG (XendDomainInfo:2414) Removing console/0
[2012-06-08 14:20:38 676] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2012-06-08 14:20:54 676] DEBUG (XendDomainInfo:151) XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 0L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 1, 'domid': 30, 'paused': 1, 'crashed': 0, 'running': 0, 'maxmem_kb': 132096L, 'shutdown': 0, 'mem_kb': 131072L, 'handle': [237, 80, 222, 13, 176, 6, 68, 29, 142, 126, 214, 197, 194, 221, 142, 25], 'blocked': 0, 'cpupool': 0})
[2012-06-08 14:20:54 676] INFO (XendDomainInfo:168) Recreating domain 30, UUID ed50de0d-b006-441d-8e7e-d6c5c2dd8e19. at /local/domain/30
[2012-06-08 14:21:01 676] DEBUG (XendDomain:476) Adding Domain: 30
[2012-06-08 14:21:02 676] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2012-06-08 13:48 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-06-08 13:48 Bug - DomUs failing to restart - issue with maxmem_mb set to 0 Anthony Wright

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).