All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor@qumranet.com>
To: Kent Borg <kentborg@borg.org>
Cc: kvm@vger.kernel.org
Subject: Re: Live Migration, DRBD
Date: Fri, 25 Jul 2008 02:02:55 +0300	[thread overview]
Message-ID: <48890A1F.4010404@qumranet.com> (raw)
In-Reply-To: <4888C5E9.2050606@borg.org>

Kent Borg wrote:
> I am very happy to discover that KVM does live migration.  Now I am
> figuring out whether it will work for me. 
>
> What I have in mind is to use DRBD for the file system image.  The
> problem is that during the migration I want to shift the file system
> access at the moment when the VM has quit running on the host it is
> leaving but before it starts running on the host where it is arriving. 
> Is there a hook to let me do stuff at this point?
>
> This is what I want to do:
>
> On the departing machine...
>
>   - VM has stopped here
>   - umount the volume with the VM file system image
>   - mark volume in DRDB as secondary
>
>
> On the arriving machine...
>
>   - mark volume in DRBD as primary
>   - mount the volume with the VM file system image
>   - VM can now start here
>
>
> Is there a way?
>
>   
No, but one can add such pretty easy. The whole migration code is in one 
file qemu/migration.c
You can add a parameter to qemu migration command to specify a script 
that should be called on
migration end event (similar to the tap script).
> Thanks,
>
> -kb
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  reply	other threads:[~2008-07-24 23:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 18:11 Live Migration, DRBD Kent Borg
2008-07-24 23:02 ` Dor Laor [this message]
2008-07-25  2:41 ` Jim
2008-07-25 13:37   ` Kent Borg

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=48890A1F.4010404@qumranet.com \
    --to=dor.laor@qumranet.com \
    --cc=kentborg@borg.org \
    --cc=kvm@vger.kernel.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 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.