[PATCH 0/2] Copy NetSettings

[Owen Smith <owen.smith@xxxxxxxxxx>]

XenVif currently has code to detect when a PV device has a working emulated
alias. XenVif will then copy the entire contents of its network settings to
a storage key based of VIF index.
When the driver starts, it will attempt to copy these settings from the
storage location back to various network setting locations for the new network
identity. This code is only executed when upgrading from emulated, but can be
extended to cover any case where the VIF is assigned a new network location,
provided the current network location's identifier (NetCfgInstanceId) is
stashed.
There are several upgrade scenarios that need to be covered to maintain network
configuration.
* Upgrade of XenBus, that exposes a new hardware ID to XenVif. In this case,
  the existing XenVif will rebind to a compatible ID exposed by XenBus and
  will not generate a new network connection. There currently is an issue that
  can cause, in some circumstances, XenBus and XenVif to enumerate the PV
  devices without issuing the VIF unplug.
* Upgrade of XenVif, binding to a different hardware ID exposed by XenBus.
  This is where the new XenVif coinstaller stashes the current network location
  identifier and XenVif's StartDevice will copy settings from the stashed
  network location identifier to the new network location identifier. XenNet
  could also rebind to a compatible ID exposed by XenVif, no chnage in network
  location is expected here.
* Upgrade of XenNet, binding to a different hardware ID exposed by Xenvif.
  This is not expected to change the network location, and therefore not require
  copying of network settings.

Owen Smith (2):
  Write current NetCfgInstanceId before upgrade
  Rework network settings copy code.

 src/coinst/coinst.c   | 341 ++++++++++++++++++
 src/xenvif/pdo.c      |  93 +++--
 src/xenvif/settings.c | 810 +++++++++++++++++++++++-------------------
 3 files changed, 849 insertions(+), 395 deletions(-)

-- 
2.32.0.windows.1