[SOLVED] No accelerator found, Virtualization set to "all"

Mrgcman · Apr 12, 2016

Good afternoon everyone!

When trying to launch Windows Server 2012 for the first time I am getting the following error:

Code:

Error: no accelrator found!

I read that this is caused by not having virtualization; it's set to full and I am running Debian 8. lscpu gives the following output:

Code:

# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 62
Model name:            Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
Stepping:              4
CPU MHz:               2094.748
BogoMIPS:              4189.49
Hypervisor vendor:     KVM
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              15360K
NUMA node0 CPU(s):     0-3

I would be happy to know if anyone have any clue what's up.

spirit · Apr 13, 2016

you need to enable vtx in your bios

(generally on cpu features - enable virtualisation technology, something like that)

Mrgcman · Apr 19, 2016

Thank you for the information @spirit.
The virtualization is set to "full" in my BIOS and I can't change that.

Does anyone know a workaround or a alternative route?
Thank you.

wosp · Apr 20, 2016

And PVE is installed on the physical node? Or is PVE installed in a VM?

Mrgcman · Apr 21, 2016

Hey @wosp.
It's a VDS with dedicated cores.

I am more than happy to try a alternative route or workaround if this doesn't work out

.

wosp · Apr 21, 2016

Please see https://pve.proxmox.com/wiki/Nested_Virtualization

I'm pretty sure this is your solution.

Mrgcman · Apr 21, 2016

That seems like the ideal solution for me @wosp!

However, /sys/module/kvm_intel/parameters/nested is not a directory in /sys/module on my Debian 8 system.
Would this be located in a different location for the latest version of Proxmox?

wosp · Apr 21, 2016

Hmm, no it should be there. For example, below is on a PVE 4.1-22 node:

Code:

root@node02:~# ls -l /sys/module/kvm_intel/parameter
/nested 
-r--r--r-- 1 root root 4096 Apr 21 21:25 /sys/module
/kvm_intel/parameters/nested

Are you sure you have a Intel CPU? What is the output of "cat /proc/cpuinfo"?

Mrgcman · Apr 21, 2016

Hey again @wosp.

Yes that is correct, I have a Intel CPU, I also replaced it with "amd" just for testing purpose, here is full directory:

I reinstalled the Debian 8 today and performed a clean install of latest Proxmox, all files are clean.

$ pveversion
pve-manager/4.1-33/de386c1a (running kernel: 3.16.0-4-amd64)

Code:

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 62
model name      : Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
stepping        : 4
cpu MHz         : 2094.748
cache size      : 15360 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr s                 se sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon nopl nonstop_tsc eagerfpu pni pclmulqdq ssse3 c                 x16 pcid sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c rdrand hypervisor lahf_lm ida arat xsaveopt fsgsbase                  smep
bogomips        : 4189.49
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 62
model name      : Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
stepping        : 4
cpu MHz         : 2094.748
cache size      : 15360 KB
physical id     : 0
siblings        : 4
core id         : 1
cpu cores       : 4
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr s                 se sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon nopl nonstop_tsc eagerfpu pni pclmulqdq ssse3 c                 x16 pcid sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c rdrand hypervisor lahf_lm ida arat xsaveopt fsgsbase                  smep
bogomips        : 4189.49
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 62
model name      : Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
stepping        : 4
cpu MHz         : 2094.748
cache size      : 15360 KB
physical id     : 0
siblings        : 4
core id         : 2
cpu cores       : 4
apicid          : 2
initial apicid  : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr s                 se sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon nopl nonstop_tsc eagerfpu pni pclmulqdq ssse3 c                 x16 pcid sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c rdrand hypervisor lahf_lm ida arat xsaveopt fsgsbase                  smep
bogomips        : 4189.49
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 62
model name      : Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
stepping        : 4
cpu MHz         : 2094.748
cache size      : 15360 KB
physical id     : 0
siblings        : 4
core id         : 3
cpu cores       : 4
apicid          : 3
initial apicid  : 3
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr s                 se sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon nopl nonstop_tsc eagerfpu pni pclmulqdq ssse3 c                 x16 pcid sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c rdrand hypervisor lahf_lm ida arat xsaveopt fsgsbase                  smep
bogomips        : 4189.49
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:
root@rs000015:/sys/module#

tom · Apr 21, 2016

Mrgcman said:
pve-manager/4.1-33/de386c1a (running kernel: 3.16.0-4-amd64)

not sure if its related but you do not run a Proxmox VE kernel.

Mrgcman · Apr 22, 2016

Hey @tom, I was unsure if the Kernel part in Wiki was required, I ran these commands:

Code:

apt-get remove linux-image-amd64 linux-image-3.16.0-4-amd64 linux-base

And as a result I got this screen:

Is this correct and safe to proceed?

tom · Apr 22, 2016

no, you cannot remove the running kernel.

first, install the proxmox ve kernel and reboot into the proxmox ve kernel - as described in the wiki.

after this, you can remove the 3.16 kernel.

Mrgcman · Apr 22, 2016

Hey @tom, you were right, I reinstalled the OS and followed the steps;

Code:

$ apt-get update && apt-get dist-upgrade
$ echo "deb http://download.proxmox.com/debian jessie pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list
$ wget -O- "http://download.proxmox.com/debian/key.asc" | apt-key add -
$ apt-get update && apt-get dist-upgrade
$ apt-get install proxmox-ve ntp ssh postfix ksm-control-daemon open-iscsi systemd-sysv
$ reboot

$ pveversion
pve-manager/4.1-33/de386c1a (running kernel: 4.4.6-1-pve)
The /sys/module/kvm_intel/parameters/nested is still not there, did I miss something?

wosp · Apr 22, 2016

Is it possible to test/re-install with a Proxmox VE installation ISO from http://www.proxmox.com/en/downloads/item/proxmox-ve-4-1-iso-installer ?

Mrgcman · Apr 22, 2016

Unfortunately not @wosp.

Any clues what's wrong/alternative method?

wosp · Apr 22, 2016

Hmm, no I don't have any other clues how to enable nested support for you, sorry.

You can disable KVM hardware virtualisation (options tab of the VM), so you can at least start the VM. But performance would not be very good.

Mrgcman · Apr 22, 2016

Thank you for all the help @wosp

.

Would love to hear other input if anyone has any suggestions!

Mrgcman · May 1, 2016

I migrated my install to a better server and with VT-x enabled in BIOS.

-Solved!

Search

Search

[SOLVED] No accelerator found, Virtualization set to "all"

Mrgcman

Member

spirit

Distinguished Member

Mrgcman

Member

wosp

Renowned Member

Mrgcman

Member

wosp

Renowned Member

Mrgcman

Member

wosp

Renowned Member

Mrgcman

Member

tom

Proxmox Staff Member

Mrgcman

Member

tom

Proxmox Staff Member

Mrgcman

Member

wosp

Renowned Member

Mrgcman

Member

wosp

Renowned Member

Mrgcman

Member

Mrgcman

Member