On 18/08/17 16:55, Konrad Rzeszutek Wilk wrote:
> On Wed, Aug 16, 2017 at 06:47:23PM +, Andri Möll wrote:
>
>> (d1) Invoking OVMF ...
>> (XEN) MMIO emulation failed: d1v0 16bit @ f000:ff54 -> 66 ea 5c ff ff ff
>> 10 00 b8 40 06 00 00 0f 22
> That code is:
> cripts/decodecode
> Code: 66
On Wed, Aug 16, 2017 at 06:47:23PM +, Andri Möll wrote:
> Hey,
>
> As per Andrew [Cooper]'s suggestion, writing here instead of #xen on
> Freenode.
>
> I'm trying out Xen (4.9.0) with OVMF (r21243.3858b4a1ff-1) and having it
OK, so this is
ommit 3858b4a1ff09d3243fea8d07bd135478237cb8f7
On Thu, 17 Aug 2017 11:56:06 +0100
Andrew Cooper wrote:
> On 17/08/17 09:49, Jan Beulich wrote:
> On 16.08.17 at 20:47, wrote:
> >> Hey,
> >>
> >> As per Andrew [Cooper]'s suggestion, writing here instead of #xen on
> >> Freenode.
> >>
> >> I'm
On 17/08/17 09:49, Jan Beulich wrote:
On 16.08.17 at 20:47, wrote:
>> Hey,
>>
>> As per Andrew [Cooper]'s suggestion, writing here instead of #xen on
>> Freenode.
>>
>> I'm trying out Xen (4.9.0) with OVMF (r21243.3858b4a1ff-1) and having it
>> crash right on boot both with
On Wed, Aug 16, 2017 at 06:47:23PM +, Andri Möll wrote:
> Hey,
>
> As per Andrew [Cooper]'s suggestion, writing here instead of #xen on
> Freenode.
>
> I'm trying out Xen (4.9.0) with OVMF (r21243.3858b4a1ff-1) and having it
> crash right on boot both with the 32b and 64b OVMF binaries. This
>>> On 16.08.17 at 20:47, wrote:
> Hey,
>
> As per Andrew [Cooper]'s suggestion, writing here instead of #xen on
> Freenode.
>
> I'm trying out Xen (4.9.0) with OVMF (r21243.3858b4a1ff-1) and having it
> crash right on boot both with the 32b and 64b OVMF binaries. This is on
>
Hey,
As per Andrew [Cooper]'s suggestion, writing here instead of #xen on
Freenode.
I'm trying out Xen (4.9.0) with OVMF (r21243.3858b4a1ff-1) and having it
crash right on boot both with the 32b and 64b OVMF binaries. This is on
Arch Linux, AMD Ryzen on a X370 motherboard.
Given the