This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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 VMCLEAR is
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 original 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.

 -- Keir

Xen-devel mailing list