<div dir="ltr">The given community NetBSD image is working with default EC2 settings for me.<div><br></div><div>It is worth noting that default ssh usernames change by AMI. This may explain why Ubuntu and other images would work. The one for the NetBSD images is <b>root</b>.</div><div><br></div><div>Thus, my ssh command was something like:</div><div><br></div><div>ssh -i ~/.ssh/foo.pem root@bar</div><div><br></div><div>This may be a silly suggestion, but worth ruling it out.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 27, 2020 at 10:50 PM Jan Schaumann <<a href="mailto:jschauma@stevens.edu" target="_blank">jschauma@stevens.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Elliot Wasem <<a href="mailto:ewasem@stevens.edu" target="_blank">ewasem@stevens.edu</a>> wrote:<br>
<br>
> So I tried booting up an ec2 instance with netbsd<br>
> 7.0 from the community ami's with fairly default<br>
> settings. However, it seems to always terminate<br>
> immediately.<br>
<br>
I've seen this when trying to launch an amd64 image on<br>
an i386 instance.<br>
<br>
Make sure the AMI and instance-type are compatible.<br>
If you continue to run into problems, post the details<br>
here (AMI ID, instance type, aws command used to<br>
launch the instance, ...).<br>
<br>
Even if an instance terminates, the console output<br>
might still be useful, so check that as well ('aws ec2<br>
get-console-output').<br>
<br>
-Jan<br>
_______________________________________________<br>
cs615asa mailing list<br>
<a href="mailto:cs615asa@lists.stevens.edu" target="_blank">cs615asa@lists.stevens.edu</a><br>
<a href="https://lists.stevens.edu/mailman/listinfo/cs615asa" rel="noreferrer" target="_blank">https://lists.stevens.edu/mailman/listinfo/cs615asa</a><br>
</blockquote></div>