After some more digging, the issue was due to "some" RAM over-provisioning on the hypervisor - vbmc was sending error when trying to start the VM.
Reducing the memory footprint of the OC nodes leads to a plain success.
Good to know!
After some more digging, the issue was due to "some" RAM over-provisioning on the hypervisor - vbmc was sending error when trying to start the VM.
Reducing the memory footprint of the OC nodes leads to a plain success.
Good to know!