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 612525 - RHEL 6B2 install bombs out during graphical install on KVM
Summary: RHEL 6B2 install bombs out during graphical install on KVM
Keywords:
Status: CLOSED DUPLICATE of bug 607650
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: x86_64
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
: 613104 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-08 13:05 UTC by Michael De La Rue
Modified: 2013-01-09 22:50 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-22 20:28:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
a full tarball of the contents of the /tmp directory from the crashed server (30.35 KB, application/x-bzip-compressed-tar)
2010-07-08 13:05 UTC, Michael De La Rue 		no flags Details
/tmp files from my first install attempt (30.37 KB, application/x-bzip-compressed-tar)
2010-07-08 15:24 UTC, Michael De La Rue 		no flags Details
View All

Description Michael De La Rue 2010-07-08 13:05:21 UTC 
Created attachment 430341 [details]
a full tarball of the contents of the /tmp directory from the crashed server

Description of problem:
When I try to install RHEL6 beta 2 under RHEL 5.5 in a KVM then 

Version-Release number of selected component (if applicable):
kvm-83-164.el5_5.12
install-cds/RHEL6.0-20100622.1-Workstation-x86_64-DVD1.iso
(SHA266 = 272c6fbf1a423e5bab6fddb101b6a4c96b57bf196fa2b26991f55202e0fa715e)

How reproducible:
Each time tried.  

Steps to Reproduce:
1. virt-install --name=rhel6b2-test2 --ram=1024 --vcpus=1 --os-type=linux --os-variant=rhel6 --accelerate --cdrom=install-cds/RHEL6.0-20100622.1-Workstation-x86_64-DVD1.iso --disk path=/var/lib/libvirt/images/rhel6b2-test2.img,size=10,sparse=false --vnc --force --noautoconsole
2. take defaults all the way through install except tell to take entire disk
3. get to select installation packages ; leave as desktop
4. press next 
5. CRASH
  
Actual results:
install exited abnormally [1/1]

Expected results:
system should install and work

Additional info:
* Text mode install seems to work okay (edit install command line add "nomodeset text" at end).
* The first time I ran this through the X server log showed the X server bombing out.  This time round there is no such thing, but something on console 6 seems to have hung though I can bet back and forward to it.
* I still have the VMs live so can provide access to the server for MM to log in.
Comment 2 Chris Lumens 2010-07-08 13:40:27 UTC 
I don't see anything in your logs that indicates the nature of the problem.  If you're receiving a traceback, can you also make sure /tmp/anaconda-tb-* is attached to this file?  If it's a stack trace, can you attach a screenshot of tty1?
Comment 3 Michael De La Rue 2010-07-08 15:20:38 UTC 
That's a complete dump of /tmp/ there was no more. Also looking at the first console there's nothing between the start of graphical install and the message install exited abnormally [1/1]

On the other hand the VM is still active so if you can suggest how I can trigger the traceback you want I can do that.  

I attempted this install before and had a problem at more or less the same stage though the X server crashed fully.  There is also no /tmp/anaconda-tb-* file there either.  I'm attaching the /tmp files from that as well just in case they provide inspiration.  

Incidentally I should point out that on this machine there are several other VMs, but RHEL 5 and Ubuntu running and they seem to have no problem.
Comment 4 Michael De La Rue 2010-07-08 15:24:26 UTC 
Created attachment 430397 [details]
/tmp files from my first install attempt

I did a previous install.  I'm not sure about the exact procedure used; approximately select workstation and full disk install; this is the set of /tmp files produced that time.  In this case the X server actually crashed out fully.  I suspect that it's just a different symptom of the same root cause, but can't be sure.  

Again, this is all the files from /tmp but the VM is still running if you want e.g. a signal sent to some process or something.
Comment 5 Brian Lane 2010-07-08 18:52:17 UTC 
This may be related to bug 610255
Comment 6 Chris Lumens 2010-07-08 18:53:27 UTC 
What happens if you increase the memory for your VM when doing a graphical install?
Comment 7 Michael De La Rue 2010-07-09 16:08:28 UTC 
With 4096M of memory the install completes and appears successful.
Comment 8 Chris Lumens 2010-07-09 18:56:16 UTC 
*** Bug 613104 has been marked as a duplicate of this bug. ***
Comment 10 Daniel Berrangé 2010-07-15 19:44:23 UTC 
Libvirt doesn't have any bearing on anaconda using too much memory inside the guest. We merely create a KVM virtual machine with the requested amount of RAM. How the guest OS uses that RAM is its own decision.
Comment 11 Dor Laor 2010-07-15 20:50:30 UTC 
It might be another incarnation of Bug 607650 - Install exited abnormally while installing packages. Adding Avi to the CC list. Reported can try the brew build on that bug
Comment 12 Andrea Arcangeli 2010-07-15 21:47:40 UTC 
I agree it worth testing with the fix for bug 607650. I don't think there's a backport to rhel5 host yet but there is a rpm for rhel6 host availabile in bug 607650.
Comment 13 Chris Lumens 2010-07-16 13:55:22 UTC 
Putting in needinfo until we can get results back for comment #11 and #12.
Comment 14 David Cantrell 2010-07-22 19:19:52 UTC 
Dor,

Can we dupe this one against bug #607650?
Comment 15 Dor Laor 2010-07-22 20:28:55 UTC 

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