I am trying to set up Xubuntu in my VirtualBox 6.0 on a Windows 10 64bit system using CPU Intel Core i5-6300U CPU @ 2.40GHz with two Cores and 8 GB RAM. My system does not support virtualization.

I set the VirtualBox RAM to 4GB and assigned it 20 GB dynamically allocated storage. VirtualBox only allows me to dedicate one CPU to it, so I have it set to 1 CPU. The Paravirtualization Interface is set to "none"

Now, I am trying to start the VM to install Xubuntu from an .iso file, but every time I do that, my laptop goes to bluescreen immediately with the Stop Code "SYSTEM_SERVICE_EXCEPTION".

The advice I was able to find through Google centered largely around Hyper-V settings, which, to my understanding, are not relevant here, seeing that my machine doesn't support virtualization.

I'd really appreciate your support, as I am dependent on doing this on a work laptop which prevents me from just setting up Ubuntu as OS.




Blue Screen Log:

Problem Event Name: BlueScreen

Code: 3b

Parameter 1: c0000096

Parameter 2: ffffe000bc9538b3

Parameter 3: ffff93026ddf6bd0

Parameter 4: 0

OS version: 10_0_17134

Service Pack: 0_0

Product: 256_1

OS Version: 10.0.17134.

Locale ID: 1033

Extra information about the problem

Bucket ID: 0x3B_c0000096_VMMR0!unknown_function

VirtualBox Log:

00:00:03.449523 VirtualBox VM 6.0.2 r128162 win.amd64 (Jan 14 2019 14:48:15) release log

00:00:03.449558 Log opened 2019-01-23T20:13:31.895250700Z

00:00:03.449559 Build Type: release

00:00:03.449564 OS Product: Windows 10

00:00:03.449565 OS Release: 10.0.17134

00:00:03.449565 OS Service Pack:

00:00:03.561602 DMI Product Name: Surface Book

00:00:03.574934 DMI Product Version: D:0B:13F:1C:03P:38

00:00:03.574976 Host RAM: 8117MB (7.9GB) total, 2933MB (2.8GB) available

00:00:03.574981 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe

00:00:03.574982 Process ID: 8828

00:00:03.574982 Package type: WINDOWS_64BITS_GENERIC

00:00:03.578730 Installed Extension Packs:

00:00:03.578780 None installed!

  • You say "My system does not support virtualization": why would you expect it to run VB? However, your CPU almost certainly does, so you should investigate the BIOS settings for this. – AFH Jan 24 at 15:00
  • (1/2) Hi AFH, thanks for your help. I am new to this (trying to set up Virtualbox following the curriculum on Odin Project), so apologies in advance if my explanations are a bit unclear. I think I was a bit confused about whether my CPU supported virtualization. In the task manager it says "Virtualization: Not capable". However, I now checked on the intel website and, as you said, my CPU seems to support VT-x: intel.ly/2RQkK0T – deus-ex-machina Jan 24 at 16:06
  • (2/2) Now, I changed the "paravirtualization interface" in VirtualBox to "Default" and checked "Enable VT-x". In my BIOS (Win10 Enterprise 1803) however, there is no option to enable virtualization. I followed the instructions I found online to access UEFI firmware settings. The "BIOS" settings I can access are very limited and don't include the option to change virtualization to "enabled". Might this be a limitation that's inherent in the OS I have? Thanks again for your time. – deus-ex-machina Jan 24 at 16:14
  • I host VMs on WinXP, Win10 and Ubuntu on i3 and i5 CPUs, and with the correct BIOS/UEFI settings it just works, both for VMware and VirtualBox. I think I may have needed a couple of attempts to get the correct CPU settings, but it's quite a long time since I set them, so I don't remember the precise settings, and since the machines are in production use it's not so easy to reboot to check. I prefer VMware, and I found their on-line help useful. – AFH Jan 24 at 16:24
  • So, next twist: I ran Intel's Processor Identification utility software and it tells me that VT-x is not supported (Screenshot:imgur.com/bjGBG0E). If this is accurate, does that mean I have to use a different machine or use a dual boot? – deus-ex-machina Jan 24 at 18:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.