Same here (spec_ctrl_cpu_init), tested with VB 6.0.8, 6.0.10, 6.0.12 and dev build 6.0.13
[*]Here is the host's CPU information:
- CPUID.txt
- CPU Information from CPU-Z
- (113.28 KiB) Downloaded 676 times
[*]Here is the console output from a random VM:
[*]Here is the console output from a second VM:
[*] Microsoft Windows 10 (10.0) Professional 64-bit v1903 (Build 18362.329)
I've noticed this is happening (
kernel panic) when it's booting:
[*] CentOS Linux (3.10.0-
957.27.2.el7.x86_64) 7 (Core)
[*] CentOS Linux (3.10.0-
957.10.1.el7.x86_64) 7 (Core)
And doesn't happen (meaning, works) with:
[*] CentOS Linux (3.10.0-
862.11.6.el7.x86_64) 7 (Core)
[*] CentOS Linux (3.10.0-
693.5.2.el7.x86_64) 7 (Core)
My guess is that it's something related to the kernel, the 3.10.0.957 branch.
Funny thing, is that all of those listed VMs
work properly on my older machine:
Microsoft Windows 10 (10.0) Professional 64-bit v1809 (Build 17763.678) with Intel Core i7 8550U
For the record, I've already tried Bios settings, bios upgrade, disabling hyper-v, bcedit, core isolation, etc.