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-bugs

[Xen-bugs] [Bug 226] New: Misleading error message

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=226

           Summary: Misleading error message
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: treed-bugzilla@xxxxxxxxxxxxxxx


While configuring xen-unstable (source distro downloaded and compiled on Sep 13)
on my P4 with 512M of RAM running CentOS 4.1 as both host and guest OS's I ran
into an interesting problem which I consider a bug. My machine has 512M of RAM
and I had dom0 configured to use 256 so I thought it would be ok to configure a
domU to use 256 also, not taking into account overhead. It too me longer to
figure out this problem than it should have because the error message upon
trying to start the domain was very misleading:

[root@localhost xen]# xm create /etc/xen/mail.conf
Using config file "/etc/xen/mail.conf".
Error: Error creating domain: (2, 'No such file or directory')

Being new to xen I was not aware of the logfiles in /var/log but once someone on
IRC turned me onto them I found the following:

[root@localhost xen]# cat /var/log/xend-debug.log
Failed alocation for dom 28 : 65536 pages order 0 addr_bits 0
Traceback (most recent call last):
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 636, in construct
    self.init_domain()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 818, in init_domain
    id = self.image.initDomain(self.id, self.memory, self.ssidref, cpu,
self.cpu_weight)
  File "/usr/lib/python/xen/xend/image.py", line 167, in initDomain
    xc.domain_memory_increase_reservation(dom, mem_kb-lmem_kb, 0, 0)
error: (12, 'Cannot allocate memory')
Traceback (most recent call last):
  File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 78, in op_create
   dominfo = self.xd.domain_create(config)
  File "/usr/lib/python/xen/xend/XendDomain.py", line 293, in domain_create
    dominfo = XendDomainInfo.create(self.dbmap, config)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 162, in create
    vm.construct(config)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 651, in construct
    self.destroy()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 774, in destroy
    self.cleanup()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 743, in cleanup
    self.release_devices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 791, in 
release_devices
    for d in t.list("vbd"):
  File "/usr/lib/python/xen/xend/xenstore/xstransact.py", line 110, in list
    ret.extend(self._list(key))
  File "/usr/lib/python/xen/xend/xenstore/xstransact.py", line 103, in _list
    return map(lambda x: key + "/" + x, xshandle().ls(path))
RuntimeError: (2, 'No such file or directory')
[root@localhost xen]#

Towards the top of the traceback is the memory allocation error followed by a
"No such file or directory" error. I think xen should give a more reasonable
error message which describes the real problem.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 226] New: Misleading error message, bugzilla-daemon <=