I looked at these related, previously asked questions and followed their suggestions as indicated in the steps above. Related Stack Exchange Questions and Other References I have uninstalled VirtualBox, rebooted, reinstalled, and then rebooted again. I have "repaired" the VirtualBox installation.
I also check that Windows Security > Device Security > Core Isolation Details is set to Off. …because my googleing seems to indicate that some or all of these might be an issue.īased on a VirtualBox forum ( I have a 64bit host, but can't install 64bit guests), using gpedit.msc, I set Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security to Disabled. I inspected Windows Features to ensure that the following are not checked: This is a vanilla Windows 10 Pro installation, no additional software (i.e., no addon virus protection software). In the Windows guest machine, I can see that the host's physical CPU details are passed through in Settings > System > About and it shows as a "64-bit operating system, 圆4-based processor". I have checked Enable VT-x/AMD-V on the System > Acceleration tab in the Ubuntu host's VirtualBox config for the Windows 10 guest machine. What I Have Already Tried …on the Ubuntu Host
Our Vagrant config is using 64-bit base images, so I need to be able set up 64-bit guests inside this Windows 10 guest. The purpose for creating a VM inside a VM is to be able to ensure that VirtualBox is working so that I can test Vagrant configuration inside a Windows 10 environment.
After several attempts to resolve this, I am still only seeing 32-bit options. I only see 32-bit options inside the Windows guest. I am trying to create an Ubuntu (64-bit) guest inside the Windows 10 guest. I installed VirtualBox v6.0.10 in the Windows 10 guest (Windows 10 Pro – v1903 – 64-bit). I have created a Windows 10 (64-bit) guest. I am running VirtualBox v5.2.32 on an Ubuntu 18.04 host.
0 kommentar(er)
