On Mon, May 17, 2021 at 11:35:42AM -0700, Jeremy Drake wrote: > I am attempting to launch a c6g.metal instance in us-west-2, but it hangs up > and never seems to boot, with: > ami-0a773686fc288ee18 > ami-054ec2aaf512d49c5 > ami-0bb3ac1447646faf5
They work, they just take a long, long time to boot. Figure about 10-15 minutes or so. Note that the below output is from one of the daily buster AMIs, but the kernel and other relevant boot components are identical to the current release AMIs: admin@ip-10-0-0-56:~$ uname -a Linux ip-10-0-0-56 4.19.0-16-arm64 #1 SMP Debian 4.19.181-1 (2021-03-19) aarch64 GNU/Linux admin@ip-10-0-0-56:~$ ec2metadata --ami-id ami-0d7d3a0ba9c1909f4 admin@ip-10-0-0-56:~$ ec2metadata --instance-type c6g.metal admin@ip-10-0-0-56:~$ lscpu Architecture: aarch64 Byte Order: Little Endian CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 1 Core(s) per socket: 64 Socket(s): 1 NUMA node(s): 1 Vendor ID: ARM Model: 1 Stepping: r3p1 BogoMIPS: 243.75 L1d cache: 64K L1i cache: 64K L2 cache: 1024K L3 cache: 32768K NUMA node0 CPU(s): 0-63 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs noah
