Hi Rajiv, Glad you're able to solve some of your problems.
Most of the dev community build on top of Linux/macOS, and tend to use their own nested setup using KVM on x86. Many prefer Ubuntu for that, but we also have developers using macOS and probably nobody who regularly uses Windows. Non-linux users generally tend to build/run/test CloudStack management server with a locally running database (MySQL) but otherwise have other storage/compute resource running locally on the same network or connected via VPN elsewhere (but low latency). Some have truly remote setup and they'd just build cloudstack locally, scp the jar elsewhere to try/test their feature. If you've a Linux host/server you can, typically build and custom your own dev setup accordingly to you needs. At work and in the community, many use the simulator to do feature development & testing, which doesn't require any real hypervisor setup: https://github.com/shapeblue/hackerbook/blob/main/2-dev.md#simulator-based-development Otherwise, most would have a custom dev-test environment setup such that their management server / MySQL is running locally (say on their workstation) but the storage/hypervisor are different hosts on the same network (or connected via VPN). You can also see: https://github.com/shapeblue/hackerbook/blob/main/2-dev.md#monkeybox-based-development and https://github.com/shapeblue/mbx Regards. ________________________________ From: Rajiv Jain <connect.rajivjain.virtualizat...@gmail.com> Sent: Friday, August 22, 2025 17:00 To: users@cloudstack.apache.org <users@cloudstack.apache.org>; david.se...@webtasy.com <david.se...@webtasy.com>; Daan Hoogland <daan.hoogl...@shapeblue.com> Subject: Re: [DISCUSS] The compute server is going down 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 >
