Red Hat Bugzilla – Bug 601782
rc.sysinit/S00microcode_ctl causing kernel panic.
Last modified: 2010-11-11 14:30:30 EST
Description of problem:
Build RHEL 6 beta on X3650 M2 system. Created a VM, no issues. Attempting to boot VM fails and hangs at various stages of boot, always with the same result. udev sometimes starts, networking sometimes starts, but it always produces the below error. Very inconsistent when the kernel panic actually happens, but always on boot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot VM.
2. Edit grub to turn off 'rhgb' and 'quiet'
Welcome to RedHat Enterprise Linux
Press 'I' to enter interactive startup.
Starting udev: /etc/rc.d/rc.sysinit: line 316: 417 Killed
init: rcS main process (394) killed by KILL signal
/etc/rc3.d/S00microcode_ctl: line 52: syntax error near unexpected token `}'
/etc/rc3.d/S00microcode_ctl: line 52: `}' Kerne; panic - not syncing: Out of memory and no killable processes...
VM to boot normally!
VM built with the following command:
virt-install --accelerate --hvm --connect qemu:///system --name foo-test --ram 1024 --file=/local/foo-test.img --file-size=6 --vnc --cdrom=/local/RHEL6.0-20100414.0-AP-x86_64-DVD1.iso --network bridge=foobridge
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
The microcode_ctl error is unrelated... perhaps this is the balloon driver bug?
Please try the workaround in bug 591784, particularly the bit about blacklisting virtio_balloon (echo "blacklist virtio_balloon" >> /etc/modprobe.d/blacklist.conf
) and report back if that solves the problem. You may need to boot the VM with the DVD in rescue mode to be able to make this change on the VM filesystem.
Cheers Alex. Definitely a dupe of bug 591784. Blacklisting virtio_balloon worked.
*** This bug has been marked as a duplicate of bug 591784 ***