I have retry RC2 source on FC5 + gcc 4.1.0. IA32pae doesn't have
problem.
So the dom0 crashing issue is related with compiler env for building
Xen.
Best Regards,
Yongkang You
-----Original Message-----
From: xen-...@lists.xensource.com
[mailto:xen-...@lists.xensource.com] On Behalf Of
You, Yongkang
Sent: Friday, September 28, 2007 3:47 PM
To: Keir Fraser; xen-devel
Subject: RE: [Xen-devel] Xen 3.1.1 RC2 testing report. -- 1
Blocked issue.
-----Original Message-----
From: Keir Fraser [mailto:Keir...@cl.cam.ac.uk]
Sent: Friday, September 28, 2007 3:43 PM
To: You, Yongkang; xen-devel
Subject: Re: [Xen-devel] Xen 3.1.1 RC2 testing report. -- 1
Blocked issue.
On 28/9/07 08:34, "You, Yongkang" <yong...@intel.com> wrote:
The testing env is same with our nightly testing env. But nightly
testing can not meet this issue.
It is stange. What is your testing env?
Some fairly old Intel SDV, booting either a Linux or w2k3 HVM guest.
I can also reproduce the crashing on an old Intel SDV, which only has 2
cpus.
How similar is your nightly env to your test env? This could be a
platform-specific issue.
I mean it is the same machine to test xen 3.1.1 and xen-unstable.
Would it because compile issue? The build machine is FC3 + gcc 3.4.2
Best Regards,
Yongkang You
7 messages in com.xensource.lists.xen-develRE: [Xen-devel] Xen 3.1.1 RC2 testing...
.log, .log