All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: Brendan Cully <brendan@cs.ubc.ca>,
	james.harper@bendigoit.com.au,
	Andrew Warfield <Andrew.Warfield@citrix.com>,
	ospk-vm@lab.ntt.co.jp
Subject: [RFC][PATCH] Kemari v1.0 released
Date: Tue, 25 Nov 2008 14:04:32 +0900	[thread overview]
Message-ID: <492B8760.2000100@lab.ntt.co.jp> (raw)

Hi,

I would like to announce the first release of Kemari, an open-source
virtual machine synchronization mechanism for fault tolerance.
It offers a feasible approach to fault tolerance that does not
require the use of specific hardware or modification of applications/OS.
Kemari aims to keep VMs transparently running in times of hardware
failures. It transfers the state of the primary VM to the secondary
VM when the primary VM is about to send an event to devices such as
storage and networks. The source code and further information are
available at the following site.

http://www.osrg.net/kemari/

Older slides and video are also available at,

http://www.xen.org/community/projects.html

In addition to Linux with PV Drivers, we tested Windows with James
Harpers's GPL PV. The video
(http://www.osrg.net/kemari/download/kemari_windows.mov) demonstrates
that Windows continued transparently when power failure occurred to the
primary server.

Kemari is now listed on Xen Product Roadmap,
(http://www.xen.org/download/roadmap.html)
and we would like to ask for your reviews and comments.
Briefly, Kemari in VMM taps event channel, pauses the guest (not
suspend), prepares for transfer, and Kemari in userland transfers
the guest. On failover, Kemari on the secondary restores the guest,
and the backend drivers in dom0 set up the backend rings from the
state of the shared rings in the guest.

Could you please review the code? Any comments are appreciated.

We're also planning to merge with Remus from UBC to propose a better
solution for Xen 3.4 together.

Thanks,

Yoshi

-- 
TAMURA, Yoshiaki

NTT Cyber Space Labs
OSS Computing Project
Kernel Group
E-mail: tamura.yoshiaki@lab.ntt.co.jp
TEL: +81-46-859-2771
FAX: +81-46-855-1152
Address: 1-1 Hikarinooka, Yokosuka
	 Kanagawa 239-0847 JAPAN

             reply	other threads:[~2008-11-25  5:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  5:04 Yoshiaki Tamura [this message]
2009-03-02 13:30 ` Design document of Kemari Yoshiaki Tamura
2009-03-05 18:58   ` Keir Fraser
2009-03-06  0:52     ` Yoshiaki Tamura
2009-03-06 16:28       ` John Levon
2009-03-06 16:48         ` Yoshiaki Tamura
2009-03-06 17:02           ` John Levon
2009-03-06 17:26             ` Yoshiaki Tamura
2009-03-06 17:36               ` John Levon
2009-03-06 23:03                 ` Brendan Cully
2009-03-09  2:05     ` Yoshisato YANAGISAWA
2009-03-09  8:13       ` Keir Fraser
2009-03-09 22:28         ` Yoshiaki Tamura
2009-03-10  8:21           ` Keir Fraser
2009-03-10 10:16             ` Yoshisato YANAGISAWA
2009-03-10 10:38               ` Keir Fraser
2009-03-10 16:51                 ` Brendan Cully
2009-03-04 22:43 ` Yoshiaki Tamura

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=492B8760.2000100@lab.ntt.co.jp \
    --to=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=Andrew.Warfield@citrix.com \
    --cc=brendan@cs.ubc.ca \
    --cc=james.harper@bendigoit.com.au \
    --cc=ospk-vm@lab.ntt.co.jp \
    --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.