virtualbox.org

VirtualBox of 6.0.10 r132072 is installed on windows 10 pro version 1903 build 18362.295
Extension pack is installed well
I would like to start a CentOS VM in VirtualBox,
But CentOS7.6 (CentOS-7-x86_64-DVD-1810.iso) can not be created, it reports "kernel panic - not syncing: fatal exception"

Please provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

Here is the VBox.log file in zip format

Did you check any of the VM settings before launching the VM? I'm finding some of the choices very strange.

For example :-

• RAM: only 1GB allocated to the VM, on a host that has 25GB available (32GB installed). I would make this more like 4GB or 8GB.
• Graphics RAM: only 16MB allocated. I'd max this out to 128MB.
• Cores: only one core allocated to the VM, the host has 4 so I'd strike a balance by giving 2 to the VM.
• The virtual hard drive seems to be only 8GB. Is that enough for a 64bit CentOS install?

Other posts on similar problems seem to indicate a problem with IOAPIC. Your log contains the line :-

00:00:04.388776 CPUM: SetGuestCpuIdFeature: Enabled x2APIC
00:00:04.389040 IOAPIC: Using implementation 2.0! Chipset type ICH9

However your virtual motherboard chipset is PIIX3, not ICH9. At least one previously solved post indicated that selecting ICH9 and enabling IOAPIC solved the problem. Perhaps worth a try.

Thanks for all the advices! Since I tried many times, all failed. So last time I didn't really make the parameters bigger numbers, but taking what it was in wizard. Now I take all your suggestions and redo the creation, the result is the same, "kernel panic - not syncing: fatal exception".
The attached is the logfile. My other friends could easily create CentOS7.6 in their VirtualBox, only difference is the edition and version of Windows, they all use VBOX 6.0.10.

I guess that may be a compatibility problem between Win10 pro 1903 and VBox 6.0.10.

RustyPuma wrote: Now I take all your suggestions and redo the creation, the result is the same

You didn't just take mpack's advice, you improvised didn't you?

00:00:04.453151 ICH9 <integer> = 0x0000000000000001 (1)

Any particular reason why you decided to override the template defaults, and go with an unsupported, experimental, OSX-guests-only option? Please change it back to the default PIIX3. Do not change the defaults unless you know what you're getting into.

But here's the deal; even with the ICH9 chipset, I couldn't reproduce your problem. And the configuration was point-to-point identical, to the T. I compared our logs and they're like twins. I don't know what causes it in your case, but the problem is that it happens in real life too. I tried a few searches, but since I can't reproduce the problem, it was pointless.

There's another recent thread that mentions this issue, but again I couldn't find anything wrong with the config.

On why he tried ICH9, I imagine it's because I suggested it as a test in the last paragraphs of my post above.

I couldn't see anything in the logs either, unless it was maybe running out of resources: with that fixed I'm leaning towards it being a problem for the CentOS forums.

I chose ICH9 motherboard duo to a suggestion from one of your colleagues, I am not improvised at all when configuring systems. It is just a test, I'll remove the VM, it wasn't created anywany.
Many of my friends don't have that problem. I think it may be caused by some incompatibility between my Windows' edition/version/build and VirtualBox's edition/version. That's the reason why you could not reproduce the result, because the edition/version/build of the Windows you use may be older than mine. Hope you can fix it in next release.

Thanks and Hope it could be fixed soon.

Please try to install VirtualBox of 6.0.10 r132072 on windows 10 pro version 1903 build 18362.295,
then mount CentOS7.6 (CentOS-7-x86_64-DVD-1810.iso) to VBox's CDROM and do installation, you'll
reproduce the crash right away.

RustyPuma wrote:I think it may be caused by some incompatibility between my Windows' edition/version/build and VirtualBox's edition/version.

The VM basically can't discover anything about the host except the CPU, so it's hard for a host feature to affect a guest OS.

I think you should treat the problem as a guest OS issue. Not a VirtualBox issue, and not a host OS issue. Often it turns out to be a fix for some exploit.

Hi I've been having trouble installing CentOS on VirtualBox v.6.0.0 r132072

My Device specifications are as followed:

• OS: Windows 10 Pro Build 17134 (x64)
  Processor: Intel(R) Core(TM) i7-4510U CPU
  Laptop Model: TravelMate P256-MG 0867
  Hardware Virtualization is enabled

Please let me know how to address this issue,

Thank you.

Previous post merged with this topic as it seems to be the same problem. PS. the latter poster is using 6.0.10, not 6.0.0.

@Zellith

00:00:14.020356 Guest OS type: 'Linux_64'

There is a specific "Red Hat (64-bit)" template that you should have chosen when creating a CentOS VM, not the generic Linux one. I would delete the VM (you got nothing to lose at this point) and set it up correctly.

00:00:15.524483   NumCPUs           <integer> = 0x0000000000000002 (2)
00:00:18.856831 CPUM: Physical host cores: 2

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). See "CPU Cores versus threads" and "Why is it a bad idea to allocate as many VCPUs as there are physical CPUs?".

00:00:15.527883   VRamSize           <integer> = 0x0000000001000000 (16 777 216, 16 MB)

I would max out the VRAM, in VM Settings » Display » Video Memory = 128 MB.

Other than that I don't see anything wrong, again search on the webs for similar messages in physical computers as well...

@mpack

6.0.0 should be a typo, because r132072 belongs to VBox 6.0.10. So the merged message is the same version of VirtualBox as mine.

I have at least two other friends successfully installed CentOS7.6 (CentOS-7-x86_64-DVD-1810.iso) in VirtualBox of 6.0.10 r132072. The differences are Windows' Edition and Version, as well as hardware.

My computer is Dell Latitude laptop 5300 2-in-1 Core i7-8665U CPU 1.90GHz 2.11GHz
Host OS is Windows 10 pro version 1903 build 18362.295

I believe this is a real non-trivial problem. It will happen from time to time if it is not fixed.

I have the same prob with my device specifications are as followed:
laptop: Dell latitude 7300
Processor: i7 8665u
OS: Win10 Pro
VirtualBox: 6.0.10
Centos 7