All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Scudeller <beto.rvs@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Problem with stubdom-dm and live migration in xen 4.0.1
Date: Thu, 14 Oct 2010 10:50:47 -0300	[thread overview]
Message-ID: <AANLkTimbjYziWbSXhoC17T=q-YdU6P38zTbR9vXYnCjz@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 917 bytes --]

Hi all,

I try using a VM with stubdom-dm instead qemu-dm, and "live migration" don't
work.

This command "xm migrate --live w2k3-ent.15 IP_Dom0_Destiny" works, in the
Dom0 destiny, created a paused VM (with memory but not a vcpus), but in the
end of process, not started appropriate and destroyed VM in both Dom0 Xen.
Look "xl list" below:


This description in "xl list", Dom0:

Name                                        ID   Mem VCPUs    State
Time(s)
w2k3-ent.15                                 29  4099     4        r--
545.1
w2k3-ent.15-dm                              30    32     1        r--
482.4

In Dom0_Destiny, during "xm migrate...":

Name                                        ID   Mem VCPUs    State
Time(s)
w2k3-ent.15                                  8  4099     1        -p-
0.0



I using xen 4.0.1 and a kernel 2.6.31.21.

Anybody help?

Sorry for my English terrible.

-- 
Roberto Scudeller

[-- Attachment #1.2: Type: text/html, Size: 1098 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

             reply	other threads:[~2010-10-14 13:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 13:50 Roberto Scudeller [this message]
2010-10-15 14:00 Problem with stubdom-dm and live migration in xen 4.0.1 Roberto Scudeller

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='AANLkTimbjYziWbSXhoC17T=q-YdU6P38zTbR9vXYnCjz@mail.gmail.com' \
    --to=beto.rvs@gmail.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.