image 2017-05 did not work on windows

[skasberger]

at the ELPUB workshop the virtual machine did not start on windows machines (it did work on one mac and on my ubuntu).

there was one error re-occuring (5 of 5 machines):

after pressing continue, the boot up process of the ubuntu os (after selecting it), stopped and no commands were executed and listed up. nothing was moving, so the start up process was stuck in the middle. can not really say, if the problem relates to the error message from above.

[chreman]

Could not reproduce on my Windows 10 machine, but from an initial search, it looks like the problem is located on the hardware/BIOS level.

https://forums.virtualbox.org/viewtopic.php?f=1&t=62339
http://www.itworld.com/article/2981515/virtualization/virtualbox-diagnose-and-fix-vt-xamd-v-hardware-acceleration-errors.html
https://askubuntu.com/questions/118006/amd-v-is-not-enabled-in-virtualbox-on-amd-apu

[tarrow]

Chris is correct. This is not a windows problem. You would have seen the same the same error on the same laptop if either ubuntu or (somehow) mac was installed.

The problem is that the CPU either doesn't support or has disabled in the BIOS hardware virtualization.
See: https://en.wikipedia.org/wiki/X86_virtualization

Often this can be fixed by turning it on in the BIOS but on corporate machines this may be locked down

[skasberger]

so, there is no other solution, than to advice people on changing something in the bios to this problem?

thats not really a good way to go, especially at workshops. people often do not know about this stuff (password, how to get in). one brought for examply his working laptop and he did not even know his admin password (could not install virtualbox). for the workshop facilitator this can be pretty tricky. i often dont know, how to get into bios (same will be for many other people).

which type of computers should we expect mostly to affected by this? old ones, laptops??

@petermr @chreman @tarrow any ideas how to solve this problem best?

in my opinion, its still the best way to coop with it when it appears and try to reduce the users impacted from it. but the VM as a whole is getting more and more problematic, as more experience we collect with it.