# AMD EpycP / Hyper-v 2022 and Rocky 10

**URL:** <https://forums.rockylinux.org/t/amd-epycp-hyper-v-2022-and-rocky-10/20719>\
**Category:** Rocky Linux Help & Support\
**Created:** [August 6, 2026, 7:15am UTC](https://forums.rockylinux.org/t/amd-epycp-hyper-v-2022-and-rocky-10/20719 "2026-08-06T07:15:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pbrowntwi](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/pbrowntwi/32/2474_2.png) [@pbrowntwi](https://forums.rockylinux.org/u/pbrowntwi)\
**Post date:** [August 6, 2026, 7:15am UTC](https://forums.rockylinux.org/t/amd-epycp-hyper-v-2022-and-rocky-10/20719/1 "2026-08-06T07:15:07Z")

</div>

Has anyone got the combination of Rocky 10 and an AMD EPYC 9354P to install on hyper-v ?

It seems to be telling me that it’s deprecated hardware (detected x86\_64-v1) and won’t proceed past the boot screen.

Rocky 9 has been fine, I just wanted to spin up a fresh box so thought I’d go with 10 and didn’t expect problems with such recent hardware (should be Zen 4 so support _x86-64-v4 ?)_.

Thanks

---

<div class="post-metadata">

**Author:** ![pbrowntwi](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/pbrowntwi/32/2474_2.png) [@pbrowntwi](https://forums.rockylinux.org/u/pbrowntwi)\
**Post date:** [August 6, 2026, 7:28am UTC](https://forums.rockylinux.org/t/amd-epycp-hyper-v-2022-and-rocky-10/20719/2 "2026-08-06T07:28:20Z")

</div>

Ok, we normally turn on the option to allow migration to a physical computer with a different architecture. Turning that off gets me past the initial problem and to a boot screen

---

<div class="post-metadata">

**Author:** ![Avery.Price71](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Avery.Price71](https://forums.rockylinux.org/u/Avery.Price71)\
**Post date:** [August 14, 2026, 7:06am UTC](https://forums.rockylinux.org/t/amd-epycp-hyper-v-2022-and-rocky-10/20719/3 "2026-08-14T07:06:37Z")

</div>

The `x86_64-v1` message looks like Hyper-V is presenting the VM with a restricted or compatibility CPU feature set, rather than Rocky 10 misidentifying the physical EPYC 9354P. Since disabling the migration-to-a-physical-computer option lets you reach the boot screen, I would compare the VM’s virtual processor compatibility setting and CPUID exposure with the Rocky 9 VM that already works. It may also be worth creating a fresh Generation 2 VM and checking that Secure Boot is using the Microsoft UEFI CA template, while keeping the virtual CPU configuration consistent. After you reach the installer, does the live environment report the expected x86-64-v2/v3 CPU level?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [October 13, 2026, 7:07am UTC](https://forums.rockylinux.org/t/amd-epycp-hyper-v-2022-and-rocky-10/20719/4 "2026-10-13T07:07:34Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.