From: Jacob Gorm Hansen <jacobg@diku.dk>
To: andrew.warfield@cl.cam.ac.uk
Cc: Eric Tessler <maiden1134@yahoo.com>, xen-devel@lists.sourceforge.net
Subject: Re: XEN migration architecture question
Date: Thu, 20 Jan 2005 13:56:45 -0800 [thread overview]
Message-ID: <41F0291D.8080307@diku.dk> (raw)
In-Reply-To: <eacc82a4050120131611654b50@mail.gmail.com>
One thing I found fairly easy to setup for self-migration, was to use
software RAID-1 (mirroring) to iSCSI targets on the original and
destination hosts. When its time to migrate, I add the remote iSCSI disk
to the RAID-1 array, and when that has synced up 100%, I self-migrate
there. You can either run your iSCSI (or GNBD haven't tried that)
targets in dom0, or you can run them in separate domUs (in my
implementation, you will first fire off a bootstrap of a small
iSCSI-server domain to the remote host, as my dom0 is not allowed to
include dangerous stuff such as a TPC/IP stack and an iSCSI server).
That gives me live disk-migration using a simple shell-script.
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-20 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 20:44 XEN migration architecture question Eric Tessler
2005-01-20 21:10 ` Mark Williamson
2005-01-20 21:16 ` Andrew Warfield
2005-01-20 21:56 ` Jacob Gorm Hansen [this message]
2005-01-20 23:28 ` B.G. Bruce
2005-01-20 23:47 ` Jacob Gorm Hansen
-- strict thread matches above, loose matches on Subject: below --
2005-01-20 22:11 Ian Pratt
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=41F0291D.8080307@diku.dk \
--to=jacobg@diku.dk \
--cc=andrew.warfield@cl.cam.ac.uk \
--cc=maiden1134@yahoo.com \
--cc=xen-devel@lists.sourceforge.net \
/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.