Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 978245

Summary:	install a rhel5 as kvm guest better always build initrd.img with ahci driver(and virtio-blk)
Product:	Red Hat Enterprise Linux 5	Reporter:	Xiaoqing Wei <xwei>
Component:	mkinitrd	Assignee:	Brian Lane <bcl>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.10	CC:	atodorov, dyuan, jherrman, juzhang, lcui, michen, mzhan, qzhang, rhod, shuang, tzheng
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	mkinitrd-5.1.19.6-82	Doc Type:	Bug Fix
Doc Text:	Prior to this update, the Advanced Host Controller Interface (AHCI) driver was not included in the initrd.img file. As a consequence, a Red Hat Enterprise Linux 5 guest in some cases failed to boot on a Red Hat Enterprise Linux 7 hypervisor. With this update, installing Red Hat Enterprise Linux 5 as a guest now always includes the AHCI driver, and the guest is therefore able to boot as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-16 00:23:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Xiaoqing Wei 2013-06-26 07:35:51 UTC

Description of problem:

install a rhel5 as kvm guest better always build initrd.img with ahci driver

Version-Release number of selected component (if applicable):
rhel5.9 GA iso

How reproducible:
100%

Steps to Reproduce:
1.install a rhel5 as kvm guest on rhel7 hypervisor, using ide drive(without -device ahci)
2.boot guest with -device ahci would fail
3.

Actual results:
guest fails to boot, as the initrd.img in guest doesn't have ahci driver.

Expected results:
ahci driver should be included in the guest initrd.img, like virtio-blk
when install a rhel5 as kvm guest with ide controller, it will always include virtio-* drivers in initrd.img.

Additional info:

as RHEL.7 hypervisor would support ahci as drive controller,
and RHEL.5 would continue to be supported for a very long time,
and switching block device controller in a virt environment is quite common useage,
so better always include ahci driver at the installation stage, like virtio-* .

Comment 1 Xiaoqing Wei 2013-07-09 08:51:10 UTC

Hi Ronen,

could you pls tell

is installing a rhel5 with ide and boot it with ahci controller a supported way ?

Thanks,
Xiaoqing.

Comment 3 RHEL Program Management 2014-01-22 16:30:38 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 5 Alexander Todorov 2014-04-16 11:33:03 UTC

Tested with the latest RHEL 5.11 tree 


* Install 5.11 as KVM guest on latest RHEL 7 nightly hypervisor:

Results:
- both ahci.ko and virtio_blk.ko are included in the initrd
- virt-manager uses virtio by default
- after stopping the VM, changing the default disk bus from virtio to IDE and restarting: the VM was able to boot, disk is now /dev/hda instead of /dev/vda


* Install 5.11 as KVM guest on latest RHEL 5.11 nightly hypervisor

Results:
- both ahci.ko and virtio_blk.ko are included in the initrd
- virt-manager uses virtio by default

Comment 7 errata-xmlrpc 2014-09-16 00:23:46 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1224.html