Mike Larkin wrote:
> On Sat, Dec 04, 2021 at 06:18:55PM +, Claus Assmann wrote:
> > Just in case someone is wondering: vultr moved the VM to a different
> > server, the system is up and running again.
> > BTW: I guess I can ignore this:
> > fd0 at fdc0 drive 1: density unknown
> >
> >
> >
On Sat, Dec 04, 2021 at 06:18:55PM +, Claus Assmann wrote:
> Just in case someone is wondering: vultr moved the VM to a different
> server, the system is up and running again.
> BTW: I guess I can ignore this:
> fd0 at fdc0 drive 1: density unknown
>
>
> OpenBSD 6.9 (GENERIC) #464: Mon Apr 19
Philip Guenther wrote:
> They have your virtualization guest configured in a way that doesn't match
> any real hardware: it has a family-model-stepping combination that matches
> the Skylake line, real hardware of which all have the cflushopt extension,
> but the host is making the guest trap
Just in case someone is wondering: vultr moved the VM to a different
server, the system is up and running again.
BTW: I guess I can ignore this:
fd0 at fdc0 drive 1: density unknown
OpenBSD 6.9 (GENERIC) #464: Mon Apr 19 10:28:56 MDT 2021
On Sat, Dec 4, 2021 at 4:32 AM Claus Assmann
wrote:
> My vultr OpenBSD 6.8 instance crashed and when it tried to reboot it
> failed at:
>
> root on sd0a (...)
> WARNING: / was not properly unmounted
> kernel: privileged instruction fault trap, code=0
> mds_handler_skl_avx+0x33: clflush
My vultr OpenBSD 6.8 instance crashed and when it tried to reboot it
failed at:
root on sd0a (...)
WARNING: / was not properly unmounted
kernel: privileged instruction fault trap, code=0
mds_handler_skl_avx+0x33: clflush __ALIGN_SIZE+0x500(%rid,%rax,8)
I tried to boot from cd{68,69,70}iso but
6 matches
Mail list logo
