Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's happened to --no-hwvirt option? #142

Open
k41zen opened this issue Feb 1, 2019 · 2 comments
Open

What's happened to --no-hwvirt option? #142

k41zen opened this issue Feb 1, 2019 · 2 comments

Comments

@k41zen
Copy link

k41zen commented Feb 1, 2019

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.

@k41zen
Copy link
Author

k41zen commented Feb 1, 2019

Enabling VT-x in the BIOS and running the same command seems to have worked.

@k41zen
Copy link
Author

k41zen commented Feb 7, 2019

Still would like to know what happened to --no-hwvirt option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant