From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Gaurav Poothia <gaurav.poothia@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cross version migration question (RH specific)
Date: Tue, 12 Dec 2017 10:05:49 +0000 [thread overview]
Message-ID: <20171212100548.GB2409@work-vm> (raw)
In-Reply-To: <CADDfC=q05U0NN5vTu08M-maV9HyT9f8o9sXcRSdgc8_dnFE4Vg@mail.gmail.com>
* Gaurav Poothia (gaurav.poothia@gmail.com) wrote:
> Hi,
> I have some dumb questions about this Red Hat cross version migration
> support matrix:
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-kvm_live_migration-live_migration_and_red_hat_enterprise_linux_version_compatibility_
>
> Questions:
> - Are all RHEL 7.x running the same version of QEMU?
They're all a 1.5.3 derivative.
> - Then the forward and backward migration support across minor
> releases (rows 3 and 4 in grid) is trivial right?
Yes, pretty much; we still have to check it of course as we add bug
fixes and things.
> - Does RHEV-H rev the QEMU versions more aggressively across minor versions?
Yes (see the qemu-kvm-rhev packages or in CentOS qemu-kvm-ev)
> - Where can I find a similar cross version migration support matrix for RHEV?
That's a good question; I'm not sure which docs cover that - although
at that level it's not just qemu versions that need considering.
The qemu level is similar to that above though; 6.x inwards is valid,
and some backwards and forwards are allowed within the 7.x range,
even though they're quite different versions of qemu.
Dave
>
> Thanks!
> Gaurav
>
>
> --
> Kiva.org - Loans That Change Lives
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2017-12-12 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 8:43 [Qemu-devel] Cross version migration question (RH specific) Gaurav Poothia
2017-12-12 10:05 ` Dr. David Alan Gilbert [this message]
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=20171212100548.GB2409@work-vm \
--to=dgilbert@redhat.com \
--cc=gaurav.poothia@gmail.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).