From: Michael Paesold <mpaesold@gmx.at>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Michael Mey <michael.mey@to.com>
Subject: Re: live migration with DRBD devices
Date: Tue, 25 Oct 2005 19:46:39 +0200 [thread overview]
Message-ID: <435E6F7F.4030308@gmx.at> (raw)
In-Reply-To: <200510251549.06207.mark.williamson@cl.cam.ac.uk>
Mark Williamson wrote:
>>I want to do live migration of domains using DRBD block devices for
>>synchronisation between the two Xen hosts with Xen 2.0.7.
>>
>>I've written a script ( block-drbd ) which binds / unbinds DRBD devices for
>>specific domains (with DRBD, only one host can write on a drbd device at
>>the same time). This script sets the current host as master (bind) or
>>secondary (unbind) in a DRBD "Netword-RAID"
>
>
> Yep - btw this is fixed with DRBD 8 (still in development), which supports
> multiple writers.
>
> How are you handling the sequencing here, though? Move the device to the new
> host at *unbind* time from the origin? I'm thinking that the DRBD script
> will get run at the destination whilst the origin domain is still running and
> using its disk...
Correct.
And it cannot work with drbd 0.7 currently without hacking Xen to change
block device setup. What would be needed is that Xen should open the new
block device read-only (there is a hack in drbd 0.7 that would allow
this) and only when the source domain is shutdown reopen the block
device r/w.
Xen want's to open the block device rw as soon as it does the setup of
the destination domain. This may work currectly with drbd 0.8 since it
supports multi-master.
I have done testing with the current development trunk of drbd some time
ago. It did not work for me. Migration crashed the guest.
Best Regards,
Michael Paesold
next prev parent reply other threads:[~2005-10-25 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 12:48 live migration with DRBD devices Michael Mey
2005-10-25 14:49 ` Mark Williamson
2005-10-25 17:46 ` Michael Paesold [this message]
2005-10-27 9:39 ` Michael Mey
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=435E6F7F.4030308@gmx.at \
--to=mpaesold@gmx.at \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=michael.mey@to.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.