current Xen3 (446aa56ca4fe) unable to reboot XenU ("cannot allocate memory")

current Xen3 (446aa56ca4fe) unable to reboot XenU ("cannot allocate memory")

[Charles Duffy]

Per subject. Funny thing is that this machine has *lots* of memory (it's 
a 16GB x86_64 system, dom0-min-mem is set to 256, and there's only one 
other domU running -- and that one is also limited to 64MB).

I can recreate the domain myself after it's shut down -- it's just that 
xend isn't restarting it as it should.

---

[2005-10-17 15:51:31 xend] INFO (XendDomainInfo:706) Domain has 
shutdown: name=labvpn id=5 reason=reboot.
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:1099) 
XendDomainInfo.destroy: domid=5
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:1107) 
XendDomainInfo.destroyDomain(5)
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:153) 
XendDomainInfo.create(['domain', ['domid', 5], ['uuid', 
'4f502834-dbcf-4165-af19-41a7491580ed'], ['memory', 64], ['name', 
'labvpn'], ['ssidref', 0], ['vcpus', 1], ['vcpu_avail', 1], 
['cpu_weight', 1.0], ['on_poweroff', 'destroy'], ['on_reboot', 
'restart'], ['on_crash', 'restart'], ['maxmem', 64], ['image', ['linux', 
['kernel', '/boot/vmlinuz-2.6.12-xenU'], ['root', '/dev/hda1 ro'], 
['args', 'init=/sbin/runit-init panic=5'], ['vcpus', '1'], ['vcpus', 
'1'], ['boot', 'c']]], ['device', ['vbd', ['uname', 'phy:data/labvpn'], 
['dev', 'hda1'], ['mode', 'w']]], ['device', ['vif', ['mac', 
'aa:00:00:95:e6:54'], ['bridge', 'xenbr1']]], ['state', '---s--'], 
['shutdown_reason', 'reboot'], ['cpu_time', 2.4210365070000002], 
['vcpus', 1], ['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]], ['cpu', 1], 
['vcpu_to_cpu', '1'], ['up_time', '47.3244888783'], ['start_time', 
'1129582243.8'], ['store_mfn', 294138], ['console_mfn', 294137]])
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:257) parseConfig: 
config is ['domain', ['domid', 5], ['uuid', 
'4f502834-dbcf-4165-af19-41a7491580ed'], ['memory', 64], ['name', 
'labvpn'], ['ssidref', 0], ['vcpus', 1], ['vcpu_avail', 1], 
['cpu_weight', 1.0], ['on_poweroff', 'destroy'], ['on_reboot', 
'restart'], ['on_crash', 'restart'], ['maxmem', 64], ['image', ['linux', 
['kernel', '/boot/vmlinuz-2.6.12-xenU'], ['root', '/dev/hda1 ro'], 
['args', 'init=/sbin/runit-init panic=5'], ['vcpus', '1'], ['vcpus', 
'1'], ['boot', 'c']]], ['device', ['vbd', ['uname', 'phy:data/labvpn'], 
['dev', 'hda1'], ['mode', 'w']]], ['device', ['vif', ['mac', 
'aa:00:00:95:e6:54'], ['bridge', 'xenbr1']]], ['state', '---s--'], 
['shutdown_reason', 'reboot'], ['cpu_time', 2.4210365070000002], 
['vcpus', 1], ['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]], ['cpu', 1], 
['vcpu_to_cpu', '1'], ['up_time', '47.3244888783'], ['start_time', 
'1129582243.8'], ['store_mfn', 294138], ['console_mfn', 294137]]
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:315) parseConfig: 
result is {'ssidref': 0, 'name': 'labvpn', 'on_reboot': 'restart', 
'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.12-xenU'], ['root', 
'/dev/hda1 ro'], ['args', 'init=/sbin/runit-init panic=5'], ['vcpus', 
'1'], ['vcpus', '1'], ['boot', 'c']], 'on_poweroff': 'destroy', 
'mem_kb': None, 'maxmem_kb': None, 'on_crash': 'restart', 'backend': [], 
'vcpus': 1, 'cpu_weight': 1.0, 'vcpu_avail': 1, 'memory': 64, 'device': 
[('vbd', ['vbd', ['uname', 'phy:data/labvpn'], ['dev', 'hda1'], ['mode', 
'w']]), ('vif', ['vif', ['mac', 'aa:00:00:95:e6:54'], ['bridge', 
'xenbr1']])], 'bootloader': None, 'cpu': 1, 'maxmem': 64}
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:1001) 
XendDomainInfo.construct: None 0
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:1020) 
XendDomainInfo.initDomain: 6 65536 1.0
[2005-10-17 15:51:31 xend] ERROR (XendDomainInfo:166) Domain 
construction failed
Traceback (most recent call last):
   File 
"/root/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", 
line 158, in create
   File 
"/root/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", 
line 1036, in initDomain
error: (12, 'Cannot allocate memory')
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:1099) 
XendDomainInfo.destroy: domid=6
[2005-10-17 15:51:31 xend] DEBUG (XendDomainInfo:1107) 
XendDomainInfo.destroyDomain(6)
[2005-10-17 15:51:31 xend] ERROR (XendDomainInfo:1258) Failed to restart 
domain 5.
Traceback (most recent call last):
   File 
"/root/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", 
line 1251, in restart
   File 
"/root/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDomain.py", 
line 205, in domain_create
   File 
"/root/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", 
line 158, in create
   File 
"/root/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", 
line 1036, in initDomain
error: (12, 'Cannot allocate memory')

[WORKAROUND] Re: current Xen3 (446aa56ca4fe) unable to reboot XenU ("cannot allocate memory")

[Charles Duffy]

Setting dom0_mem such that it's not necessary to balloon out on the 
restart appears to work around this issue, such that the DomU is 
successfully restarted by xend.