Comment 10 for bug 2048517

Hello Mauricio,

thanks for providing the nova patch. It worked as expected.

I installed on a node with xsaves enabled and updated nova.conf

# dpkg -l | grep nova
ii nova-api-metadata 2:21.2.4-0ubuntu2.7~ppa3 all OpenStack Compute - metadata API frontend
ii nova-common 2:21.2.4-0ubuntu2.7~ppa3 all OpenStack Compute - common files
ii nova-compute 2:21.2.4-0ubuntu2.7~ppa3 all OpenStack Compute - compute node base
ii nova-compute-kvm 2:21.2.4-0ubuntu2.7~ppa3 all OpenStack Compute - compute node (KVM)
ii nova-compute-libvirt 2:21.2.4-0ubuntu2.7~ppa3 all OpenStack Compute - compute node libvirt support
ii python3-nova 2:21.2.4-0ubuntu2.7~ppa3 all OpenStack Compute Python 3 libraries

# grep cpu_model /etc/nova/nova.conf
cpu_model = EPYC-Rome
cpu_model_extra_flags = -xsaves

Then I restarted nova-compute.

I had the following VM running which was using xsaves:

# virsh dumpxml instance-001499b6 | grep xsaves <feature policy='require' name='xsaves'/>

I stopped/started the VM and the xsaves feature was disabled after that

# virsh dumpxml instance-001499b6 | grep xsaves <feature policy='disable' name='xsaves'/>

and that allowed me to migrate the VM to a node with xsaves disabled (newer kernel)

I think next step should be to start SRU process for this patch, correct?

Thanks,
Giuseppe