Date: Wed, 1 Jun 2016 07:53:51 +0200 From: "Bradley T. Hughes" <bradleythughes@fastmail.fm> To: Seo Townsend <seotownsend@icloud.com> Cc: freebsd-cloud@freebsd.org Subject: Re: EC2 won't load with FreeBSD AMI Message-ID: <AA885028-D701-4933-9FF3-DFFAD2D79CEE@fastmail.fm> In-Reply-To: <C7E0AB48-5C08-49C5-9202-8C3312E514D4@icloud.com> References: <C7E0AB48-5C08-49C5-9202-8C3312E514D4@icloud.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 01 Jun 2016, at 06:00, Seo Townsend <seotownsend@icloud.com> wrote: >=20 > Trying to load FreeBSD on AWS with no luck=E2=80=A6 I=E2=80=99ve used = FreeBSD on AWS for ages and never ran into issues :/ >=20 > When I go to view the emulated monitor output on AWS, it=E2=80=99s = stuck at: >=20 > Loading /boot/defaults/loader.conf > / >=20 > ...Any Ideas? :/ > I=E2=80=99ve tried this on the 10.2 and 10.3 (official) AMIs on = several instance types. I wanted to start off saying that it works for me. I just booted a = t2.micro instance in eu-west-1 using ami-a2f87fd1 (10.3-RELEASE amd64 = hvm). The system log output from the AWS console usually lags behind. Is the = instance reachable via its public IP? (If it has one, and assuming = security group rules to allow incoming traffic.) -- Bradley T. Hughes bradleythughes@fastmail.fm
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AA885028-D701-4933-9FF3-DFFAD2D79CEE>