)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":6962,"name":"Kashyap Chamarthy","email":"kchamart@redhat.com","username":"kashyapc"},"change_message_id":"23b5811f6d0275cd5d7f76691ddc70bd5e718bd6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b9aeebee_e0568163","updated":"2021-10-21 15:34:04.000000000","message":"I just learnt that Fedora has not[1] switched the baseline to x86-64-v2.  So the Fedora-34 boot-issues are unrelated to the x86-64-v2.thing.\n\nRegardless, we can try the Nehalem switch to see how it works out.\n\n[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/5EJ7T27EBBSJKMDY2MKCKR5ZIRBCKPJ6/","commit_id":"e06d954229fc4fca827105f5bb0809a19075d590"},{"author":{"_account_id":6962,"name":"Kashyap Chamarthy","email":"kchamart@redhat.com","username":"kashyapc"},"change_message_id":"9cd479cb12a43e3300e9ac805e8a4c749fc900c7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"aebd5731_5f51b24a","updated":"2021-10-25 13:53:01.000000000","message":"I\u0027m late here, but thanks for the quick work!  I\u0027m glad Nehalem at least rescued us here :-)","commit_id":"e06d954229fc4fca827105f5bb0809a19075d590"},{"author":{"_account_id":6962,"name":"Kashyap Chamarthy","email":"kchamart@redhat.com","username":"kashyapc"},"change_message_id":"fdeffc53172e277433bbbf0d88e0521a8ba511f9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"666b6dc4_614b0a8e","updated":"2021-10-21 15:23:11.000000000","message":"Thanks for the quick change.\n\nI\u0027d guess it\u0027s a safe assumption (?) that any hardware older than Nehalem is not capable of running OpenStack.  I can confirm this much:\n\n- Nehalem works with `virt_type\u003dqemu` or `virt_type\u003dkvm`; and\n- it also works on Intel *and* AMD\n","commit_id":"e06d954229fc4fca827105f5bb0809a19075d590"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"64c22db7ea3f3b5524aa86ce7d128b908caecbf8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fc4a7879_f8010155","updated":"2021-10-22 08:57:04.000000000","message":"recheck","commit_id":"e06d954229fc4fca827105f5bb0809a19075d590"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"17de7524407a080478b3a2d24aeffede87819892","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"dca1166e_3a0d889e","updated":"2021-10-21 21:33:21.000000000","message":"recheck I think most of the previous failures were unrelated to the cpu model change. Things like pip not being able to resolve dependencies and nova api being too slow serving metadata requests.","commit_id":"e06d954229fc4fca827105f5bb0809a19075d590"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"eba9d0382ad98051fb31f6fffe372eddd9602942","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8538968c_7e5bdddf","updated":"2021-10-21 18:28:14.000000000","message":"recheck want to run this as much as possible to ensure the various clouds can successfully manage a nehalem cpu.","commit_id":"e06d954229fc4fca827105f5bb0809a19075d590"}]}