Date: Sun, 23 Feb 2014 08:40:21 -0800 From: Peter Grehan <grehan@freebsd.org> To: Willem Jan Withagen <wjw@digiware.nl> Cc: "freebsd-virtualization@freebsd.org" <virtualization@freebsd.org> Subject: Re: Bhyve and Ubuntu booting Message-ID: <530A2475.6090608@freebsd.org> In-Reply-To: <530A20BE.4050602@digiware.nl> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 :) later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?530A2475.6090608>