From: jd <jdsw2002@yahoo.com>
To: KVM List <kvm@vger.kernel.org>
Subject: KVM Management : Migration
Date: Fri, 8 Aug 2008 19:22:56 -0700 (PDT) [thread overview]
Message-ID: <218687.89390.qm@web35807.mail.mud.yahoo.com> (raw)
Hi
For migration to work, it is recommended to start the VM with exact same params as the original VM. Can some one clarify the minimum set that should be the same.. while if others like VNC port Or default bridge can be different. (as the target machine may have vnc port already used.)
Also, if there are any compatibility checks for migration that needed to be done for predicting successful migration
-- KVM version ? Same... similar.. any other way to find if they are 'compatible' ? (As KVM is released frequently)
-- Processor same / similar ? Do we have a good compatibility matrix somewhere ? I am assuming that there is nothing specific to KVM but would like to confirm.
-- Memory availability : How to compute availability of "enough" memory ? Free physical memory ? Or some weight on available virtual memory/swap ? weave in some knowledge of ballooning details.
Any other checks ?
Thanks
/Jd
next reply other threads:[~2008-08-09 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 2:22 jd [this message]
2008-08-09 15:48 ` KVM Management : Migration Anthony Liguori
2008-08-09 21:33 ` jd
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=218687.89390.qm@web35807.mail.mud.yahoo.com \
--to=jdsw2002@yahoo.com \
--cc=kvm@vger.kernel.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