Re: SIGILL in grub in guest on 4365

Avi Kivity
2007-02-01T13:05:05Z

Gregory Haskins wrote:
>>>> On Thu, Feb 1, 2007 at 7:46 AM, in message <45C1E116.1070802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
>>>>
> Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>
>> Gregory Haskins wrote:
>>
>>
>>> 1) Is this how illegal- op would be handled, or would that stay entirely in
>>>
>> the domain of the guest?
>>
>>>
>>>
>> An illegal opcode in the guest is handled normally by generating #UD in
>> the guest, without host involvement at all.
>>
>>
>
> Ah, thank you. Sounds like I need to do some more reading in the Intel docs ;) Despite my failings here, I did learn a lot about KVM/QEMU in the process so it wasnt wasted effort.
>
>

VT allows both methods. Basically you tell it for which exceptions you
want a vmexit.

In kvm, we only intercept page faults (for mmu virtualization), and, if
guest debugging is enabled, breakpoint exceptions. We let the guest
handle the rest.

--
error compiling committee.c: too many arguments to function