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 993512 - The vm can't be started and show an kernel panic while finished installing a vm with no swap partition on rhel6.5
Summary: The vm can't be started and show an kernel panic while finished installing a ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: virt-mgr-maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-06 05:56 UTC by chentao
Modified: 2013-08-06 08:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-06 08:26:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description chentao 2013-08-06 05:56:04 UTC 
Description of problem:
The vm can't be started and show an kernel panic while finished installing a vm with no swap partition on rhel6.5. But use the physical machine do the uppper installation won't meet this problem.

Version-Release number of selected component (if applicable):
kernel-2.6.32-400.el6.x86_64
qemu-kvm-0.12.1.2-2.382.el6.x86_64
libvirt-0.10.2-21.el6.x86_64
How reproducible:
100%

Steps
1.Prepare to install a guest with rhel6.5 use virt-manager

2.Chose basic storage devices

3.Chose create custom layout,and create two standard partion /boot and /(the file system can be ext3 or ext4),do not create swap partion.

4.Chose Desktop as the default installation of Red Hat Enterprise Linux,then start install.

5.Afer the installation is finished,click reboot.

Actual results:
The vm can't be start with Kernel panic - not syncing : Attempted to kill init!
Pid:1,comm:init Not tainted 2.6.32-358.e16.x86_64 #1
Call Trace:
  [<ffffffff8150cfc8>] ? panic+0xa7/0x16f
  [<ffffffff81073ae2>] ? do_exit+0x862/0x870
  [<ffffffff81182885>] ? fput+0x25/0x30
  [<ffffffff81073b48>] ? do_group_exit+0x58/0xd0
  [<ffffffff81073bd7>] ? sys_exit_group+0x17/0x20
  [<ffffffff8100b072>] ? system_call_fastpath+0x16/0


Expected results:
The vm should be reboot sucessfully.
Comment 2 chentao 2013-08-06 06:27:48 UTC 
The virt-manager version is virt-manager-0.9.0-18.el6.x86_64.
Comment 3 Martin Kletzander 2013-08-06 08:26:43 UTC 
The VM has not enough memory and since the guest has nowhere to swap, OOM killer starts killing processes.  After it has nothing to kill, you get to this point.  The problem is not enough RAM and that is a thing you need to properly configure (change from the default) in case you change the default in the guest.
Note You need to log in before you can comment on or make changes to this bug.