Bug 229684 - clean install stopped at "Installing kernel-xen-2.6.19-1.2898.2.3.fc7.x86_64"
Summary: clean install stopped at "Installing kernel-xen-2.6.19-1.2898.2.3.fc7.x86_64"
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-xen   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-22 18:35 UTC by ericm24x7
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-19 21:48:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description ericm24x7 2007-02-22 18:35:27 UTC
Description of problem:
performing a clean installation including virtualization package stopped at:
"installing kernel-xen-2.6.19-1.2898.2.3.fc7.x86_64"

Version-Release number of selected component (if applicable):
kernel-xen 2.6.19-1.2898.2.3.fc7.x86_64

How reproducible:

Steps to Reproduce:
1. perform network install
2. select clean installation
2. select "virtualization" package
Actual results:
installation stopped at:
"installing kernel-xen-2.6.19-1.2898.2.3.fc7.x86_64"

Expected results:

Additional info:

Comment 1 Richard W.M. Jones 2007-03-19 14:11:22 UTC

Are you installing Rawhide on the bare metal, or trying to install a Rawhide guest?

In any case, can you attach copies of the following files, to this bug report:
/root/.virt-manager/virt-manager.log (if you have it)

Comment 2 Richard W.M. Jones 2007-03-19 14:23:52 UTC
Sorry, I meant:


Comment 3 ericm24x7 2007-03-19 21:48:25 UTC
I was testing the bare metal xen install. Good news, the latest build (3.19.07)
is  downloading/installing without a problem (continuing at this writing). I
will also test the guest install when I get around to it. Closing this bug for now.

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