Comment 10 for bug 2060992

Revision history for this message
Seth Carolan (secarola) wrote :

Batch tested the proposed kernel for Jammy 6.5 and achieved 99+% success rate on CLI/console initiated Hibernate/Resumes. Complete batch tests across all ARM supported instance types ran previously, limited this test to the M6g family as confirmation.

High level testing details:
1.) Spun up instance with patched AMI + this hibinit-agent ppa (https://launchpad.net/~mitchdz/+archive/ubuntu/ec2-hibinit-agent-arm).
2.) Started up bashscript "heartbeat" on the instance, pushing timestamp to dynamoDB table every 30 seconds.
3.) Hibernated instance through the AWS CLI
4.) Resumed instance through the AWS CLI
5.) Confirmed "heartbeat" updates to dynamoDB table after resume
6.) Repeated once more.

Manually tested instance initiated hibernation successfully:
High level testing details:
1.) Spun up instance with patched AMI + this hibinit-agent patch (https://git.launchpad.net/~secarola/ubuntu/+source/ec2-hibinit-agent/commit/?h=applied/ubuntu/jammy-devel&id=034ec3ffdc8cbd9d319aa5815f02d60ec3e27f93).
2.) Connected to the instance and started up bash script "heartbeat" on the instance, writing to text file every second with new timestamp.
#!/bin/bash
while :
do
        echo $(date) > text.txt
        sleep 1
done
3.) Hibernated instance through the GuestOS.
sudo swapon --priority=32767 /swap-hibinit
sudo systemctl hibernate
4.) Confirmed that hosting environments reported the instance as Hibernated and not shutdown.
4.) Resumed instance through the AWS CLI
5.) Connected to the instance and confirmed the date was still being written to the text file
cat text.txt