From: Lukas Straub <lukasstraub2@web.de>
To: Daniel Cho <danielcho@qnap.com>
Cc: qemu-devel@nongnu.org
Subject: Re: The problems about COLO
Date: Mon, 4 Nov 2019 19:37:19 +0100 [thread overview]
Message-ID: <20191104193719.665f6b3c@luklap> (raw)
In-Reply-To: <CA+XQNE5xLXSNUEEd9n_=Hcgu=8QXvwFNuZ4B5WunSmiqM_tnrg@mail.gmail.com>
On Thu, 31 Oct 2019 17:05:20 +0800
Daniel Cho <danielcho@qnap.com> wrote:
> Hello all,
> I have some questions about the COLO.
> 1) Could we dynamic set fault tolerance feature on running VM?
> In your document, the primary VM could not start first (if you start
> primary VM, the secondary VM will need to start), it means to if I
> want this VM with fault-tolerance feature, it needs to be set while
> we boot it.
Hi Daniel,
Yes, this is possible as long you have a quorum block node. The rest
can be added while running.
> 2) If primary VM or secondary VM broke, could we start the third VM
> to keep fault tolerance feature?
I'm currently working on this, see my latest PATCH series here:
https://lore.kernel.org/qemu-devel/cover.1571925699.git.lukasstraub2@web.de/
>
> Best regard,
> Daniel Cho.
next prev parent reply other threads:[~2019-11-04 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 9:05 The problems about COLO Daniel Cho
2019-11-04 18:37 ` Lukas Straub [this message]
2019-11-07 8:14 ` Daniel Cho
2019-11-07 13:34 ` Lukas Straub
2019-11-08 3:43 ` Daniel Cho
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=20191104193719.665f6b3c@luklap \
--to=lukasstraub2@web.de \
--cc=danielcho@qnap.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).