weizhouapache commented on issue #8596:
URL: https://github.com/apache/cloudstack/issues/8596#issuecomment-1924032090

   > Yes I want VMs to support nested virtualization
   > 
   > Exact requirement is I want to run Hyper V on Windows Server 2019 VM
   > 
   > My host processor is AMD EPYC
   > 
   > Just for clarification Whether I need to follow below steps since my host 
is already showing as nested virtualization enabled
   > 
   > 
![image](https://private-user-images.githubusercontent.com/48643957/301866248-eeef208e-232c-47b4-9747-8ba483cbbf0f.jpeg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY4ODUxOTIsIm5iZiI6MTcwNjg4NDg5MiwicGF0aCI6Ii80ODY0Mzk1Ny8zMDE4NjYyNDgtZWVlZjIwOGUtMjMyYy00N2I0LTk3NDctOGJhNDgzY2JiZjBmLmpwZWc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMjAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDIwMlQxNDQxMzJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04Y2U5YzU3MjM1MmI5YTI0ZjU0NGMwY2E3NzJjZWY5ZjgyZWUzNzkyNWM3NTYwZjQ3ZDI2NTkzMjMwNTk1MDg5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.wMNXxxvXq1SZ4DlNYMfOfj-7Vth40EBsmdgfXN8IuIc)
   > 
   > _Create the following file: /etc/modprobe.d/kvm-nested.conf and add the 
following details to the file: options kvm-amd nested=1_
   
   it looks good. nested is already enabled on the kvm host.
   
   now you need to add a cpu flag to the vms. please refer to 
https://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html#configure-cpu-model-for-kvm-guest-optional
   
   since the processor is AMD, you can try with a cpu feature "svm" ("vmx" is 
for intel processors)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to