I have a laptop with Xubuntu desktop 14.10 , and I installed VirtualBox and updated it to the latest version .

I'm trying to install CentOS 7 (source downloaded from the official site) as a VM, but each time I begin the installation the laptop itself suffers from a kernel panic.

I wonder how a VM will kernel panic the laptop, and I want to know how to solve this issue.

  • The iso I use is CentOS-7.0-1406-x86_64-Everything.iso
  • The version of VirtualBox is 4.3.18.r96516
  • Laptop model: Dell E6430

  • VM Settings
    enter image description here

  • Crash photo
    enter image description here

    uname -a  
    Linux Laptop 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux  
  • Looking at your vbox screen-shot, are both Centos1 and Centos2 working, or they both are crashing the same as Centos3? When did you upgrade VirtualBox - before installing any of the clients shown, or just before Centos3? Did you install vbox from the Canonical repository, then upgraded from an Oracle download? I am running on the same XUbuntu 14.10 with vbox 4.3.20 r96996, so I might be able to help you figuring this out. – arch-abit Jan 16 '15 at 10:04
  • @arch-abit, yes all the others are working fine only centos7 crash the host itself – Fat Mind Jan 17 '15 at 5:21

somewhere on the internet i found suggestion the issue is related to fused FS .

so i reformatted the partition from NTFS to EXT4

then all the issues were gone and no more kernel panic

| improve this answer | |

You most likely have a corrupted download. 7.1 GB is a large file, this is why network install was invented in the first place. I downloaded it via torrent.

Here is the head of my vbox installation log, a very basic install on my experimental server. The entire log is too large to post, but if your install is crashing at the very beginning your log is going to be none, or going to look very different from mine.

VirtualBox VM 4.3.20 r96996 linux.amd64 (Nov 21 2014 15:55:22) release log
00:00:00.887295 Log opened 2015-01-17T06:20:31.951658000Z
00:00:00.887296 Build Type: release
00:00:00.887298 OS Product: Linux
00:00:00.887299 OS Release: 3.13.0-43-generic
00:00:00.887299 OS Version: #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
00:00:00.887313 DMI Product Name: ThinkServer TS140
00:00:00.887317 DMI Product Version: 70A4001LUX
00:00:00.887432 Host RAM: 15843MB total, 10266MB available
00:00:00.887434 Executable: /usr/lib/virtualbox/VirtualBox
00:00:00.887434 Process ID: 1249
00:00:00.887435 Package type: LINUX_64BITS_DEBIAN_7_0
00:00:00.921186 Installed Extension Packs:
00:00:00.921199   Oracle VM VirtualBox Extension Pack (Version: 4.3.20 r96996; VRDE Module: VBoxVRDP)
00:00:00.936796 UIMediumEnumerator: Medium-enumeration finished!
00:00:00.937106 Using XKB for keycode to scan code conversion
00:00:00.938619 SUP: Opened VMMR0.r0 (/usr/lib/virtualbox/VMMR0.r0) at 0xffffffffa1122020.
00:00:00.940886 Guest OS type: 'RedHat_64'
00:00:00.943064 fHMForced=true - Lots of RAM
00:00:00.943071 fHMForced=true - SMP
00:00:00.943075 fHMForced=true - 64-bit guest
00:00:00.946357 File system of '/media/abit/ISO/Lin/CentOS7/CentOS-7.0-1406-x86_64-Everything.iso' (DVD) is fuse
00:00:00.948904 File system of '/srv/VirtualBox_VMs/Experiment/CentOS7/Snapshots' (snapshots) is unknown
00:00:00.948912 File system of '/srv/VirtualBox_VMs/Experiment/CentOS7/CentOS7.vdi' is ext4
00:00:00.961183 Shared clipboard mode: Off
00:00:00.962319 Drag'n'drop mode: Off

UPDATE 01/21/2015

For any and all install, if you do not have such list you might need to start one: what can and what cannot, affect a kernel (in your case it is the GNU/Linux, not Windows or Apple or BSD or HURD or any other) during boot, and during operation - for your hardware.

This is your own specific list tied to your specific hardware, as it is inconceivable to list all variations, or to spend anyone's time minding such data. Data, after all, do not equals (useful) information by proxy.

So far what I suspect in your case is that these are NOT suspects: - The ISO - The laptop's BIOS - Xubuntu 14.10 plus all upgrades to date - xfce and all updates to date - Virtual Box 4.3.20 r96996

My experimental server's Xubuntu/xfce purpose is to host Virtual Box only, it is unchanged from the defaults except maybe the way I installed vbox - I only used the terminal, and I only used it once - what I currently have is no update or upgrade. I have not installed or removed anything else, what I do on this 'server' happens inside vbox clients, NOT on the host OS.

If you need to understand what is happening, one good approach might be to collect log data by the kernel, the distro, vbox and by client OS, and maybe more or better ways. This is a concept I am still trying to understand myself, so I end my update here. But I started to archive vbox client log data, and in time I would like to learn how to search and make sense out of them.

| improve this answer | |
  • i used the torrent also and checked the sha 256 and it's correct , the only diffrence i see is the vrsion of the virtual box so i will update it and try again , – Fat Mind Jan 17 '15 at 7:16
  • I keep my install and the log, if you need to compare I'll post my entry. – arch-abit Jan 17 '15 at 7:18
  • i updated the VB also but it didn't work, it sometime just hang and sometime causes the kernel panic , while in VMWARE it worked fine without any issue so i installed it in VMware and then cloned the HDD to VDI and it's working fine , how ever i still don't know how this should happen – Fat Mind Jan 19 '15 at 4:23
  • 1
    Good info.. You made it work by installing it in VMWare, then import the VMware-spun vdi into vbox? I never used VMware.. and now that the ISO is not a suspect anymore I need to update/change my answer. As your post says you want to get to the bottom of this and learn from it, and the best way to do that is to crash once more, but this time also install to some external storage from which you can read the OS logs after the fact? For example, /var/log on a USB stick, the rest to your internal drive? I need to remind you, /var/log is just the basics, the kernel could be made very verbose. – arch-abit Jan 20 '15 at 23:17
  • I just wonder... when the UNIX guys here get tired of this, and request us to move this discussion. I suspect we need to establish a base-line, also to record progress. So I go first. "hello!" – arch-abit Jan 21 '15 at 7:14

Your Answer

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.