current on virtualbox

dr.s · 08-12-2012, 05:12 PM

Went into the bios and enabled the "Virtualization Technology" setting and the problem is gone, although I'm pretty sure I had in the past booted, installed and re-booted a Slackware virtual machine without enabling that setting (seems to be disabled by default), that might have been on a different pc/laptop though with AMD instead of Intel...

DasFox · 08-12-2012, 08:18 PM

Quote:

Originally Posted by dr.s

Went into the bios and enabled the "Virtualization Technology" setting and the problem is gone, although I'm pretty sure I had in the past booted, installed and re-booted a Slackware virtual machine without enabling that setting (seems to be disabled by default), that might have been on a different pc/laptop though with AMD instead of Intel...

That was my problem too, I personally over looked the Intel Virtualization in the bios and it was disabled. So I enabled it now Slack is working! WoOT!

Cheers

mcnalu · 08-14-2012, 05:59 AM

It seems there's a common cause here. I have an intel U5400 CPU in my laptop and it has no virtualisation extensions. However, windows XP and other OSes do run reasonably well in virtual box despite this. So I am left wondering why slackware does not. To be honest, this isn't really a hindrance to me, except that I wanted to play with and test slackware-current whilst on holiday.