Fariborz, had any luck with this issue?
From: Pearl d'Silva
Sent: Monday, April 19, 2021 9:21 AM
To: users@cloudstack.apache.org
Subject: Re: Enabling nested virtualization
Hi Fariborz,
To enable nested virtualization on the KVM hypervisor hosts:
1. sh
cloudstack-agent service.
Start the VM(s) - you should now see the vmx flag in your guest VM(s).
Thanks,
Pearl
From: Nicolas Vazquez
Sent: Monday, April 19, 2021 9:33 AM
To: users@cloudstack.apache.org
Subject: Re: Enabling nested virtualization
Hi Fariborz,
Can you
nday, April 18, 2021 7:50 PM
To: users@cloudstack.apache.org
Subject: Re: Enabling nested virtualization
Hello,
I just added the following lines to agent.properties file:
guest.cpu.mode=host-model
guest.cpu.features=vmx
And stopped/started the VM. The CPU model name inside /proc/cpuinfo on the
Hello,
I just added the following lines to agent.properties file:
guest.cpu.mode=host-model
guest.cpu.features=vmx
And stopped/started the VM. The CPU model name inside /proc/cpuinfo on the
VM reads exac;y as the CPU model of the physical host but it still does not
expose the vmx feature to the
I would use imagination and imagine that in order to apply a specific CPU
model (and expose flags) to the needed VMs (ps aux | grep i-2-XXX-VM) -
you will need to stop/start just the wanted VMs.
Otherwise, after agent.properties change, it is required to restart the
agent, for obvious reasons.
B
Hi,
Should I stop/start all VMs or just the one I want to be deployed with VTX
flag?
Regards.
On Sun, Apr 18, 2021 at 1:49 AM Andrija Panic
wrote:
> Try with the custom CPU model inside the agents.properties, making sure you
> pass the VTX and other CPU flags. (you can defined CPU model, or us
Try with the custom CPU model inside the agents.properties, making sure you
pass the VTX and other CPU flags. (you can defined CPU model, or use some
CPU model + some more CPU flags (i.e. VTX)
Never tested, but is supposed to work that way.
Best,
On Sat, 17 Apr 2021 at 21:58, Fariborz Navidan
wr
