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. Best, On Sun, 18 Apr 2021 at 13:22, Fariborz Navidan <mdvlinqu...@gmail.com> wrote: > 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 <andrija.pa...@gmail.com> > 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 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 <mdvlinqu...@gmail.com> > > wrote: > > > > > Hi All, > > > > > > How can I enable nested virtualization on KVM hypervisor so that a > guest > > VM > > > supports nested Intel-VTX? > > > > > > TIA > > > > > > > > > -- > > > > Andrija Panić > > > -- Andrija Panić
