[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] credit scheduler issues in 64bit hypervisor


>-----Original Message-----
>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
>Sent: 2006年7月2日 0:02
>To: Li, Xin B
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Ian Pratt; Rik van Riel; 
>Steven Hand; Zheng, Jeff
>Subject: Re: [Xen-devel] credit scheduler issues in 64bit hypervisor
>On 1 Jul 2006, at 16:22, Li, Xin B wrote:
>> This is caused by a vmcs bug, the root cause is on x86_64, a 
>VMX domain
>> is killed without any vmentry (caused by "Error: Device 768 
>(vbd) could
>> not be connected. Hotplug scripts not working."), but then a 
>> still executed on its unlaunched VMCS.
>> the following patch fixes it.
>> Signed-off-by: Xin Li <xin.b.li@xxxxxxxxx>
>This patch is itself buggy: Just because a VMCS hasn't been launched 
>doesn't mean it hasn't been activated on some CPU. I think the 
>bug would be better fixed by only calling vmx_clear_vmcs() in 
>vmx_destroy_vmcs() if arch_vmx->vmcs != NULL. Even better would be not 
>to allocate the VMCS so darn late.

Yes, it's buggy, and prevent the first vmclear to a vmcs.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.