)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"dae443958d68a257619e5ce96f1fdd7c4a677f28","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"f0513bd2_aed8c24e","updated":"2026-08-13 18:27:17.000000000","message":"Again, in order to actually have nested virtualization as of today inside of the workload, operator must explicitly add svm/vmx modules as an override, ie:\n```\nnova_nova_conf_overrides:\n  libvirt:\n    cpu_model_extra_flags: vmx\n```\n\nWithout that, even if everything else is enabled, VMs are not gonna have nested virt enabled/propagated.\n\nSo regardless of `nova_nested_virt_enabled` value extra step is still required to get it usable.\n\nBut even if not, introduction of `nova_nested_virt_disabled` along with `nova_nested_virt_enabled` is extremely confusing proposal, which is unclear already now.","commit_id":"84ace0ab205fc3e652703c1e7f78902f2b136389"},{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"7fa9a6dec0082dbc884c673013df73035358cd60","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"453fa29f_4103e9d7","in_reply_to":"f0513bd2_aed8c24e","updated":"2026-08-15 15:51:59.000000000","message":"Hello, well, you right. Ok.. I updated code for prevent confusion, standard logic is completely consistent with the current one,","commit_id":"84ace0ab205fc3e652703c1e7f78902f2b136389"}]}