All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Sardo <sandro.sardo@polito.it>
To: xen-devel@lists.xensource.com
Subject: Migration of paused domains
Date: Sat, 19 Jul 2008 14:33:48 +0200	[thread overview]
Message-ID: <4881DF2C.4080806@polito.it> (raw)

Hello,

today I wanted to find out if it was possible to migrate a paused 
domain. So, I tried the following:

# xm pause <dom>
# xm migrate <dom> <dest>

Unfortunately, the migration process would just hang before suspending 
the domain and transferring its state. In order to resume it and 
complete migration, I had to unpause the domain:

# xm unpause <dom>

After that, the process did get completed successfully.

-----

Then, I tried and track down the reason of this in the sources, and I 
came to the following snip (XendDomainInfo.py):

def waitForShutdown(self):
      self.state_updated.acquire()
           try:
                while self._stateGet() in 
(DOM_STATE_RUNNING,DOM_STATE_PAUSED):
                self.state_updated.wait()
           finally:
                self.state_updated.release()

It looks like that makes it wait forever, since the domain remains stuck 
in the DOM_STATE_PAUSED state.

Now, the question is: is that the right behaviour or am I missing 
something? Is it really not possible to migrate a paused domain?

Thanks,

- AS

             reply	other threads:[~2008-07-19 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19 12:33 Alessandro Sardo [this message]
2008-07-19 12:37 ` Migration of paused domains James Harper
2008-07-19 12:46   ` Alessandro Sardo
2008-07-19 15:51     ` Mark Williamson
  -- strict thread matches above, loose matches on Subject: below --
2006-08-03 13:13 Rob Bradford
2006-08-03 13:25 ` Steven Hand
2006-08-03 17:42   ` Jayesh Salvi

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=4881DF2C.4080806@polito.it \
    --to=sandro.sardo@polito.it \
    --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.