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/
Home Products Support Community News


[Xen-bugs] [Bug 936] New: An unstarted domain is not registered

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 936] New: An unstarted domain is not registered
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 23 Mar 2007 04:39:05 -0700
Delivery-date: Fri, 23 Mar 2007 04:39:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: An unstarted domain is not registered
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: kanno.masaki@xxxxxxxxxxxxxx

I tried the following operations with xen-unstable:cs14488.
 1. xm new command
 2. xend stop command
 3. xend start command.

The result was as follows. And I saw the following Traceback 
message in the xend.log.
FYI, if there is not the cpus parameter in the domain 
configuration file, the unstarted domain is registered.

# xm new /xen/vm1.conf 
Using config file "/xen/vm1.conf".
# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0   512     2     r-----     65.9
vm1                                            256     2                 0.0
# xend stop
# xend start
# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0   512     2     r-----     69.8

[2007-03-23 19:20:03 5405] ERROR (XendDomain:331) Unable to open or parse
Traceback (most recent call last):
  File "//usr/lib/python/xen/xend/XendDomain.py", line 323, in _managed_domains
    cfg = XendConfig.XendConfig(filename = cfg_file)
  File "//usr/lib/python/xen/xend/XendConfig.py", line 266, in __init__
  File "//usr/lib/python/xen/xend/XendConfig.py", line 626, in _sxp_to_xapi
    cfg = self._parse_sxp(sxp_cfg)
  File "//usr/lib/python/xen/xend/XendConfig.py", line 607, in _parse_sxp
    raise XendConfigError(\047cpus = %s: %s\047 % (cfg[\047cpus\047], e))
XendConfigError: Invalid Configuration: cpus = [1]: invalid literal for int():

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 936] New: An unstarted domain is not registered, bugzilla-daemon <=