From: Xiao-Yong Jin <meta.jxy@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] kernel crash in bhyve
Date: Thu, 10 Dec 2020 14:37:21 -0600 [thread overview]
Message-ID: <5D95EB31-AA3C-4D20-A314-568A308A4CE2@gmail.com> (raw)
In-Reply-To: <A7E128CB534A0508001E840F35D29F38@felloff.net>
> On Dec 10, 2020, at 5:30 AM, cinap_lenrek@felloff.net wrote:
>
> Btw, would it be possible for you to file a bug
> with bhyve?
>
> I do not have a bsd installation nor do i want to
> subscribe to their mailinglist right now.
>
> The issue is that the mtrr values they give us
> are basically useless.
>
> Qemu, vmware and everyone else gets this right.
>
> The simplest fix might be that they just change
> cpuid to tell the guest that mtrr is not supported.
>
> --
> cinap
I'm not sure I understand the issue completely.
I was using a specific debug switch '-w' in bhyve.
-w Ignore accesses to unimplemented Model Specific
Registers (MSRs). This is intended for debug
purposes.
Because previously, 9front wouldn't boot without this flag.
Now I guess you added more error checking during the boot,
and 9front boots fine without this '-w'. However, without
this '-w' to bhyve, the MTRR code you gave me produces an
error,
rdmsr to register 0xc0010010 on vcpu 0
rdmsr c0010010: bad arg in system call
range 0 1000000000 ( 1000000000) uc
cache 0x0000000000000000 68719476736 uc
It looks like '#P/msr' just cannot be read.
; cat '#P/msr'
cat: error reading #P/msr: bad arg in system call
next prev parent reply other threads:[~2020-12-10 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 18:18 Xiao-Yong Jin
2020-12-09 18:26 ` [9front] " Xiao-Yong Jin
2020-12-09 18:44 ` ori
2020-12-09 19:05 ` [9front] " cinap_lenrek
2020-12-09 19:42 ` Xiao-Yong Jin
2020-12-09 20:52 ` cinap_lenrek
2020-12-09 21:22 ` Xiao-Yong Jin
2020-12-09 22:04 ` cinap_lenrek
2020-12-09 22:36 ` Xiao-Yong Jin
2020-12-09 23:18 ` cinap_lenrek
2020-12-10 0:10 ` Xiao-Yong Jin
2020-12-10 0:45 ` cinap_lenrek
2020-12-10 11:30 ` cinap_lenrek
2020-12-10 20:37 ` Xiao-Yong Jin [this message]
2020-12-10 23:12 ` Nick Owens
2020-12-11 4:55 ` Xiao-Yong Jin
2020-12-11 14:27 ` cinap_lenrek
2020-12-11 1:12 ` ori
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=5D95EB31-AA3C-4D20-A314-568A308A4CE2@gmail.com \
--to=meta.jxy@gmail.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).