Closed samitcheema closed 3 years ago
@samitcheema interesting ... wonder how to say all of this without sidelining too much
To summarize, it makes sure the user has VT-x/AMD-V capability within their CPU and it is enabled before they start to proceed and work within their own virtual machine so they avoid any errors they might encounter further on. So nothing more than a small side note. @dogi
Sami's small side note could be placed somewhere around this section:
Problem
Users who are already working within their own dedicated VM and want to continue working within it might run into issues regarding nested virtualization.
Steps to reproduce the problem
Run vagrant up within your VM without VT-x/AMD-V support enabled.
Screenshots
N/A
Proposed solution
Dedicating a small section to those who are already working within a VM, to make sure their CPU has VT-x/AMD-V support and that they have VT-x/AMD-V enabled on their vm software. i.e. VMWare Workstation, Virtualbox etc.
NOTE:If you are already working within your own virtual machine and wish to continue to do so, please enable VT-x/AMD-V for your respected VM software to enable nested virtualization before proceeding forward. How to enable VT-x/AMD-V: Virtualbox, VMware.