On 08/05/2010 03:10 PM, Nadav Har'El wrote:
quoted text
> On Thu, Aug 05, 2010, Avi Kivity wrote about "Re: [PATCH 9/24] Implement VMCLEAR":
>> As far as the processor is concerned, there is no end to physical
>> memory.  The VMCLEAR will write some stuff out, and the chipset will
>> throw it away.
> So isn't what you're saying that for accurate VMCLEAR emulation, I should
> simply ignore this error and have VMCLEAR do nothing in this case?
>

That would be most accurate.

quoted text
>>   However, eventually the guest will crash and burn,
>> better to take it out in a controlled way.
> Isn't it concievable that some poorly-written hypervisor actually VMCLEARs
> something beyond available memory, and doesn't crash because it never tries
> to actually use that memory later?

It's very unlikely.

quoted text
> Do you think it's a good idea to kill
> the guest immediately, in anticipation of a crash that will most likely come
> later?

At this stage, the problem is likely to be in the nvmx implementation.  
So it's best to report the problem as early as possible.

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

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html