All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: current xen-unstable fails to xm start <name>
Date: Mon, 23 Aug 2010 22:40:49 +0100	[thread overview]
Message-ID: <1282599649.5417.67.camel@localhost.localdomain> (raw)
In-Reply-To: <20100823211359.GA25636@aepfle.de>

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

      reply	other threads:[~2010-08-23 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 21:13 current xen-unstable fails to xm start <name> Olaf Hering
2010-08-23 21:40 ` Ian Campbell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1282599649.5417.67.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.