You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to init a windows10 instance I get the following error in VirtualBox "VT-x/AMD-v hardware acceleration is not available on your system". The init command was:
The command gets to 100% and when I look at the VM in Virtualbox its showing the above message. Clicking OK shows me the blue windows logo and there it sits for hours (left it overnight last night).
The command is sat there and my CPU has gone through the roof but nothing seems to be happening.
Ignoring the enabling of this in the BIOS there's supposed to be an option (--no-hwvirt) to disable this in VMCloak according to the docs. However when running this on the command line it errors and listing the available options for VMCloak init --help it's not listed either. I've followed the instructions to install is so guess I'm using v4.
The text was updated successfully, but these errors were encountered:
When trying to init a windows10 instance I get the following error in VirtualBox "VT-x/AMD-v hardware acceleration is not available on your system". The init command was:
vmcloak init --win10x86 --iso-mount /mnt/win10 --ramsize 2048 windows10_1
The command gets to 100% and when I look at the VM in Virtualbox its showing the above message. Clicking OK shows me the blue windows logo and there it sits for hours (left it overnight last night).
vb.log below:
VBox.log
The command is sat there and my CPU has gone through the roof but nothing seems to be happening.
Ignoring the enabling of this in the BIOS there's supposed to be an option (--no-hwvirt) to disable this in VMCloak according to the docs. However when running this on the command line it errors and listing the available options for VMCloak init --help it's not listed either. I've followed the instructions to install is so guess I'm using v4.
The text was updated successfully, but these errors were encountered: