it says there: "I guess this is the patch from XSA-240, you need to boot with
pv-linear-pt=true on the Xen command line" how would that work on aws? can "pv-linear-pt=true" be used in a some .d or .conf file at startup? even if that was possible the only way to do that on aws would be to start mounting root partitions on currently running netbsds. and if you still have enough /dev/xbd*s left. apparently by default there are only up to xbd3*. even if the dmesg shows a new disk attached mounting would be a pain if you already have xbd3 devices mounted... thanks... On Sat, Nov 4, 2017 at 9:40 AM, Chavdar Ivanov <[email protected]> wrote: > 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 <[email protected]> wrote: > >> Hi All, >> >> Mine doesn't work either and rebooting it again does not help:( >> >> Best regards, >> r0ller >> >> -------- Eredeti levél -------- >> Feladó: Abhinav Upadhyay < [email protected] (Link -> mailto: >> [email protected]) > >> Dátum: 2017 november 4 08:05:07 >> Tárgy: Re: NetBSD on Amazon EC2 >> Címzett: Eric Haszlakiewicz < [email protected] (Link -> mailto: >> [email protected]) > >> >> On Sat, Nov 4, 2017 at 2:49 AM, Eric Haszlakiewicz <[email protected]> >> 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 > >
