Mike Larkin <mlar...@azathoth.net> wrote: > On Thu, Aug 02, 2018 at 09:22:53AM +0200, Nulani t'Acraya wrote: > > Hello, > > > > Something similar also appears to also be affecting bhyve, at least on an > > AMD Opteron 4228 HE. The error produced is different depending on > > whether bhyve is instructed to ignore accessed to model specific registers > > that are not implemented in the current CPU. I haven't had to have that flag > > toggled previously. I've included the dmesg and trace from both setups > > below. > > > > A snapshot of -current with a build date of 1533181438 - Thu Aug 2 03:43:58 > > UTC 2018 boots successfully with ignore_bad_msr set to on. I'm not entirely > > sure if Bryan's patch will have made it into that snapshot or not, but > > if it has, > > it appears to also be fixing the issue on bhyve. Thanks! > > > > Sincerely, > > Nulani. > > > > The problem is not ignoring access to bad MSRs. > > The problem is that these hypervisors dont know that the MSR we are accessing > is > indeed a real, valid MSR. And then they panic.
Indeed. AMD said their hardware has this chicken bit in a specific MSR. It was previously undocumented. The hypervisors have a whitelist of MSR, and this MSR is not listed, and instead blocked. The hypervisors need to be updated. The people who run that code can tell them to do so.
