Date: Sun, 23 Feb 2014 17:51:31 +0100 From: Willem Jan Withagen <wjw@digiware.nl> To: Peter Grehan <grehan@freebsd.org> Cc: "freebsd-virtualization@freebsd.org" <virtualization@freebsd.org> Subject: Re: Bhyve and Ubuntu booting Message-ID: <530A2713.6000602@digiware.nl> In-Reply-To: <530A2475.6090608@freebsd.org> References: <53090599.5000505@digiware.nl> <CAG=rPVdtQX32pvxNPo9SqRb3q7zQSTopD2qXnSDer0NvEq2kiw@mail.gmail.com> <20AAA4CA-38F9-4D07-BAAA-434F8BC20129@digiware.nl> <CAG=rPVd50JwE9No0SSsgT83nM=DNzLdhCN6ws2QHiawOqi7DDQ@mail.gmail.com> <530A20BE.4050602@digiware.nl> <530A2475.6090608@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23-2-2014 17:40, Peter Grehan wrote: >> vm exit rdmsr 0xc0010015, cpu 0 >> --- >> >> And I've seen discussions in other threads about reading/writing cpu >> registers where some bits should be 0, but trap when being set.... >> (Or something close to this...???) >> >> So it could again be due to the amdsrc tree differences? > > It's Linux accessing different MSRs on AMD as opposed to Intel. There > is an option to ignore unknown MSRs with bhyve, but that probably > shouldn't be used on AMD systems until we've worked out if the MSRs need > to be emulated or not. Hopefully that will be in the next updated :) It's a toy box here so if anything needs to be tested, worked out. Just let me know. And I'm willing to run the risk of lost work, because using the ignore option bites me.... So if you want me to see how we fare, .. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?530A2713.6000602>