All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jaggi, Manish" <Manish.Jaggi@cavium.com>
To: Anthony Liguori <aliguori@us.ibm.com>,
	Juan Quintela <quintela@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Jaggi, Manish" <Manish.Jaggi@cavium.com>
Subject: [Qemu-devel] [Query] Live Migration between machines with different processor ids
Date: Thu, 23 Aug 2018 11:18:37 +0000	[thread overview]
Message-ID: <CD29DCF7-6537-406F-A127-6A2FFDDAAD79@caviumnetworks.com> (raw)
In-Reply-To: <CABgNM92-PHWg3X41tCVfErmV9-Hnu5GYpz_pa9-iXfbScFUCZg@mail.gmail.com>

Hi,

Posting again with my cavium ID and CCing relevant folks


Live Migration between machines with different processorIds

VM Migration between machines with different processorId values throws
error in qemu/kvm. Though this check is appropriate but is overkill where
two machines are of same SoC/arch family and have same core/gic but
delta could be in other parts of Soc which have no effect on VM
operation.

There could be two ways to address this issue by ignoring the
comparison of processorIDs and so need feedback from the
community on this.

a) Maintain a whitelist in qemu:

This will be a set of all processorIds which are compatible and migration can
happen between any of the machines with the Ids from this set. This set can
be statically built within qemu binary.

b) Provide an extra option with migrate command

   migrate tcp:<ip>:<port>:<dest_processor_id>

This is to fake the src_processor_id as dest_processor_id, so the qemu running
on destination machine will not complain. The overhead with this approach is
that the destination machines Id need to be known beforehand.

If there is some better way… please suggest.

Thanks,
Manish

  reply	other threads:[~2018-08-23 11:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21  6:39 [Qemu-devel] Live Migration between machines with different processor ids Mjaggi Oss
2018-08-23 11:18 ` Jaggi, Manish [this message]
2018-08-23 14:29   ` [Qemu-devel] [Query] " Juan Quintela
2018-08-24  9:24     ` Jaggi, Manish
2018-08-28 17:27       ` Dr. David Alan Gilbert
2018-08-29 12:40         ` Jaggi, Manish
2018-08-29 13:16           ` Andrew Jones
2018-08-31  9:52             ` Jaggi, Manish
2018-08-31 11:11               ` Andrew Jones
2018-09-04  9:16                 ` Jaggi, Manish
2018-09-04  9:54                   ` Andrew Jones
2018-09-04 10:27                     ` Juan Quintela
2018-09-04 10:32                     ` Dr. David Alan Gilbert
2018-09-04 12:17                       ` Peter Maydell
2018-09-05 11:46                     ` Jaggi, Manish
2018-09-05 12:20                       ` Andrew Jones
2018-09-05 12:42                         ` Jaggi, Manish
2018-09-05 13:17                           ` Andrew Jones
2018-08-29 13:58           ` Dr. David Alan Gilbert
2018-08-31  9:41             ` Juan Quintela

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=CD29DCF7-6537-406F-A127-6A2FFDDAAD79@caviumnetworks.com \
    --to=manish.jaggi@cavium.com \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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.