WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Memory problems persist... Cannot allocate memory

On Thu, Dec 31, 2009 at 01:44:30PM -0500, James Pifer wrote:
> > Looks like you don't have dom0 ballooning enabled, so then dom0 should
> > always have the dedicated 2048 MB of memory.
> > 
> > What was the error you got? check dom0 "dmesg", "xm dmesg" and "xm log"
> > when creating 15/16+ guests..
> > 
> > -- Pasi
> 
> Here's what I get in the log when I try to start a domain right now:
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:2757) 
> XendDomainInfo.destroy: domid=40
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:2227) Destroying device model
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:2234) Releasing devices
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:2247) Removing vif/0
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:1137) 
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:2247) Removing vkbd/0
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:1137) 
> XendDomainInfo.destroyDevice: deviceClass = vkbd, device = vkbd/0
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:2247) Removing console/0
> [2009-12-31 11:42:19 5611] DEBUG (XendDomainInfo:1137) 
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> [2009-12-31 11:42:22 5611] DEBUG (XendDomainInfo:2247) Removing vbd/768
> [2009-12-31 11:42:22 5611] DEBUG (XendDomainInfo:1137) 
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2009-12-31 11:42:22 5611] DEBUG (XendDomainInfo:2247) Removing vbd/832
> [2009-12-31 11:42:22 5611] DEBUG (XendDomainInfo:1137) 
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/832
> [2009-12-31 11:42:23 5611] DEBUG (XendDomainInfo:2247) Removing vfb/0
> [2009-12-31 11:42:23 5611] DEBUG (XendDomainInfo:1137) 
> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> [2009-12-31 11:42:23 5611] ERROR (SrvBase:88) Request start failed.
> Traceback (most recent call last):
>   File "/usr/lib64/python2.6/site-packages/xen/web/SrvBase.py", line 85, in 
> perform
>     return op_method(op, req)
>   File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDomain.py", 
> line 77, in op_start
>     return self.xd.domain_start(self.dom.getName(), paused)
>   File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 
> 1040, in domain_start
>     dominfo.start(is_managed = True)
>   File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 
> 459, in start
>     XendTask.log_progress(31, 60, self._initDomain)
>   File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, 
> in log_progress
>     retval = func(*args, **kwds)
>   File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 
> 2594, in _initDomain
>     self._createDevices()
>   File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 
> 2218, in _createDevices
>     self.image.createDeviceModel()
>   File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 419, in 
> createDeviceModel
>     pid = os.fork()
> OSError: [Errno 12] Cannot allocate memory
> 

So what does "xm info" say about free memory? How much does the guest
you're trying to start have memory configured for it? 

-- Pasi


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