virtualbox.org

@'John Tang'
I merged your thread with the most prominent one dealing with that issue, read the thread from the beginning.

John Tang wrote:Then I realized the "Windows Hypervisor Platform" has been disabled. So I enabled it

Wrong move. Please disable everything Hyper-V related, it competes really aggressively with VirtualBox.

@socratis
Thanks for the valuable information. Now my VM is working again.

I have disabled hyper-v and hypervisor.

I also need to run .\DG_Readiness_Tool_v3.5.ps1 -Disable -AutoReboot in powershell as administrator

Finally my vm is back to life.

Glad to hear it 'John Tang'.

i download the image CentOS-7-x86_64-DVD-1810
the version of the virtualbox is 6.0.14
the system of my computer is windows10,the detailed configuration is in the annexs.
i create the virtual machine, An error has occured,the steps to create are in the annexs.
the logs of the creating a virtual machine process is also in the annexs,the error is

ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37".

i can create the virtual machine centos6.5 with the image CentOS-6.5-x86_64-bin-DVD1 on the virtualbox, and i can create the virtual machine centos7 in another computer.
please help me find the problem,thank you!

The problem is solved,when i rollback the version to 6.0.4.

This kernel panic thing has happened rather a bit and the 'one solution' hasn't emerged yet. Try a Google:

centos7 error kernel panic site:forums.virtualbox.org

Solutions that work in some cases don't apply in others. It's still an open question. For some, rolling back to earlier versions has worked.

If an earlier version works but a later version does not, then the developers need to hear about it, if they haven't already, on the Bugtracker. A log of failing 6.0.14 and another of working 6.0.4 would be good.

Some folks have Hyper-V interfering with their Virtualbox, but you're clear of this problem:

00:00:02.561339 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support

The "Could not take a screenshot (VERR_NOT_SUPPORTED)" error happens all the time even on working guests, you can ignore it.

You have six available cores in the host PC, only one in the guest. You can give it two. Also, Your host PC has almost 27GB available. You can give your guest more than the 1GB it has now. Reinstall the guest OS after making these changes.

No idea if these changes will help, though.

@'akun'
I merged your thread with the most prominent one dealing with that issue, read the thread from the beginning.

@akun, I tried CentOS-7-x86_64-DVD-1810 on my Windows 10 host, Virtualbox 6.0.4 and 6.0.14 and got good installs and normal runs with no kernel panics on both Virtualbox versions.

FWIW there's lots of info in a web search:

centos kernel panic not syncing fatal exception

that shows this happens on real computers, too. Maybe there's a clue?

scottgus1 wrote:I tried CentOS-7 ... and got good installs and normal runs ... this happens on real computers, too. Maybe there's a clue?

Yes, there most definitely should be one, and I tend to start thinking that it's in the CPU capabilities. The question is to figure out which one...

'scottgus1', do you happen to have a log from a CentOS VM? I'm interested actually in your CPU, the line that goes like:

00:00:03.106553 Full Name: " ... "

I had the same issue with VirtualBox 6.0.14 and versions RedHat 7.6-7.7 and CentOS 7.
The problem occures in very first step of installation from DVD.iso. After "Install CentOS" - black screen with errors (the most noticeable was: spec_ctrl_cpu_init)
After magic command:

JacenBoy wrote: ...
Solution was:

Code: Select all

VBoxManage modifyvm <vmname> --spec-ctrl on

(where <vmname> is the name of you virtual machine)
...

I'm already getting to the installation process and everything looks perfect

Thank you JacenBoy!!!

socratis wrote:'scottgus1', do you happen to have a log from a CentOS VM?

Sure, here you go:

centos 7 b-2019-11-10-12-34-01.zip

(28.37 KiB) Downloaded 36 times

The 'full name' line is:

00:00:04.669634 Full Name:  "       Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz"

And in accord with the spec-ctrl question, 'Inspectre' says Meltdown and Spectre are protected on this host PC.

Here's the .vbox file, if anyone wants it:

centos 7 b.zip

(1.28 KiB) Downloaded 30 times

Here are two other hosts I have. Both run the CentOS-7-x86_64-DVD-1810 just fine.

Host 2:

00:00:03.246832 Full Name:  "Intel(R) Core(TM) i5 CPU 750  @ 2.67GHz"

Meltdown & Spectre fixes turned off.

centos 7-2019-11-10-13-28-51 corei5.zip

(27.3 KiB) Downloaded 31 times

Host 3:

00:00:19.541584 Full Name: "AMD A4-3400 APU with Radeon(tm) HD Graphics"

Meltdown doesn't happen in this CPU, Spectre fix turned off.

centos 7-2019-11-10-13-33-01 AMD win7.zip

(20.75 KiB) Downloaded 26 times

Hello,

I am experiencing a similar issue to 'Firefds' when attempting to install a CentOS 7 guest on my Windows 10 host running VirtualBox 6.0.10. Detailed information:

Host: Windows 10 Enterprise Version 10.0.16299 Build 16299 | 64 bit | 64 GB RAM
Guest: CentOS 7 18.10 | 64 bit | 8 GB RAM

Both VBox.log and VBoxHardening.log are in the "VMLogs" zip file.

Things I've tried (one at a time):
1. Installing different versions of VirtualBox (5.2.34 and 6.0.14)
2. changing chipset to ICH9
3. Disabling I/O APIC
4. Disabling 3D acceleration
5. changing Graphics Controller to VBoxSVGA

I'd be very grateful for any insight anyone is able to provide!

Update: Right before I posted this, I tried one last thing:
Changing my guest OS to CentOS 7 18.04 . This isn't my preferred solution, but it also didn't give a kernel panic, which I consider an improvement
I've attached the logs from that successful run as well ("SuccessLogs") for reference.

Hej all,

I have the same kernel panic using VirtualBox version 6.0.14 r133895 no matter which paravirtualization I choose (even "None").

I get this on my Deskotp and my Laptop both running Windows 10 Pro 1909 on Intel CPUs (using the same VM image).
Since I have installed CentOS quite some time back, I still have an old Linux Kernel (3.10.0-693.5.2.el7.x86_64) which works flawless.

3.10.0-693.5.2.el7.x86_64 works fine: All newer Kernels do fail: So something changed between Kernel 3.10.0-693.5.2 and 3.10.0-957.27.2 that trigers the kernel panic...

Greetings
Bjoern

I faced same issue with Oracle linux 7.7 and VirtualBox 6.0.14.
Once I downgraded VirtualBox version from 6.0.14 to 6.0.6, it got resolved.