qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jing-Wei Su <jwsu1986@gmail.com>
To: qemu-devel@nongnu.org
Subject: Live migration using a specified networking adapter
Date: Wed, 14 Apr 2021 12:49:05 +0800	[thread overview]
Message-ID: <CAFKS8hW6mwS89HHteyYcjRuvw7c5LxLdUrYo705Op7XreJBjTQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]

Hello experts,


I have a network topology like this diagram.

When start live migration moving a VM from Host A to B,

the migration process uses either 10GbE (10.0.0.1) or 1 GbE (10.0.0.2),

but the user cannot specify the source NIC by current migrate command.


To solve the problem, my rough idea is to add a source ipv4:port argument,

the migration command seems like

```

migrate -b tcp:10.0.0.1:4444 -d tcp:10.0.0.3:4444.

```


Is it an available solution? Or, is there any concern and sugesstion?

Besides the idea, is there any good way to this issue?


   +-----------------------------------------------------+
   |                     10GbE switch                    |
   +-----------------------------------------------------+
           |            |                |
           |            |                |
           |            |                |
  10.0.0.1 |    10.0.0.2|        10.0.0.3|
   +-+----------+-+--------+-+  +--+----------+---------+
   |  |10GbE NIC | |1GbE NIC||  |  |10GbE NIE |         |
   |  +----------+ +--------+|  |  +----------+         |
   |                         |  |                       |
   |      +---------+        |  |                       |
   |      |   VM    |        |  |                       |
   |      +---------+        |  |                       |
   +-------------------------+  +-----------------------+
           Host A                         Host B


Thank you.


Regards,

Derek.

[-- Attachment #2: Type: text/html, Size: 5314 bytes --]

             reply	other threads:[~2021-04-14  4:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14  4:49 Jing-Wei Su [this message]
2021-04-19 19:06 ` Live migration using a specified networking adapter Dr. David Alan Gilbert
2021-04-20  8:27   ` Daniel P. Berrangé

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=CAFKS8hW6mwS89HHteyYcjRuvw7c5LxLdUrYo705Op7XreJBjTQ@mail.gmail.com \
    --to=jwsu1986@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).