From: Thorolf Godawa <nospam@godawa.de>
To: xen-users@lists.xensource.com, xen-devel@lists.xensource.com
Subject: Re: XEN and failover
Date: Thu, 09 Feb 2006 01:17:31 +0100 [thread overview]
Message-ID: <43EA8A1B.6090901@godawa.de> (raw)
Hi,
>First off, please don't reply to some random thread if you indend
>to open a new one.
sorry for this, I just was to lasy, I take care not to do it again.
OK, I have the following:
Two servers connected via NFS to a storage-solution.
Both servers have the same hardware and same software (SLES 10.0b3) on
it, both are running XEN 3.0.0 and some Linux-guests for testing.
I'm able to do "xm save/restore", "xm migrate --live ..." etc.
>Then, for failover, I don't see a reason why you shouldn't be able to
>apply the normal linux failover solutions to xen domUs, like heartbeat
OK, but heartbeat just checks if the other machine is still there and
then it can do s.th., f.ex. starting the domU that just crashed on the
master machine on the backup machine!
But it would be better to make in an fixed (and short as possible)
interval snapshots of the running VM including processor and memory
(like "xm save" does, but without interrupting or even disturbing the VM
too much), putting it on the shared storage and if the domU crashes
restoring it from the backup host quite fast and in a most actual state!
I've read several times the XEN 3 should support failover with the
live-migration, but how can I use it for the BEFORE the master crashes?
>The main problem with failover solutions always is to make sure the
>failing host releases its MAC or IP. Solutions include disabling the
With XEN 3 and the live-migration this should not be a big problem, or?
>failover solutions usually provide means to execute a script whenever
>action is needed, so issuing the right commands to your dom0 should be
>quite easy.
Yes, it should be, but only if you know the right commands and there
parameters :-)
Thanks for your answers,
--
Chau y hasta luego,
Thorolf
next reply other threads:[~2006-02-09 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 0:17 Thorolf Godawa [this message]
2006-02-09 10:05 ` Re: XEN and failover Thorolf Godawa
-- strict thread matches above, loose matches on Subject: below --
2006-02-06 14:02 [Xen-devel] RE: Intel/VT Petersson, Mats
2006-02-08 13:22 ` Intel/VT success :-) Thorolf Godawa
2006-02-08 14:17 ` Ralph Passgang
2006-02-08 21:27 ` XEN and failover Thorolf Godawa
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=43EA8A1B.6090901@godawa.de \
--to=nospam@godawa.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.