xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Raman Bane <ramanbane@gmail.com>
Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org
Subject: Re: xm migrate working but vm not starting on destination
Date: Fri, 9 May 2014 22:46:13 +0200	[thread overview]
Message-ID: <20140509204613.GA18059@aepfle.de> (raw)
In-Reply-To: <CAA+LQLkNL7BvKfx0FftM9vGha2H87aQgLnTwP-1vM-FkYj3OCg@mail.gmail.com>

On Fri, May 09, Raman Bane wrote:

> xm migrate command executed without error but migrated vm not stating on
> destination.

[2014-04-28 19:19:05 4620] ERROR (XendCheckpoint:357) Device 51712 (vbd)
could not be connected. /dev/ramanbane2-vg/ubuntu2 does not exist.

Please fix.


Olaf

      reply	other threads:[~2014-05-09 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 17:19 xm migrate working but vm not starting on destination Raman Bane
2014-05-09 20:46 ` Olaf Hering [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=20140509204613.GA18059@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=ramanbane@gmail.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).