hyperv reenlightenment can break live-migration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Jie Song |
Bug Description
With ZED nova enabled some new hyperv settings for instances with
os_type="windows" property (https:/
Enabling the reenlightenment setting can lead to unmigrateable VMs.
QEMU currently does not support full re-enlightenment notifications (see https:/
Windows VMs which have hyperv or WSL enabled make use of that feature,
but qemu can only migrate them if a tsc-frequency is set. The frequency
setting however is not applied and when set would restrict the target hv
to support the exact frequency.
Trying to migrate instances with reenlightenment enabled will fail
Traceback (most recent call last):
File "/usr/local/
timer() File "/usr/local/
cb(*args, **kw)
File "/usr/local/
waiter.
File "/usr/local/
result = function(*args, **kwargs) File "/usr/local/
return func(*args, **kwargs)
File "/usr/local/
with excutils.
File "/usr/local/
self.
File "/usr/local/
raise self.value
File "/usr/local/
guest.
File "/usr/local/
self.
File "/usr/local/
result = proxy_call(
File "/usr/local/
File "/usr/local/
six.reraise(c, e, tb)
File "/usr/lib/
raise value
File "/usr/local/
rv = meth(*args, **kwargs)
File "/usr/local/
raise libvirtError(
libvirt.
2023-12-
2023-12-
2023-12-
Adding the tsc clock or removing the hypver reenlightenment will make migration work again.
eg.:
<clock>
<timer name='tsc' frequency=
</clock>
A related bug for windows enlightenments targets evmcs: https:/
tags: | added: libvirt |
tags: | added: windows |
Changed in nova: | |
importance: | Undecided → High |
Changed in nova: | |
assignee: | nobody → Jie Song (songjie-cmss) |
Fix proposed to branch: master /review. opendev. org/c/openstack /nova/+ /904183
Review: https:/