#11185 Fedora-Rawhide does not boot anymore on Xen AWS instances
Closed: Upstream by zlopez. Opened by mvadkert.

After few days of trying to get to an error message, we confirm the Fedora Rawhide fails to boot on AWS Xen-based instances. On Nitro-based instances it works.

Here is the screenshot from AWS:

i-0e348bd68f622b31c.jpg


@davdunc @kevin @adamwill ^

Is F38 affected?

We are not aware, it was working, I will try to check tmrw

Metadata Update from @jnsamyak:
- Issue priority set to: Waiting on External (was: Needs Review)

@adamwill Fedora 38 is not affected, it works just well.

Is this persisting?

Yep, it is, just verified @humaton

@adamwill this looks like regression, do you need some more info from me?

I don't, but I also can't do anything about it, this is hardly my forte. I guess we need kernel folks and/or amazon folks. @davdunc @jforbes halp?

Reserved this instance:

https://us-east-2.console.aws.amazon.com/ec2/home?region=us-east-2#GetInstanceScreenshot:instanceId=i-01c5c336bf921a37d

provisioned just now on t2.medium with Fedora-Cloud-Base-Rawhide-20230403.n.0.x86_64-hvm-us-east-2-gp2-0

i-01c5c336bf921a37d.jpg

Ok, seems this will now get more eyes:

https://bugzilla.redhat.com/show_bug.cgi?id=2184745

Do we need to keep ticket open here in the fedora-infrastructure queue? or can we close as upstream with the above bugzilla?

Closing as upstream. See https://bugzilla.redhat.com/show_bug.cgi?id=2184745 for more info.

Metadata Update from @zlopez:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

uh, well, the bugzilla is for RHEL, so it's not going to automatically get applied to Fedora too. folks reading that bug may not know we need to fix Fedora as well. @jforbes are you aware of this whole issue? can we do anything that needs doing in Fedora kernels to fix this?

Agreed :) maybe we should clone to Rawhide?

Metadata