Additional triage After bringing up the server, I am trying to run VirtualBox and start the Oracle Linux VM. And it results in the following error message
VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE) I was checking on solutions for this and I found that 1) Why This Happens KVM uses VT-x/AMD-V virtualization extensions. VirtualBox, when running on a host with KVM enabled, cannot access those extensions because they are already in use. This is common when you're running VirtualBox on a Linux system where KVM is active. 2) How to Fix It Disable KVM Temporarily You can disable the KVM kernel modules before starting VirtualBox: For AMD CPUs, use kvm_amd instead of kvm_intel. Then start VirtualBox again. ⚠️ Note: This disables KVM until the next reboot. If you're using KVM actively (e.g., for CloudStack), this may not be ideal. In the above solutions, what should be the right deployment for the dev and test setup for us? On Fri, Aug 22, 2025 at 4:46 PM Rajiv Jain < connect.rajivjain.virtualizat...@gmail.com> wrote: > Hi Daan, David, Mates, > > I am trying to deploy the management server and KVM on the same computer > node by following the link > > > https://docs.cloudstack.apache.org/en/4.20.1.0/quickinstallationguide/qig.html > > > I got everything done successfully. But after some time, I am finding the > compute node is going down. And we experience this multiple times. I wanted > to confirm, is there anything I am missing? > > How can we confirm that getting the management server, CloudStack-agent, > and KVM on the same server is not causing any issues? > > Thanks > Rajiv >
