I’m running Cloudstack 4.17.1.0 and for unknown reasons, I’m having issues running Rocky 9. Kernel begins to boot and then it looks like it fails on loading initrd and I get a kernel oops. Just curious if this is a known issue or if there’s a work around. I tried using the qcow2 image from Rocky as well and just using the install iso to create a new image. Same result.
Rocky 8 works fine.
Thanks -jeremy
In an effort to troubleshoot this, I decided to launch a Rocky 8 vm and do a manual upgrade to Rocky 9. While I understand this isn’t recommended, I thought perhaps it would reveal what the issue are. After I started doing package upgrade, I noticed this:
Fatal glibc error: CPU does not support x86-64-v2
I suspect this is the root of my issues. Can anyone explain this further?
Thanks -jeremy
On Friday, Dec 09, 2022 at 8:13 PM, Jeremy Hansen <jeremy@skidrow.la (mailto:jeremy@skidrow.la)> wrote: I’m running Cloudstack 4.17.1.0 and for unknown reasons, I’m having issues running Rocky 9. Kernel begins to boot and then it looks like it fails on loading initrd and I get a kernel oops. Just curious if this is a known issue or if there’s a work around. I tried using the qcow2 image from Rocky as well and just using the install iso to create a new image. Same result.
Rocky 8 works fine.
Thanks -jeremy
Rocky Linux 9 has a hard requirement on x86-64-v2. If the processor does not support it, system won't boot nor run. There's no workarounds as this is built into glibc.
What I would do is verify that the host supports x86-64-v2. You can do this by running something like:
/lib64/ld-linux-x86-64.so.2 --help | grep supported
If x86-64-v2 shows as supported, then the host CPU will work for 9. It'll be a matter of configuring your VM's to use the host CPU instead of emulating another. (Eg in KVM you'd use --cpu host on the CLI).
On Sat, Dec 10, 2022, 13:25 Jeremy Hansen via rocky rocky@lists.resf.org wrote:
In an effort to troubleshoot this, I decided to launch a Rocky 8 vm and do a manual upgrade to Rocky 9. While I understand this isn’t recommended, I thought perhaps it would reveal what the issue are. After I started doing package upgrade, I noticed this:
Fatal glibc error: CPU does not support x86-64-v2
I suspect this is the root of my issues. Can anyone explain this further?
Thanks -jeremy
On Friday, Dec 09, 2022 at 8:13 PM, Jeremy Hansen jeremy@skidrow.la wrote: I’m running Cloudstack 4.17.1.0 and for unknown reasons, I’m having issues running Rocky 9. Kernel begins to boot and then it looks like it fails on loading initrd and I get a kernel oops. Just curious if this is a known issue or if there’s a work around. I tried using the qcow2 image from Rocky as well and just using the install iso to create a new image. Same result.
Rocky 8 works fine.
Thanks -jeremy
rocky mailing list -- rocky@lists.resf.org To unsubscribe send an email to rocky-leave@lists.resf.org
Looks like it’s supported by the host hardware on my CS hosts:
[root@netman ~]# cexecs cs: "/lib64/ld-linux-x86-64.so.2 --help | grep x86-64-v2" ************************ cs ************************ --------- cm01--------- x86-64-v2 (supported, searched) --------- cm02--------- x86-64-v2 (supported, searched) --------- cn04--------- x86-64-v2 (supported, searched) --------- cn05--------- x86-64-v2 (supported, searched) --------- cn06--------- x86-64-v2 (supported, searched) --------- cn07--------- x86-64-v2 (supported, searched)
I am running KVM. Any idea how to incorporate using the ‘—cpu host’ option in a Cloudstack environment?
Thanks!
On Saturday, Dec 10, 2022 at 3:35 PM, Louis Abel via rocky <rocky@lists.resf.org (mailto:rocky@lists.resf.org)> wrote: Rocky Linux 9 has a hard requirement on x86-64-v2. If the processor does not support it, system won't boot nor run. There's no workarounds as this is built into glibc.
What I would do is verify that the host supports x86-64-v2. You can do this by running something like:
/lib64/ld-linux-x86-64.so.2 --help | grep supported
If x86-64-v2 shows as supported, then the host CPU will work for 9. It'll be a matter of configuring your VM's to use the host CPU instead of emulating another. (Eg in KVM you'd use --cpu host on the CLI).
On Sat, Dec 10, 2022, 13:25 Jeremy Hansen via rocky <rocky@lists.resf.org (mailto:rocky@lists.resf.org)> wrote:
In an effort to troubleshoot this, I decided to launch a Rocky 8 vm and do a manual upgrade to Rocky 9. While I understand this isn’t recommended, I thought perhaps it would reveal what the issue are. After I started doing package upgrade, I noticed this:
Fatal glibc error: CPU does not support x86-64-v2
I suspect this is the root of my issues. Can anyone explain this further?
Thanks -jeremy
On Friday, Dec 09, 2022 at 8:13 PM, Jeremy Hansen <jeremy@skidrow.la (mailto:jeremy@skidrow.la)> wrote: I’m running Cloudstack 4.17.1.0 and for unknown reasons, I’m having issues running Rocky 9. Kernel begins to boot and then it looks like it fails on loading initrd and I get a kernel oops. Just curious if this is a known issue or if there’s a work around. I tried using the qcow2 image from Rocky as well and just using the install iso to create a new image. Same result.
Rocky 8 works fine.
Thanks -jeremy
rocky mailing list -- rocky@lists.resf.org (mailto:rocky@lists.resf.org) To unsubscribe send an email to rocky-leave@lists.resf.org (mailto:rocky-leave@lists.resf.org)
rocky mailing list -- rocky@lists.resf.org To unsubscribe send an email to rocky-leave@lists.resf.org
I believe this page explains how to do that: https://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.htm...
If I had to guess, setting guest.cpu.mode to "host-passthrough" will likely get you there. But if you have different varying hardware, "host-model" might be the better pick.
On Sat, 10 Dec 2022 at 13:40, Jeremy Hansen via rocky rocky@lists.resf.org wrote:
Looks like it’s supported by the host hardware on my CS hosts:
[root@netman ~]# cexecs cs: "/lib64/ld-linux-x86-64.so.2 --help | grep x86-64-v2" ************************ cs ************************ --------- cm01--------- x86-64-v2 (supported, searched) --------- cm02--------- x86-64-v2 (supported, searched) --------- cn04--------- x86-64-v2 (supported, searched) --------- cn05--------- x86-64-v2 (supported, searched) --------- cn06--------- x86-64-v2 (supported, searched) --------- cn07--------- x86-64-v2 (supported, searched)
I am running KVM. Any idea how to incorporate using the ‘—cpu host’ option in a Cloudstack environment?
Thanks!
On Saturday, Dec 10, 2022 at 3:35 PM, Louis Abel via rocky < rocky@lists.resf.org> wrote: Rocky Linux 9 has a hard requirement on x86-64-v2. If the processor does not support it, system won't boot nor run. There's no workarounds as this is built into glibc.
What I would do is verify that the host supports x86-64-v2. You can do this by running something like:
/lib64/ld-linux-x86-64.so.2 --help | grep supported
If x86-64-v2 shows as supported, then the host CPU will work for 9. It'll be a matter of configuring your VM's to use the host CPU instead of emulating another. (Eg in KVM you'd use --cpu host on the CLI).
On Sat, Dec 10, 2022, 13:25 Jeremy Hansen via rocky rocky@lists.resf.org wrote:
In an effort to troubleshoot this, I decided to launch a Rocky 8 vm and do a manual upgrade to Rocky 9. While I understand this isn’t recommended, I thought perhaps it would reveal what the issue are. After I started doing package upgrade, I noticed this:
Fatal glibc error: CPU does not support x86-64-v2
I suspect this is the root of my issues. Can anyone explain this further?
Thanks -jeremy
On Friday, Dec 09, 2022 at 8:13 PM, Jeremy Hansen jeremy@skidrow.la wrote: I’m running Cloudstack 4.17.1.0 and for unknown reasons, I’m having issues running Rocky 9. Kernel begins to boot and then it looks like it fails on loading initrd and I get a kernel oops. Just curious if this is a known issue or if there’s a work around. I tried using the qcow2 image from Rocky as well and just using the install iso to create a new image. Same result.
Rocky 8 works fine.
Thanks -jeremy
rocky mailing list -- rocky@lists.resf.org To unsubscribe send an email to rocky-leave@lists.resf.org
rocky mailing list -- rocky@lists.resf.org To unsubscribe send an email to rocky-leave@lists.resf.org
rocky mailing list -- rocky@lists.resf.org To unsubscribe send an email to rocky-leave@lists.resf.org
Yes. Someone clued me in on the Cloudstack list and all is well now. Thank you!
-jeremy
On Saturday, Dec 10, 2022 at 8:31 PM, Louis Abel via rocky <rocky@lists.resf.org (mailto:rocky@lists.resf.org)> wrote: I believe this page explains how to do that: https://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.htm...
If I had to guess, setting guest.cpu.mode to "host-passthrough" will likely get you there. But if you have different varying hardware, "host-model" might be the better pick. On Sat, 10 Dec 2022 at 13:40, Jeremy Hansen via rocky <rocky@lists.resf.org (mailto:rocky@lists.resf.org)> wrote:
Looks like it’s supported by the host hardware on my CS hosts:
[root@netman ~]# cexecs cs: "/lib64/ld-linux-x86-64.so.2 --help | grep x86-64-v2" ************************ cs ************************ --------- cm01--------- x86-64-v2 (supported, searched) --------- cm02--------- x86-64-v2 (supported, searched) --------- cn04--------- x86-64-v2 (supported, searched) --------- cn05--------- x86-64-v2 (supported, searched) --------- cn06--------- x86-64-v2 (supported, searched) --------- cn07--------- x86-64-v2 (supported, searched)
I am running KVM. Any idea how to incorporate using the ‘—cpu host’ option in a Cloudstack environment?
Thanks!
On Saturday, Dec 10, 2022 at 3:35 PM, Louis Abel via rocky <rocky@lists.resf.org (mailto:rocky@lists.resf.org)> wrote: Rocky Linux 9 has a hard requirement on x86-64-v2. If the processor does not support it, system won't boot nor run. There's no workarounds as this is built into glibc.
What I would do is verify that the host supports x86-64-v2. You can do this by running something like:
/lib64/ld-linux-x86-64.so.2 --help | grep supported
If x86-64-v2 shows as supported, then the host CPU will work for 9. It'll be a matter of configuring your VM's to use the host CPU instead of emulating another. (Eg in KVM you'd use --cpu host on the CLI).
On Sat, Dec 10, 2022, 13:25 Jeremy Hansen via rocky <rocky@lists.resf.org (mailto:rocky@lists.resf.org)> wrote:
In an effort to troubleshoot this, I decided to launch a Rocky 8 vm and do a manual upgrade to Rocky 9. While I understand this isn’t recommended, I thought perhaps it would reveal what the issue are. After I started doing package upgrade, I noticed this:
Fatal glibc error: CPU does not support x86-64-v2
I suspect this is the root of my issues. Can anyone explain this further?
Thanks -jeremy
On Friday, Dec 09, 2022 at 8:13 PM, Jeremy Hansen <jeremy@skidrow.la (mailto:jeremy@skidrow.la)> wrote: I’m running Cloudstack 4.17.1.0 and for unknown reasons, I’m having issues running Rocky 9. Kernel begins to boot and then it looks like it fails on loading initrd and I get a kernel oops. Just curious if this is a known issue or if there’s a work around. I tried using the qcow2 image from Rocky as well and just using the install iso to create a new image. Same result.
Rocky 8 works fine.
Thanks -jeremy
rocky mailing list -- rocky@lists.resf.org (mailto:rocky@lists.resf.org) To unsubscribe send an email to rocky-leave@lists.resf.org (mailto:rocky-leave@lists.resf.org)
rocky mailing list -- rocky@lists.resf.org (mailto:rocky@lists.resf.org) To unsubscribe send an email to rocky-leave@lists.resf.org (mailto:rocky-leave@lists.resf.org)
rocky mailing list -- rocky@lists.resf.org (mailto:rocky@lists.resf.org) To unsubscribe send an email to rocky-leave@lists.resf.org (mailto:rocky-leave@lists.resf.org)
--
-L _______________________________________________ rocky mailing list -- rocky@lists.resf.org To unsubscribe send an email to rocky-leave@lists.resf.org
On Sun, 11 Dec 2022, Jeremy Hansen via rocky wrote:
Yes. Someone clued me in on the Cloudstack list and all is well now. Thank you!
I realize Jeremy's original question has been answered, so I add this bit only for folks who end up here via search engine at a later date.
To get Rocky 9 to run in UTM, a Mac virtualization application, I had to launch the VM with the "Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-7.0) (q35)" machine definition.
There are perhaps other UTM machine definitions that work as well, but the default machine type didn't support x86-64-v2 and would not run Rocky 9.
-
Jeremy Hansen -
Louis Abel -
Paul Heinlein