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-* .
Hi Ronen, could you pls tell is installing a rhel5 with ide and boot it with ahci controller a supported way ? Thanks, Xiaoqing.
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.
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
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