Date: Mon, 29 Jan 2024 20:30:12 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 276720] AMIs fail to boot in AWS EC2 Message-ID: <bug-276720-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276720 Bug ID: 276720 Summary: AMIs fail to boot in AWS EC2 Product: Base System Version: 13.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: mgrooms@shrew.net Created attachment 248065 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D248065&action= =3Dedit Stuck boot I can't seem to boot any version of FreeBSD in AWS EC2 at the moment. I tri= ed the non ZFS community AMIs for the following versions ... FreeBSD 12 FreeBSD 13 FreeBSD 14 It seems to get to the point where the network stack initialized as I can p= ing the host, but it looks like it gets stuck shortly after that. I tried a t2.small and several different t3 instance sizes. All of them appear to exh= ibit the same behavior. I tried booting an Amz Linux AMI with the same parameters and connected with ssh immediately after, so I'm quite certain it's not a u= ser error. I've attached a screen shot of the console for a t3.micro instance. It just sits in that stuck state without completing the boot process. When I attemp= t to attach the serial console it just shows jibberish as if there was a baud ra= te mismatch. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276720-227>