Hyper-V driver destroys and recreates the VM on cold migration / resize
Bug #1663238 reported by
Claudiu Belu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Triaged
|
Medium
|
Unassigned | ||
os-win |
Invalid
|
Medium
|
Unassigned |
Bug Description
Currently, the nova Hyper-V driver destroys the instance on the source node and recreates it on the destination node, losing some of the instance settings.
For this reason, guest PCI device IDs change, causing undesired effects in some cases. For example, this affects guests relying on static network configuration, which will be lost after a cold migration.
This issue can be solved by importing the desired VM on the destination node, and updating the VM resources according to the new flavor.
tags: | added: hyper-v |
description: | updated |
Changed in os-win: | |
importance: | Undecided → Medium |
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: resize |
Changed in os-win: | |
status: | New → Invalid |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/431223 /git.openstack. org/cgit/ openstack/ os-win/ commit/ ?id=133271f250a eff69792e9fba07 8a99034a1daf4b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 133271f250aeff6 9792e9fba078a99 034a1daf4b
Author: Claudiu Belu <email address hidden>
Date: Thu Feb 9 01:07:08 2017 +0200
vmutils: set all *DataRoot paths to the same value
In order to maintain consistency with create_vm, update_vm
should also set the *DataRoot paths to the same given value.
Furthermore, this will be required for planned VMs, in order to
prevent having instances running on different compute nodes and
different storages to have some of the *DataRoot paths pointing to
the old compute node.
Partial-Bug: #1663238
Change-Id: Ic9248f44de6ff0 97b8080a80fd321 2eeef6712f6