Changing the boot disk via sunstone removes CPU_MODEL from the vm configuration

Product Support Bug Reporting
1

Please, describe the problem here and provide additional information below (if applicable) …

Versions of the related components and OS (frontend, hypervisors, VMs):

OpenNebula 7.0, KVM Nodes

Steps to reproduce:

Edit the Configuration of a VM via “Update VM Configuration” in SunStone, go to Boot order and select any disk, click on “Accept”

Current results:

the CPU_MODEL parameter gets removed from the VM configuration and needs to be re-added with onevm updateconf

Expected results:

change of boot order without messing up the VM configuration

2

Hello @twa,

Thanks for raising this issue on the category :wink:

From what I could investigate, there’s a workaround for this:

  • Modify the boot order via CLI using onevm updateconf instead of Sunstone.
  • Define CPU_MODEL in the original VM template so it is preserved during UI edits.

In any case, my suggestion would be file an issue on the OpenNebula repo:
Github Repo, so the technical team can review it better and give you a more technical reply.

Regards,