RHEL 5.8 64bit support on Azure or Hyper-V

Latest response

Hi Guys,

We are trying to create RHEL 5.8 on Azure, since there is no Azure Marketplace vm available so we have downloaded RHEL 5.8 ISO from redhat official site and created custom VM image but unfortunately Hyper-V doesn't seems let access my Network card.

Also failed to install LIS on RHEL 5.8 64bit.

error: Failed dependencies:
kernel < 2.6.18-165 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_kernel_ga) = 84d69198cf51b494e38d9d0a54e52607c8a507e2 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_drivers_base_ga) = 61dc730b8ca5e74017f2df5b55ecda8b7df7f9c2 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_vmlinux_ga) = 78f928da689a93ecf2e044fc0ced6b3eaedf5c19 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_fs_ga) = 1c422a6b84a2000991b1b99c61506cfd711a20d1 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_drivers_video_ga) = a2b696de763cab21944e1e98f127d6cdc163d762 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_net_core_ga) = c186a7dc043c903564c2dd9ed49d8847b7043c86 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_mm_ga) = d5edc1b3d2a4f2bf8ce28d7f4dbeab27cfeb19bd is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_drivers_scsi_ga) = 1cc16b1f8996d37eaa858690bfbab7f4030c55b6 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_drivers_pci_ga) = 88a9a7f6575f2f00a7ca4ac83a9f3a2c81641290 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_net_ethernet_ga) = d17ace18cf21997af17e0b1057679e4819e5b1fc is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_net_ipv4_ga) = 5f159ec8729b8777d27407ddd6cf485fa3d960f3 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_lib_ga) = ff25b583d6d314edd98f7c9533c5867194b3d30d is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_net_core_u4) = 0971fc19326374d80187da0f9e0ad6a0a44e358c is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_drivers_input_ga) = 6721f62837b422dedc38ac8d1e8b4d862ec2b473 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_fs_debugfs_ga) = 805b85b7314d1d795a6ab61313070217939fb54f is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_arch_x86_64_kernel_ga) = 880dbfce5086d666f5bab6ad642c0323fcdabd90 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_drivers_acpi_u4) = 2ea0b770166607af80ae50ea034caebee6a1e08a is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_fs_nls_ga) = 0a7be2859d1a992e0c363811f8fd3a099a8b3ac3 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_net_sched_ga) = f59ed7ca1ff4a5999cc750181083f8e6dd78c491 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_block_ga) = 5b4effd1cc3809b4bd243e499ab6be486fd95fd9 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_drivers_char_ga) = f226911057872ff1aec3f38ff138e7004af9345d is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_arch_x86_64_mm_ga) = ca7f91963b9397351659241974f92dc85546f8ca is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_arch_x86_64_kernel_u2) = 12cc0c2f515fd81b2da9071974dc948e339f09cd is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_drivers_xen_core_ga) = c05a8027c47f037b99169c7441da64fa0a723869 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
kernel(rhel5_kernel_module_ga) = a74a9d2bf87d13d6b9412698dc2728248ca92523 is needed by kmod-microsoft-hyper-v-4.1.3.2-20170310.x86_64
Kmod RPM installation failed, Exiting

Responses

I know this isn't the response you were looking for, and I hate to be "that guy", but...

Why are you exerting effort on an OS that exited "Support 2" over a year ago? I mean, we're already advising our business units that haven't already gone to production, "don't deploy on RHEL 6, it exits Support 2 in under three years". RHEL 5 was problematic on legacy virtualization environments. You go to modern cloud contexts and you really lose out on many of those environments' features (as you're seeing with your driver issues).

RHEL 5 is not one of the Linux distributions endorsed by Microsoft for Azure. That support started with RHEL 6.7. Our own Azure support matrix says the same thing. Hyper-V and Azure just weren't designed with RHEL5 in mind.

If all you need is the network, you could probably use the "legacy" network adapter which Hyper-V provides. I believe that's an emulation of the old DEC Tulip which is very sub-optimal for modern workloads. You may be able to overwhelm that emulated hardware with offloading and need to disable the offloading features. However the tulip driver should be in RHEL5. That code hasn't seen updates for a decade or more.

I also agree with Thomas above. You shouldn't be installing new RHEL5 systems now. You need the ELS entitlement to install new RHEL5 and remain supported. You probably shouldn't even be installing new RHEL6 now, as that's only got a couple of years before it transitions to the Extended Life Phase too.

You can learn more about the RHEL lifecycle at: https://access.redhat.com/support/policy/updates/errata/

I also strongly recommend you get your organisation to consider RHEL 7 - the current "Full Support phase" release - if at all possible.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.