RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 601782 - rc.sysinit/S00microcode_ctl causing kernel panic.
Summary: rc.sysinit/S00microcode_ctl causing kernel panic.
Keywords:
Status: CLOSED DUPLICATE of bug 591784
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: x86_64
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-08 15:35 UTC by Tudor Georgescu
Modified: 2010-11-11 19:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-10 14:06:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tudor Georgescu 2010-06-08 15:35:08 UTC 
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):
RHEL6.0-20100414.0-AP-x86_64-DVD1.iso

How reproducible:
Boot VM.

Steps to Reproduce:
1. Boot VM.
2. Edit grub to turn off 'rhgb' and 'quiet'
3. Boot.
  
Actual results:
           Welcome to RedHat Enterprise Linux
           Press 'I' to enter interactive startup.
Starting udev: /etc/rc.d/rc.sysinit: line 316:   417 Killed
/sbin/start_udev
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... 

Expected results:
VM to boot normally!

Additional info:
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
Comment 2 RHEL Program Management 2010-06-08 15:53:37 UTC 
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
inclusion.
Comment 3 Bill Nottingham 2010-06-08 19:07:44 UTC 
The microcode_ctl error is unrelated... perhaps this is the balloon driver bug?
Comment 4 Alex Williamson 2010-06-09 18:33:18 UTC 
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.
Comment 5 Tudor Georgescu 2010-06-10 10:55:51 UTC 
Cheers Alex. Definitely a dupe of bug 591784. Blacklisting virtio_balloon worked.
Comment 6 Alex Williamson 2010-06-10 14:06:04 UTC 

*** This bug has been marked as a duplicate of bug 591784 ***
Note You need to log in before you can comment on or make changes to this bug.