Question about save and restore OVS per-port data in live migration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

When we try to migrate a guest with 12 NICs, we find libvirt will try
to get per-port data in finish phase, it makes the guest paused for
several hundred milliseconds.

  qemuMigrationCookieAddNetwork
    -> virNetDevOpenvswitchGetMigrateData for per-nic
      -> run 'ovs-vsctl --if-exists get Interface vnetx external_ids:Port'  (about 25ms)

In our case, there's no portData available and it seems there is no need to run the cmd.

Questions:
1. Is it necessary to get/set per-port data in migration finish phase? It will increase the downtime.
2. Is there any way (i.e. a switch) to not run the OVS cmd if there's no portData available? 

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux