Comment 6 for bug 1968062

Performing verification for Jammy.

I started one of each of the below instance types, trying to cover one of all Xen based instance types:

c3.large, c4.large, i3.large, m3.medium, m4.large, r3.large, r4.large, t2.medium.

Each instance had between 20 to 30gb of encrypted storage, and hibernation was enabled in advanced settings.

From there, I enabled -proposed, installed the 5.15.0-1019-aws kernel and rebooted.

I checked to make sure the /swap-hibinit file was generated and the correct size.

I started a screen session, and echod some text. I detached screen and logged out.

I then used the AWS EC2 UI to Hibernate each instance. I waited a minute for each instance to move to the stopped state.

From there I started all instances.

I ssh'd into all instances and resumed my screen session.

All instance types with the 5.15.0-1019-aws kernel had successfully hibernated and resumed, and my screen session was intact.

In my basic testing, the 5.15.0-1019-aws kernel can successfully hibernate and resume on all Xen instance types. Happy to mark as verified.