aboutsummaryrefslogtreecommitdiff
path: root/src/include/ipxe/efi/Uefi
diff options
context:
space:
mode:
authorMichael Brown <mcb30@ipxe.org>2023-11-07 18:05:45 +0000
committerMichael Brown <mcb30@ipxe.org>2023-11-07 18:05:45 +0000
commit77b07ea4fdc259d7253c6f9df2beda6e6c7a9d85 (patch)
tree1bfef5dcace38b30337edad88d6f605c9fc8e89b /src/include/ipxe/efi/Uefi
parentd8f9c221ede6d67a251134989a30bb850f8709e6 (diff)
downloadipxe-77b07ea4fdc259d7253c6f9df2beda6e6c7a9d85.zip
ipxe-77b07ea4fdc259d7253c6f9df2beda6e6c7a9d85.tar.gz
ipxe-77b07ea4fdc259d7253c6f9df2beda6e6c7a9d85.tar.bz2
[cloud] Add utility script to read iPXE output from INT13CON partition
Some AWS instance types still do not support serial console output or screenshots. For these instance types, the only viable way to extract debugging information is to use the INT13 console (which is already enabled via CONFIG=cloud for all AWS images). Obtaining the INT13 console output can be very cumbersome, since there is no direct way to read from an AWS volume. The simplest current approach is to stop the instance under test, detach its root volume, and reattach the volume to a Linux instance in the same region. Add a utility script aws-int13con to retrieve the INT13 console output by creating a temporary snapshot, reading the first block from the snapshot, and extracting the INT13 console partition content. Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/include/ipxe/efi/Uefi')
0 files changed, 0 insertions, 0 deletions