All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: domU reboot failure
Date: Wed, 21 Mar 2007 15:08:32 -0600	[thread overview]
Message-ID: <1174511312.5747.5.camel@lappy> (raw)


   FYI, latest unstable tip (14462) fails to reboot pv domains (issuing
reboot from within the domain).  Xend.log shows the following:

[2007-03-21 14:54:26 3097] DEBUG (__init__:1072) features       = 
[2007-03-21 14:54:26 3097] ERROR (__init__:1072) XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
  File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 1499, in _initDomain
    channel_details = self.image.createImage()
  File "//usr/lib64/python/xen/xend/image.py", line 112, in createImage
    return self.createDomain()
  File "//usr/lib64/python/xen/xend/image.py", line 131, in createDomain
    result = self.buildDomain()
  File "//usr/lib64/python/xen/xend/image.py", line 611, in buildDomain
    return LinuxImageHandler.buildDomain(self)
  File "//usr/lib64/python/xen/xend/image.py", line 215, in buildDomain
    features       = self.vm.getFeatures())
Error: (11, 'Resource temporarily unavailable')
[2007-03-21 14:54:26 3097] ERROR (__init__:1072) VM start failed
...

Seeing this both on ia64 and x86_64 (didn't test x86_32).  Domain was
started with 'xm create'.  The breakage seems to have occurred within
the last ~50 csets.  Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.

             reply	other threads:[~2007-03-21 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 21:08 Alex Williamson [this message]
2007-03-22 15:59 ` domU reboot failure Al Stone
2007-03-22 17:08   ` Ewan Mellor

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=1174511312.5747.5.camel@lappy \
    --to=alex.williamson@hp.com \
    --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.