Re: [Xen-devel] domain reboots broken (and suspend too) -- resent

[Chris <hap10@xxxxxxxxxxxxxx>]

The xend patches that Alastair committed today appear to solve part of
the reboot issue.  However, the following case still causes problems:
 #> xm new <config>
 #> xm start <domname>
 #> xm reboot <domname>

During domU restart, xend.log shows that XendDomainInfo complains the
rebooted domU's name already exists:

File "XendDomainInfo.py", line 1033, in _restart
  new_dom = XendDomain.instance().domain_create(config)
File "XendDomain.py", line 819, in domain_create
  dominfo = XendDomainInfo.create(config)
File "XendDomainInfo.py", line 148, in create
  vm = XendDomainInfo(XendConfig(sxp = config))
File "XendDomainInfo.py", line 419, in __init__
  self._checkName(self.info['name'])
File "XendDomainInfo.py", line 1635, in _checkName
  raise VmError("VM name '%s' already exists" % name)

------------

Also, the patches did not improve suspend:

[Start Cut&Paste]

#> xm new <vmconfig>
#> xm start <vmconfig>
#> xm suspend <domname>
Error: Domain is not managed by Xend lifecycle support.
Usage: xm suspend <DomainName>

Suspend a Xend maanged domain

[End Cut&Paste]

See attached for a xend trace of the above suspend example in which the
domU's name is "fc5-1"

-Chris

xend-suspend.trace.gz
Description: GNU Zip compressed data

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