current xen-unstable fails to xm start <name>

current xen-unstable fails to xm start <name>

[Olaf Hering]

Hello,

current xen-unstable.hg-4.1.22019 fails to run 'xm start <name>', while
xen-unstable.hg-4.1.21976 was still ok.
Its not obvious from browsing the diff between the two trees whats the cause.
Any other info required besides the one pasted below?

# xm start $name
Error: 
Usage: xm start <DomainName>

Start a Xend managed domain
  -p, --paused                   Do not unpause domain after starting it    
  -c, --console_autoconnect      Connect to the console after the domain    
                                 is created
  --vncviewer                    Connect to display via VNC after the       
                                 domain is created
  --vncviewer-autopass           Pass VNC password to viewer via stdin and  
                                 -autopass


/var/log/xen/xend.log shows this. 
[2010-08-23 23:05:10 4672] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain
[2010-08-23 23:05:10 4672] DEBUG (balloon:187) Balloon: 153020 KiB free; need 16384; done.
[2010-08-23 23:05:10 4672] ERROR (XendDomainInfo:488) VM start failed
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 473, in start
    XendTask.log_progress(0, 30, self._constructDomain)
  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 2618, in _constructDomain
    assert type(weight) == int
AssertionError
[2010-08-23 23:05:10 4672] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: domid=6
[2010-08-23 23:05:10 4672] DEBUG (XendDomainInfo:2406) No device model
[2010-08-23 23:05:10 4672] DEBUG (XendDomainInfo:2408) Releasing devices
[2010-08-23 23:05:10 4672] ERROR (xmlrpclib2:178) Internal error handling xend.domain.start
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/util/xmlrpclib2.py", line 131, in _marshaled_dispatch
    response = self._dispatch(method, params)
  File "/usr/lib64/python2.6/SimpleXMLRPCServer.py", line 418, in _dispatch
    return func(*params)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 1070, in domain_start
    dominfo.start(is_managed = True)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 473, in start
    XendTask.log_progress(0, 30, self._constructDomain)
  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 2618, in _constructDomain
    assert type(weight) == int
AssertionError

Olaf

Re: current xen-unstable fails to xm start <name>

[Ian Campbell]

On Mon, 2010-08-23 at 22:13 +0100, Olaf Hering wrote:
> Hello,
> 
> current xen-unstable.hg-4.1.22019 fails to run 'xm start <name>', while
> xen-unstable.hg-4.1.21976 was still ok.
> Its not obvious from browsing the diff between the two trees whats the cause.

Given the assertion failure is "assert type(weight) == int"
22000:4fc66044477d looks a bit suspicious to me.

My guess would be that whatever writes cfg["vcpus_params"]["weight"]
before the patched code is writing something other than an int and that
this changeset means we no longer overwrite it with an int. I'm not
familiar enough with xend to say where that original write is happening
though.

Ian.


> Any other info required besides the one pasted below?
> 
> # xm start $name
> Error: 
> Usage: xm start <DomainName>
> 
> Start a Xend managed domain
>   -p, --paused                   Do not unpause domain after starting it    
>   -c, --console_autoconnect      Connect to the console after the domain    
>                                  is created
>   --vncviewer                    Connect to display via VNC after the       
>                                  domain is created
>   --vncviewer-autopass           Pass VNC password to viewer via stdin and  
>                                  -autopass
> 
> 
> /var/log/xen/xend.log shows this. 
> [2010-08-23 23:05:10 4672] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain
> [2010-08-23 23:05:10 4672] DEBUG (balloon:187) Balloon: 153020 KiB free; need 16384; done.
> [2010-08-23 23:05:10 4672] ERROR (XendDomainInfo:488) VM start failed
> Traceback (most recent call last):
>   File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 473, in start
>     XendTask.log_progress(0, 30, self._constructDomain)
>   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 2618, in _constructDomain
>     assert type(weight) == int
> AssertionError
> [2010-08-23 23:05:10 4672] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: domid=6
> [2010-08-23 23:05:10 4672] DEBUG (XendDomainInfo:2406) No device model
> [2010-08-23 23:05:10 4672] DEBUG (XendDomainInfo:2408) Releasing devices
> [2010-08-23 23:05:10 4672] ERROR (xmlrpclib2:178) Internal error handling xend.domain.start
> Traceback (most recent call last):
>   File "/usr/lib64/python2.6/site-packages/xen/util/xmlrpclib2.py", line 131, in _marshaled_dispatch
>     response = self._dispatch(method, params)
>   File "/usr/lib64/python2.6/SimpleXMLRPCServer.py", line 418, in _dispatch
>     return func(*params)
>   File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 1070, in domain_start
>     dominfo.start(is_managed = True)
>   File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 473, in start
>     XendTask.log_progress(0, 30, self._constructDomain)
>   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 2618, in _constructDomain
>     assert type(weight) == int
> AssertionError
> 
> Olaf
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel