Hi, Tim and Kevin,
I used the changeset 16704 to take the stability test, and at that
changeset, vmxassist=y is the default. Later I used the Xen3.2 test tree to
have a test, it met the same issue, that is, windows guest would be blue
screen, and linux guest would pop up some call trace. Also Dom0 will pop up
some call trace too. My test environment is
First guest (Linux): kernel build;
Second guest (Linux): network copy;
Third guest (Windows): Sysmark 2007;
In dom0, I did local migration to the three guest.
Tim, could you tell me what's the test case and test environment (changeset)
when you take the stability test? Then I may use your environment to test
Kevin's patch. Thanks very much!
Best Regards,
Xu Dongxiao
-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tim Deegan
Sent: 2008年1月25日 18:01
To: Xu, Dongxiao
Cc: Tian, Kevin; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: [PATCH][RFC]Provide fast write emulation
pathtorelease shadow lock
Hi,
At 09:41 +0800 on 25 Jan (1201254064), Xu, Dongxiao wrote:
> But I found that even without Kevin's patch, the guest would be blue
> screen in Windows or print some call trace in Linux guest. Have you
> seen this issue before? Thanks!
Can you try building Xen with "vmxassist=y" on the make command-line?
Cheers,
Tim.
--
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 0DZ, UK.]
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home