qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Jing-Wei Su <jwsu1986@gmail.com>
Cc: berrange@redhat.com, qemu-devel@nongnu.org
Subject: Re: Live migration using a specified networking adapter
Date: Mon, 19 Apr 2021 20:06:23 +0100	[thread overview]
Message-ID: <YH3UrzZ4L4/tGIK2@work-vm> (raw)
In-Reply-To: <CAFKS8hW6mwS89HHteyYcjRuvw7c5LxLdUrYo705Op7XreJBjTQ@mail.gmail.com>

* Jing-Wei Su (jwsu1986@gmail.com) wrote:
> 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.

I'm not sure what the OS lets us do, but if it lets us pick the IP and
port I think that would work; I don't think you need another tcp:
since we already know which protocol we're using.

> 
> ```
> 
> Is it an available solution? Or, is there any concern and sugesstion?
> 
> Besides the idea, is there any good way to this issue?

It's unusual; I don't think I've seen anyone ask for it before.
I assume there's a wayto get the host network stack to prefer
the 10GbE interface.
Or to use separate subnets; rememember that each interface
can have multiple IP addresses.

Dave

> 
>    +-----------------------------------------------------+
>    |                     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.
-- 
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  reply	other threads:[~2021-04-19 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14  4:49 Live migration using a specified networking adapter Jing-Wei Su
2021-04-19 19:06 ` Dr. David Alan Gilbert [this message]
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=YH3UrzZ4L4/tGIK2@work-vm \
    --to=dgilbert@redhat.com \
    --cc=berrange@redhat.com \
    --cc=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).