Re: arm64 metal instances not booting?
On Mon, May 17, 2021 at 12:46:20PM -0700, Jeremy Drake wrote: > > > On Mon, 17 May 2021, Noah Meyerhans wrote: > > > They work, they just take a long, long time to boot. Figure about 10-15 > > minutes or so. > > Thanks, it did eventually boot. It's hard to be patient when you are paying > based on time ;) It may be worth following up with your AWS TAM to get clarification on when billing actually starts. Most of the time spent initializing the system is outside of the customer's control; You can see from dmesg output that the kernel doesn't take particularly long to start. If the resources you've provisioned aren't yet available to you, I don't think you're being billed for them. (Although I work for AWS, I don't have a deep understanding of how billing and metering work.) noah
Re: arm64 metal instances not booting?
On Mon, 17 May 2021, Noah Meyerhans wrote: They work, they just take a long, long time to boot. Figure about 10-15 minutes or so. Thanks, it did eventually boot. It's hard to be patient when you are paying based on time ;)
Re: arm64 metal instances not booting?
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
arm64 metal instances not booting?
Hello, 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 I also tried with m6g.metal, same result. I tried launching a more 'normal' arm64 instance and that was fine. The wiki says that arm64 metal support was added in with the 10.7 update (as of December), so it seems like it should work. I am at a bit of a loss on how to diagnose this, none of the 'monitor and troubleshoot' options seem to work - get system log is blank, and serial console and get screenshot give errors.
