Avi Kivity wrote:
>>
>>> 2. Add hacks in the memory slot code to not return a memory slot if
>>> the physical address is in the forbidden range.
>>
>> I'm not sure I understand what you mean by this. I guess I have to
>> spend some time and understand how the whole memory slot thing works.
>
> M
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>> Any thoughts?
>>
>> SMM continues the tradition of making each x86 generation hackier
>> than before.
>>
>> What happens (probably) is that the virtual hardware unmaps the vga
>> memory when SMM is entered, and uses the ph
Avi Kivity wrote:
Anthony Liguori wrote:
Any thoughts?
SMM continues the tradition of making each x86 generation hackier than
before.
What happens (probably) is that the virtual hardware unmaps the vga
memory when SMM is entered, and uses the physical memory at these
addresses (which is
Anthony Liguori wrote:
> I spent some time this weekend trying to port the KVM changes to the
> latest QEMU CVS. I got snagged on a certain changeset though.
> Specifically, the changeset on Sep 24th that added SMM support (and
> moved ACPI init to the BIOS) is where my patch stops working.
>
I spent some time this weekend trying to port the KVM changes to the
latest QEMU CVS. I got snagged on a certain changeset though.
Specifically, the changeset on Sep 24th that added SMM support (and
moved ACPI init to the BIOS) is where my patch stops working.
KVM dies with a bus error after
