Juicebox - seeing "hardware acceleration not available" error on start - is this OK?

#1

I followed the instructions here https://jpadilla.github.io/juicebox/#get-started to install Juicebox. I have a Windows laptop with Win 7 Pro. Seeing this error when I do a “normal” start on the Juicebox VM.
VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.

Upon hitting “continue” the window did come up but not sure what I can do with it to test whether this is still OK to use. Is this error expected?
Thanks.

#2

Huh. So the VM did correctly pop up in the end, just an error?

#3

Yes but I can’t do anything in that window after it captures the mouse and keyboard.

VM image.JPG1919×1034 104 KB

After I choose Ubuntu, it is a black window. I’'m stuck, keystroke or mouse movements do nothing. What should I be seeing?
(this post is not allowing me to upload multiple images so I will write another post with the 2nd image of the blank screen)
Thanks.

#4

Here is what I see after I choose Ubuntu above.

VM image after choosing ubuntu.JPG1910×1034 82.2 KB

#5

I had to escalate this to some people because it looks like the image doesn’t work with the laptop you have. We can just get your laptop set up with Python in person tomorrow so you don’t have to use the VM.

If you don’t have a code editor that you like, mind grabbing http://www.sublimetext.com/ before tomorrow?

A mentor can walk through these instructions with you tomorrow. :) http://docs.python-guide.org/en/latest/starting/install/win/

#6

Alternatively, if you’re comfortable messing around with your laptop’s BIOS, you can see if there’s a way to enable "Set Virtualization".

I opened an issue with Juicebox and that’s what they suggested.

It can be tricky to get into the BIOS, it really depends on the device and manufacturer. You might need to search for how to get into the BIOS for your specific laptop model. It usually involves holding some button while it’s booting. Also be careful to not change other things willy-nilly. :)

If you’re not comfortable doing that, no worries! We should be able to get you going with just Windows and a bit of extra work.

#7

I also faced the same issue and it went away after I made the BIOS changes. Thanks shazow!!

#8

OK, the BIOS idea worked, thanks! Though why it depends on hardware virtualization when the VirtualBox is supposed to provide software virtualization is a mystery to me. Juicebox is doing something weird.

#9

Yeah I’m looking for other solutions now just in case.