[Xen-devel] Re: [xen-unstable test] 2549: regressions - FAIL

[Keir Fraser <keir@xxxxxxx>]

On 04/11/2010 16:05, "Keir Fraser" <keir@xxxxxxx> wrote:

>> xc: error: No extended context for VCPU133120 (3 = No such process): Internal
>> error
>> xc: error: Failed to map/save the p2m frame list (3 = No such process):
>> Internal error
>> libxl: error: libxl_dom.c:448:libxl__domain_suspend_common saving domain: No
>> such process
>> xl: fatal error: xl_cmdimpl.c:2610: Unknown error 4294967294:
>> libxl_domain_suspend(&ctx, NULL, domid, fd)
>> 
>> A similar failure occurs with xend and appears in the xend logfile.
> 
> Just as well we didn't check it in to 4.0-testing too, eh?

Obviously the whole patchset was never tested in the common case of xsave
being unsupported or disabled. I have reverted the save/restore patch, and I
have also reverted patch hunks which make XSAVE/AVX visible to guests. The
reason for this is that the code which determines guest CPUID is based on
reading host CPUID -- this will report XSAVE/AVX as available on any CPU
that supports it, even if it has actually been disabled by use_xsave=0 in
the hypervisor (which is the default!). So the guest will try to use the
feature, and at the very least will get its state trashed across context
switches and save/restore (because Xen sees !cpu_has_xsave). Very nice.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel