Bug 452484 - Exception during xen virtual machine
Exception during xen virtual machine
Status: CLOSED DUPLICATE of bug 445862
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda (Show other bugs)
5.2
All Linux
low Severity low
: rc
: ---
Assigned To: Anaconda Maintenance Team
Martin Jenner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-23 07:18 EDT by Kamlesh Kumar
Modified: 2008-08-29 15:01 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-29 15:01:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Attachment contains all the information about exception. (42.62 KB, text/plain)
2008-06-23 07:18 EDT, Kamlesh Kumar
no flags Details

  None (edit)
Description Kamlesh Kumar 2008-06-23 07:18:10 EDT
Description of problem:
Trying to install xen virtual(Paravirtualized) machine on rhel5 installed
machine. Virtual machin installation gets start but during installation, this
exception occurs.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Exception occurs

Expected results:
Installation should be completed.

Additional info:
Comment 1 Kamlesh Kumar 2008-06-23 07:18:10 EDT
Created attachment 310019 [details]
Attachment contains all the information about exception.
Comment 2 Chris Lalancette 2008-06-23 07:26:38 EDT
This doesn't look like a Xen specific issue.  If anything, it looks possibly
anaconda related, although that first error:

GroupsError: No Groups Available in any repository

Makes me suspect that there are no repositories that it can currently reach. 
I'm going to assign it over to anaconda for now.

Chris Lalancette
Comment 3 Chris Lumens 2008-08-29 15:01:35 EDT

*** This bug has been marked as a duplicate of bug 445862 ***

Note You need to log in before you can comment on or make changes to this bug.