Please check the following thread: http://mail-index.netbsd.org/port-xen/2017/10/23/msg009097.html
Chavdar Ivanov On Sat, 4 Nov 2017 at 13:03 r0ller <r0l...@freemail.hu> wrote: > Hi All, > > Mine doesn't work either and rebooting it again does not help:( > > Best regards, > r0ller > > -------- Eredeti levél -------- > Feladó: Abhinav Upadhyay < er.abhinav.upadh...@gmail.com (Link -> mailto: > er.abhinav.upadh...@gmail.com) > > Dátum: 2017 november 4 08:05:07 > Tárgy: Re: NetBSD on Amazon EC2 > Címzett: Eric Haszlakiewicz < haw...@gmail.com (Link -> mailto: > haw...@gmail.com) > > > On Sat, Nov 4, 2017 at 2:49 AM, Eric Haszlakiewicz <haw...@gmail.com> > wrote: > > Up until today I was running a NetBSD server on Amazon's EC2 service, > > but then I restarted it because Amazon told me they'd be forcing a > > restart soon anyway, to "deploy important updates". > > Of course, when I tried to start it back up, it failed. Trying to > > start a brand new instance using the available NetBSD AMIs > > (NetBSD-i386-7.0-201511211930Z-20151121-1234 (ami-9f8090fe)) also > > fails in a similar way, specifically with errors like: > > > > Failed to read /local/domain/0/backend/vbd/7994/2050/feature-barrier. > > Failed to read /local/domain/0/backend/vbd/7994/2050/feature-flush-cache. > > and > > xc_dom_probe_bzimage_kernel: kernel is not a bzImage > > > > Do these errors ring a bell with anyone? > > Does anyone have a working AMI that I can use? > Yes, my instance also was rebooted last night (automatically by AWS > for maintenance) and now unreachable. No idea how to get it back. > (Didn't try creating new instance) > - > Abhinav
