From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] vmx(1) vs openbsd
Date: Thu, 25 Jun 2020 21:55:35 -0400 [thread overview]
Message-ID: <20200626015535.V4hnN8QSYXqIUc1qoz0D-gm4lkGBdMTcjuTSHRPPI2w@z> (raw)
In-Reply-To: <61D0EA46F9773C79C149E55F5711DABB@eigenstate.org>
>> http://plan9.stanleylieber.com/hardware/thinkpad/x210/pre-1st-gen-1920x1200/sysinfo
>>
>> vmx -M 2G -n ether0 -d /dev/sdE1/data -v vesa:1280x800 /tmp/bsd.67 device=sd0a
>>
>> http://plan9.stanleylieber.com/vmx/img/20200624.vmx.openbsd67.png
>>
>> vmx(1) itself did not crash. is there something maybe wonky with my machine's
>> support for intel virtualization extensions? i had no trouble booting openbsd
>> on my x250[0], but this is the first time i've tried to boot a local disk
>> guest from a tls-booted host.
>>
>> sl
>>
>> [0] http://plan9.stanleylieber.com/hardware/thinkpad/x250/20cm-cto1ww/sysinfo
>
> xgetbv is an instruction that we probably don't emulate yet.
> Seems to be somethign that OpenBSD calls as part of the
> spectre-class attack mitigations. (Specifically, MDS).
>
> We can probably work around it by lying around cpuid,
> but it'd be better to fix it right. Not sure what that
> means yet.
i believe the last time i booted this openbsd installation in vmx(1) it
was using a slightly older version of the 6.6 kernel. the current 6.6
kernel on the ftp sites (presumably patched?) fails the same way.
sl
prev parent reply other threads:[~2020-06-26 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1251C16DB5CD3CEFEE590AAFCE4C4543@ewsd.inri.net>
2020-06-25 3:48 ` ori
2020-06-25 6:55 ` hiro
2020-06-26 2:56 ` Ori Bernstein
2020-06-26 1:55 ` sl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200626015535.V4hnN8QSYXqIUc1qoz0D-gm4lkGBdMTcjuTSHRPPI2w@z \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).