VirtualBox

Ticket #10427 (closed defect: fixed)

Opened 2 years ago

Last modified 22 months ago

Warm boot with Linux kernel => 3.0 locks or fials

Reported by: Perryg Owned by:
Priority: major Component: guest smp
Version: VirtualBox 4.1.12 Keywords: lock, bad warm boot, kernel=> 3.0
Cc: Guest type: Linux
Host type: Linux

Description

I have been seeing this for a while but didn't know what to post before. It happens when trying to do a warm boot of the guest, but not always. Perhaps 80%+ of the time.

It will either go through the shutdown part and then just freeze before Grub shows or if it does make it past the Grub window it shows softlocks on the CPU. I really don't know what to provide but I do see it showing in the guest log.

This can be followed with a shut down (cold boot) and the guest will boot properly. I think this started happening around the time the 3.* kernels started being used.

Let me know what else you need and I will provide it.

Attachments

Debian-SID-2012-04-09-13-48-09.log Download (91.4 KB) - added by Perryg 2 years ago.
Capture.PNG Download (26.3 KB) - added by CoreyW 2 years ago.
CentOS 6.2 x86 kernel panic screen
VBox.log.1 Download (72.8 KB) - added by CoreyW 2 years ago.
CentOS 6.2 x86 failure log
centos_6.2_2.6.PNG Download (22.1 KB) - added by web_knows 2 years ago.
CentOS 6.2 kernel panic after VBox Guest Additions install
centos6-oops.png Download (34.8 KB) - added by rschmied 22 months ago.
CentOS 6.2 32 Bit crash
VBox.log Download (72.5 KB) - added by rschmied 22 months ago.
CentOS 6.2 VBox Log file
centos6.vbox Download (6.7 KB) - added by rschmied 22 months ago.
CentOS 6.2 Configuration File

Change History

Changed 2 years ago by Perryg

comment:1 Changed 2 years ago by Perryg

A litle more information. While testing I notice that on a warm boot and hang, you can inject a reset which does reboot the guest again but it does not solve the issue. I did this several times and after the logo screen and just before the Grub menue shows the guest hangs. Finally resorting to a power down then start and the guest boots normal.

comment:2 Changed 2 years ago by Perryg

Further investigation shows this is not only happening in SMP but also i686.

Changed 2 years ago by CoreyW

CentOS 6.2 x86 kernel panic screen

comment:3 Changed 2 years ago by CoreyW

A very similar problem seems to happen when cold booting a CentOS 6.2 x86 client on several different Windows 7 x64 hosts (DELL, HP laptops and desktops). VM with both Guest Additions installed and not installed exhibit kernel panics on cold boots just past the grub menu.

Sometimes, if the VM is shutdown and restarted repeatedly, it will boot properly - not all the time, though.

Attachment submitted showing kernel panic.

Changed 2 years ago by CoreyW

CentOS 6.2 x86 failure log

comment:4 Changed 2 years ago by web_knows

Similar problem here with a few differences.

VirtualBox version: 4.1.12.
Host version: Windows XP SP 3
Guest version: Linux CentOS 6.2 (kernel 2.6.32)

After installing CentOS, rebooted the VM and it worked fine several times. Then, decided to install the VirtualBox Guest Additions for Linux bundled with that version of VB. Since then, I can't boot the VM anymore and it is failing with a kernel panic as showed on the screenshot attached.

Last edited 2 years ago by web_knows (previous) (diff)

Changed 2 years ago by web_knows

CentOS 6.2 kernel panic after VBox Guest Additions install

comment:5 follow-up: ↓ 7 Changed 2 years ago by deizel

We ran into the  same issue - solved by switching chipset emulation from PIIX3 to ICH9.

VBoxManage modifyvm "VM name" --chipset ich9

Does this solve the issue for you guys also?

comment:6 Changed 2 years ago by frank

Please don't do this. ICH9 is experimental and will probably show other bugs.

comment:7 in reply to: ↑ 5 Changed 2 years ago by Perryg

Replying to deizel:

We ran into the  same issue - solved by switching chipset emulation from PIIX3 to ICH9.

VBoxManage modifyvm "VM name" --chipset ich9

Does this solve the issue for you guys also?

Sorry, I have not tried the ICH9 chipset in an attempt to work around this issue and wonder why I would have to. Set aside the fact that I have had extremely bad experiences with guests using ICH9, the additional warning when enabling it suggest that the experimental nature of ICH9 is not well supported (yet).

comment:8 Changed 2 years ago by frank

Actually I think we found and fixed this problem in current trunk. The fix is in r41256.

comment:9 Changed 2 years ago by Perryg

Thanks Frank,

I'll build out today and let you know.

comment:10 Changed 2 years ago by Perryg

r41256 Seems to have fixed the issue.

Reboots actually reboot. Thank you!

comment:11 Changed 2 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Thank you Perry for the feedback!

Changed 22 months ago by rschmied

CentOS 6.2 32 Bit crash

Changed 22 months ago by rschmied

CentOS 6.2 VBox Log file

Changed 22 months ago by rschmied

CentOS 6.2 Configuration File

comment:12 Changed 22 months ago by rschmied

I'm seeing exactly the same issue running 4.1.18 and kernel-2.6.32-220.17.1.el6, the current kernel of CentOS 6.2, 32 bit version. The OS / kernel was running w/ a kernel from CentOS 6.1. It was painfully slow compared to a 2.6.18 kernel (b/c my Atom CPU lacks virtualization features and thus the timer calibration failed) but it was at least running w/o crashing. After upgrading to latest CentOS 6.2 packages and kernel the OS crashes (see the attached files centos6-oops.png, VBox.log and centos6.vbox).

Last edited 22 months ago by rschmied (previous) (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use