Hm, do you know the point of code there is intent to handle this rewrite? Can I patch this on runtime (without recompiling), just for testing... -----Ursprüngliche Nachricht----- Von: Chris Friesen [mailto:chris.friesen@windriver.com] Gesendet: Freitag, 18. Januar 2019 17:10 An: starlingx-discuss@lists.starlingx.io Betreff: Re: [Starlingx-discuss] cpu mode There is no way to prevent the rewrite of the nova.conf file as it is intended to be managed by the system. Chris On 1/18/2019 8:44 AM, von Hoesslin, Volker wrote:
i know, i know, i shouldnt spam this list ;) but after some tests i have tried to change the nova-conf (/etc/nova/nova.conf) and edit some values:
[default] libvirt_cpu_mode = "custom" // none -> costom libvirt_cpu_model = "EPYC-IBRS" // insert this line
[libvirt] cpu_mode = "custom" // none -> custom cpu_model = "EPYC-IBRS" // insert this line
but after reboot my compute-node, some auto-config logic is reconfigure this config-file and "[libvirt]" part the option "cpu_mode" is back to "none" and "cpu_model" is deleted completly :(
is there any way to prevent or configure this auto-config?
volker... ________________________________________
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss