July 20, 2005 using latest HG source pull:
* changeset: 5814:2ecb91fb6cdbdfa001a48bc2bb2b1db320a19485
tag: tip
user: kaf24§firebug.cl.cam.ac.uk
date: Tue Jul 19 04:26:18 2005
summary: Fix wallclock timebase extraction in XenLinux.
* x86
* SLES 9/SP1, RHEL 4 and FC3 on IBM xSeries 305,
235, HS20(x86) and IBM ThinkCentre
* Builds and boots without problems
* *ISSUE 1*:
* DomU crashes
Oops: 0002 [#1]
PREEMPT SMP modules linked
in:
CPU: 0
EIP: 0061:[<00244ec0>]
Not tainted VLI
* No other output
* Bugzilla #96
* *ISSUE 2*:
* Experiencing disconnections from
ssh session to dom0
* Only seeing this happening with
Broadcom NetXtreme Gigabit Ethernet card
* Bugzilla #103
* x86_64
* EMT64
* Builds and boots without problems (GCC 3 and
GCC4)
* Able to create function domains (Running LTP on
dom0)
* Opteron
* No test data. If you are testing
Opteron, please send me test status
information so that I can include it in
this report.
Regards,
Li
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
July 21, 2005 using latest HG source pull:
* changeset:
5821:6e11af443eb1cc3ff5533d531ab48c9964ad2dee
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Jul 21 09:15:35 2005
summary: Fix problem of can not create two or more
vmx guest.
* x86
* SLES 9/SP1, RHEL 4 and FC3 on IBM xSeries 305,
235, HS20(x86) and IBM ThinkCentre
* Builds and boots without problems
* OUTSTANDING ISSUE: (NO CHANGE FROM LAST
WEEK - UNRESOLVED PROBLEM)
* DomU crashes
Oops: 0002 [#1]
PREEMPT SMP modules linked in:
CPU: 0
EIP: 0061:[<00244ec0>]
Not tainted VLI
* No other output
* Seeing this on test boxes where
DomU is a SLES 9 installation
* On a test box where Dom0 is SLES
9 and DomU is RHEL 4, however,
no problems are observed
* Bugzilla #96-
''BLOCKER''
* x86_64 EMT64
* OUTSTADING ISSUES:
* Bugzilla #93
* Can''t test further until #102
is
resolved, but I believe problem
may still be unresolved.
* Dom0 crashes when a DomU is
created
* Problem is consistently
reproducible
* Bugzilla #104
When starting xend on an x86_64 machine
(IBM HS20 Blade EMT64) with SLES 9,
networking is completely disabled.
** Note: This problem is NOT happening
on an identical machine that has FC4.
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
July 21, 2005 using latest HG source pull:
* changeset:
5822:9038a369268d0552ce659cdea3f38409bbaffffc
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Jul 21 10:50:11 2005
summary: Here is a patch to enable Xen to run on a
Unisys ES7000 x86_64 system.
* x86
* BUILD BREAK on FC3
* make[4]: *** No rule to make target
`vbe.h'', needed by
`vgabios.bin''. Stop.
* Bugzilla #111
* SLES 9/SP1, and RHEL 4 on IBM xSeries 305, and
235
* Builds and boots without problems
* OUTSTANDING ISSUE: (NO CHANGE FROM LAST
REPORT - UNRESOLVED PROBLEM)
* DomU crashes
Oops: 0002 [#1]
PREEMPT SMP modules linked in:
CPU: 0
EIP: 0061:[<00244ec0>]
Not tainted VLI
* No other output
* Seeing this on test boxes where
DomU is a SLES 9 installation
* On a test box where Dom0 is SLES
9 and DomU is RHEL 4, however,
no problems are observed
* Bugzilla #96-
''BLOCKER''
* x86_64
* EMT64*
* Builds and boots without problems on
SLES 9/SP1 and FC4
* Able to build functional DomUs,
networking and all
* Bugzilla #93 - RESOLVED.
* Bugzilla #104 -RESOLVED.
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Defect/issue summary:
* Buld break on FC3 platform, Bugzilla #111
* DomU crashes on setup where DomU is a SLES 9 install, Bugzilla #96
(Blocker).
July 25, 2005 using latest HG source pull:
* changeset:
5824:48aed1403fe35f80aaed8f03c354cbb8c1a0c4ab
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Fri Jul 22 11:44:33 2005
summary: Port kallsyms to Xen, as
''symbols''.
* x86
* BUILD BREAK on FC3 platform:
* make[4]: *** No rule to make target
`vgabios.c'', needed by
`vgabios.bin''.
Stop.
* Bugzilla #111
* SLES 9 SP2, and RHEL 4 on IBM xSeries 305, and
235
* Builds and boots without problems
* *NEED SOME HELP IN RESOLVING PROBLEM
DESCRIBED BELOW*
* OUTSTANDING ISSUE: (NO CHANGE FROM LAST
WEEK - UNRESOLVED PROBLEM)
* DomU crashes
Oops: 0002 [#1]
PREEMPT SMP modules linked in:
CPU: 0
EIP: 0061:[<00244ec0>]
Not tainted VLI
* No other output
* Seeing this on test boxes where
DomU is a SLES 9 installation
* On a test box where Dom0 is SLES
9 and DomU is RHEL 4, however,
no problems are observed
* Bugzilla #96-
''BLOCKER''
* x86_64
* EMT64*
* Builds and boots without problems on
SLES 9 SP2 and FC4
* Able to build functional DomUs,
networking and all
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On Mon, 2005-07-25 at 10:24 -0500, David F Barrera wrote:> Defect/issue summary: > * Buld break on FC3 platform, Bugzilla #111Please disregard this statement. I dug a little more and found out I have a problem with the setup on this particular box. David> * DomU crashes on setup where DomU is a SLES 9 install, Bugzilla #96 > (Blocker). > > July 25, 2005 using latest HG source pull: > * changeset: > 5824:48aed1403fe35f80aaed8f03c354cbb8c1a0c4ab > tag: tip > user: kaf24@firebug.cl.cam.ac.uk > date: Fri Jul 22 11:44:33 2005 > summary: Port kallsyms to Xen, as ''symbols''. > * x86 > * BUILD BREAK on FC3 platform: > * make[4]: *** No rule to make target > `vgabios.c'', needed by `vgabios.bin''. > Stop. > * Bugzilla #111 > * SLES 9 SP2, and RHEL 4 on IBM xSeries 305, and > 235 > * Builds and boots without problems > * *NEED SOME HELP IN RESOLVING PROBLEM > DESCRIBED BELOW* > * OUTSTANDING ISSUE: (NO CHANGE FROM LAST > WEEK - UNRESOLVED PROBLEM) > * DomU crashes > Oops: 0002 [#1] > PREEMPT SMP modules linked in: > CPU: 0 > EIP: 0061:[<00244ec0>] Not tainted VLI > * No other output > * Seeing this on test boxes where > DomU is a SLES 9 installation > * On a test box where Dom0 is SLES > 9 and DomU is RHEL 4, however, > no problems are observed > * Bugzilla #96- ''BLOCKER'' > * x86_64 > * EMT64* > * Builds and boots without problems on > SLES 9 SP2 and FC4 > * Able to build functional DomUs, > networking and all >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Defect summary: I have been reporting since July 11 that DomU crashes on a couple of my machines upon creation, on setups where DomU is based on a SLES 9 installation. I am still experiencing this problem. Defect #96 in the Xensource bugzilla system has been created to document this problem. I sent this note out on July 13:> David F Barrera wrote: > > We are seeing a problem in xen-unstable where DomU crashesimmediately> > after booting on some x86 boxes. In my case, it is happening on acouple> > of machines that have SCSI drives and where DomU is a SLES 9 > > installation. Here''s some data on my setup: > > > > Dom0 DomU Dom U Crash? SCSI > > > > Machine A SLES 9 SLES 9 Yes Yes > > Machine B SLES 9 RHEL 4 No Yes > > Machine C RHEL 4 SLES 9 Yes Yes > > Machine D FC3 SLES 9 and Debian No No > > > > The only thing I see in common in the machines that fail is the SCSI > > drives. Machines B and C are identical; the others are different > > models. >* July 26, 2005 using latest HG source pull: * changeset: 5844:d63b100b327ab8354bc9a71c38dbca436c64c0a5 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Tue Jul 26 05:09:06 2005 summary: Fix restart/poweroff properly. From aq. * x86 * SLES 9 SP2, FC3 and RHEL 4 on IBM xSeries 305, 235, and ThinkCentre * Builds and boots Dom0 without problems * **NEED SOME HELP IN RESOLVING PROBLEM DESCRIBED BELOW** * OUTSTANDING ISSUE: (NO CHANGE FROM LAST REPORT - UNRESOLVED PROBLEM) * DomU crashes Oops: 0002 [#1] PREEMPT SMP modules linked in: CPU: 0 EIP: 0061:[<00244ec0>] Not tainted VLI * No other output * Seeing this on test boxes where DomU is a SLES 9 installation * On a test box where Dom0 is SLES 9 and DomU is RHEL 4, however, no problems are observed * Bugzilla #96- ''BLOCKER'' * x86_64 * EMT64* * Builds and boots without problems on SLES 9 SP2 and FC4 * Able to build functional DomUs, networking and all -- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hot Defect(s):
Bugzilla #96- ''BLOCKER'' -DomU crashes (read description
below)
July 27, 2005 using latest HG source pull:
* changeset:
5884:7599a943b39e5eb2ed612d0738cf27913cb78885
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Wed Jul 27 06:20:47 2005
summary: On opt_nosmp, also force num_cores to 1. Do
this in setup.c
* x86
* SLES 9 SP2, FC3 and RHEL 4 on IBM xSeries 305s,
235, and ThinkCentre
* Builds and boots Dom0 without problems
* OUTSTANDING ISSUE: (NO CHANGE FROM LAST
REPORT - UNRESOLVED PROBLEM)
* DomU crashes
Oops: 0002 [#1]
PREEMPT SMP modules linked in:
CPU: 0
EIP: 0061:[<00244ec0>]
Not tainted VLI
* No other output
* Seeing this on test boxes where
DomU is a SLES 9 installation
* On a test box where Dom0 is SLES
9 and DomU is RHEL 4, however,
no problems are observed
* Bugzilla #96-
''BLOCKER''
* x86_64
* EMT64*
* Builds and boots without problems on
SLES 9 SP2 and FC4
* Able to build functional DomUs,
networking and all
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Built Xen with x86 PAE mode ''on''. Some issues have arisen
relating to
that.
July 28, 2005 using latest HG source pull:
* changeset: 5905:501a70f3ae968e46e27b9003febf05253f4cf949
tag: tip
parent:
5904:e2d635617acd58e01dc87145f5d30a3a1143ad01
parent:
5901:80fed4ff19b2423feb98ceddf5cf98218836699d
user: cl349@firebug.cl.cam.ac.uk
date: Thu Jul 28 07:34:45 2005
summary: merge?
* x86
* SLES 9 SP2, FC3 and RHEL 4 on IBM xSeries 305s, 235, and
ThinkCentre
* Builds and boots Dom0 without problems
* ISSUES:
* Dom0 WILL NOT BOOT on SLES 9 boxes built with
PAE mode ''ON'';
* However, Dom0 boots up fine on RHEL 4
machine AND on x86_64 boxes with SLES 9
and RHEL 4 distros
* Bugzilla #122- ''CRITICAL''
* DomU crashes - can''t verify this problem
because
of the problem described above;
* however, the machine where Dom0 is based
on RHEL 4 and DomU is based on SLES 9
that was previously exhibiting the DomU
crash problem seems to be working fine
today. I need to investigate whether
compiling without the PAE option would
make it revert to the DomU crash.
Oops: 0002 [#1]
PREEMPT SMP modules linked in:
CPU: 0
EIP: 0061:[<00244ec0>] Not
tainted VLI
Seeing this on test boxes where DomU is
a SLES 9 installation
On a test box where Dom0 is SLES 9 and
DomU is RHEL 4, however, no problems are
observed
Bugzilla #96- ''BLOCKER''
* x86_64
* EMT64*
* Builds and boots without problems on SLES 9 SP2
and FC4
* Able to build functional DomUs, networking and
all
* Issue:
* Bugzilla #62 - Losing network when xend
started
* I am seeing this problem almost daily on
an x86_64 box, though it has happened on
both architectures previously
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
July 28, 2005 using latest HG source pull:
* changeset:
5919:55a5ad2f028d55758c6193b4fec970ee46a60ec1
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Fri Jul 29 06:21:39 2005
summary: dom_mem_ops address_bitsd fix.
* x86
* SLES 9 SP2, FC3 and RHEL 4 on IBM xSeries 305s,
235, and ThinkCentre
* BUILD BREAK on X86 with PAE
''ON''
* shadow_public.c:1387: error:
`spl3e'' undeclared (first use
in
this function)
* Bugzilla #125
* WITHOUT PAE, XEN Builds and boots Dom0
and DomUs without problems
* Able to create VMs without major
issues.
* Running LTP test suite on Dom0s
and DomUs
* PENDING ISSUE(S):
* Unable to verify Bugzilla #122
due to non-build with PAE on
x86.
* Dom0 WILL NOT BOOT on SLES 9
boxes built with PAE mode
''ON'';
* However, Dom0 boots up
fine on RHEL 4 machine
AND on x86_64 boxes with
SLES 9 and RHEL 4
distros
* Bugzilla #122-
''CRITICAL''
* Bugzilla #96-
''BLOCKER'' DomU
crashes - FIXED.
* Bugzilla #62 - Losing network
when xend started
* We are seeing this
problem almost daily on
both x86 and x86_64
without a particular
pattern.
* x86_64
* EMT64*
* Builds and boots without problems on
SLES 9 SP2 and FC4
* Able to build functional DomUs,
networking and all
* Issue:
* Bugzilla #62 - Losing network
when xend started
* I am seeing this problem almost
daily on an x86_64 box, though
it has happened on both
architectures previously
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 1, 2005 using latest HG source pull:
* changeset:
5925:0db6a59abb955be772d94ba32fe1a34a26db86da
tag: tip
parent:
5924:6a83d157a391d246dfb8bae6a936f6f8266a5818
parent:
5923:90f2b122fc43c72d1e4005e9278b26ba18bf1df0
user: smh22@firebug.cl.cam.ac.uk
date: Mon Aug 1 05:48:24 2005
summary: Manual merge.
* x86
* SLES 9 SP2, FC3 and RHEL 4 on IBM xSeries 305s,
235, and ThinkCentre
* BUILD BREAK on X86 with PAE
''ON''
* shadow_public.c:1387: error:
`spl3e'' undeclared (first use
in
this function)
* Bugzilla #125
* WITHOUT PAE, XEN Builds and boots Dom0
and DomUs without problems
* Able to create VMs without major
issues.
* Running LTP test suite on Dom0s
and DomUs
* PENDING ISSUE(S):
* Unable to verify Bugzilla #122
due to non-build with PAE on
x86.
* Dom0 WILL NOT BOOT on
SLES 9 boxes built with
PAE mode ''ON'';
* However, Dom0 boots up
fine on RHEL 4 machine
AND on x86_64 boxes with
SLES 9 and RHEL 4
distros
* x86_64
* EMT64*
* Builds and boots without problems on
SLES 9 SP2 and FC4
* Able to build functional DomUs,
networking and all
* Issue:
* Bugzilla #62 - Losing network
when xend started
* I am seeing this problem
almost daily on an
x86_64 box.
* Bugzilla Bug 127 - Dom0 crashes
when copying files over NFS from
DomU to an NFS share
* Bugzilla Bug 128 - Dom0 crashed
while running LTP on DomU
* Bugzilla Bug 129 - Kernel BUG at
"fs/fs-writeback.c":363
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
>> August 1, 2005 using latest HG source pull: > * changeset: > 5925:0db6a59abb955be772d94ba32fe1a34a26db86da > tag: tip > parent: > 5924:6a83d157a391d246dfb8bae6a936f6f8266a5818 > parent: > 5923:90f2b122fc43c72d1e4005e9278b26ba18bf1df0 > user: smh22@firebug.cl.cam.ac.uk > date: Mon Aug 1 05:48:24 2005 > summary: Manual merge. > * x86 > * SLES 9 SP2, FC3 and RHEL 4 on IBM xSeries 305s, > 235, and ThinkCentre > * BUILD BREAK on X86 with PAE ''ON'' > * shadow_public.c:1387: error: > `spl3e'' undeclared (first use in > this function) > * Bugzilla #125 > * WITHOUT PAE, XEN Builds and boots Dom0 > and DomUs without problems^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Are you sure? This seems unlikely if you were using cset 5925 since that enabled (by mistake) the use of grant tables for netfront/netback which, at least for me, causes almost an immediate and quite spectacular crash when you start a domU. Can you confirm that this works/worked for you? It''d be a good data point in trying to debug that code. cheers, S. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
August 2, 2005 using latest HG source pull:
* changeset: 5943:dcdcec634c2d5624988d9f4907ade378ff575c51
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Tue Aug 2 11:11:31 2005
summary: Better XenLinux page fault debug output for
PAE.
* x86
* SLES 9 SP2, FC3 and RHEL 4 on IBM xSeries 305s, 235, and
ThinkCentre
* Build break on x86-32 (FIXED NOW)
* (XS_PERM_CREATE'' undeclared in xs.c)
* Bugzilla #133
* PENDING ISSUE(S):
* Bugzilla #122
* Dom0 WILL NOT BOOT on SLES 9
boxes built with PAE mode
''ON'';
* However, Dom0 boots up fine on
RHEL 4 machine AND on x86_64
boxes with SLES 9 and RHEL 4
distros
* Insufficient log/trace info at
the moment
* x86_64
* EMT64*
* Builds and boots without problems on SLES 9 SP2
and FC4
* Able to build functional DomUs, networking and
all
* Issue:
* Bugzilla #62 - Losing network when xend
started
* I am seeing this problem almost
daily on an x86_64 box.
* These problems seem to have happened
because the CONFIG_XEN_NETDEV_GRANT_TX
and CONFIG_XEN_NETDEV_GRANT_RX options
were set to ''y'' (when set to
''N'', the
problems are not observed)
* Bugzilla Bug 127 - Dom0 crashes
when copying files over NFS from
DomU to an NFS share
* Bugzilla Bug 128 - Dom0 crashed
while running LTP on DomU
* Bugzilla Bug 129 - Kernel BUG at
"fs/fs-writeback.c":363
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 3, 2005 using latest HG source pull:
* changeset: 6005:60c4cd9ebaa16a6fcac05275e5e21056794339ad
tag: tip
user: kaf24§firebug.cl.cam.ac.uk
date: Wed Aug 3 11:11:32 2005
summary: Move more drivers to bind_evtchn_to_irqhandler() interface.
1) x86
- SLES 9 SP2, FC3 and RHEL 4 on IBM xSeries 305s, 235, and ThinkCentre
* Builds and boots without problems on SLES 9 SP2 and RHEL4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* PENDING ISSUE(S):
* Bugzilla #122
* Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode
''ON'';
* However, Dom0 boots up fine on RHEL 4 machine with PAE mode
''ON''
2) x86_64
- EMT64*
* Builds and boots without problems on SLES 9 SP2 and FC4
* Able to build functional DomUs, networking and all
* Issue:
* Bugzilla #62 - Losing network when xend started
* Seeing this problem today on an x86_64 box with SLES9 SP2.
Regards,
Li
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 4, 2005 using latest HG source pull:
* changeset: 6012:f3f48305925034ce4a023bd0913ed4cf1866fccb
tag: tip
user: akw27@arcadians.cl.cam.ac.uk
date: Thu Aug 4 09:32:21 2005
summary: Fix two syntax errors in frame-and-sect decoding macros..
1) x86_32
- SLES 9 SP2, RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on SLES 9 SP2 and RHEL4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on dom0
* ISSUE(S):
* Bugzilla #141 (NEW)
* xc_console: Could not read tty from store;
* This happens on all of my test boxes (x86_32, x86_64) with all the
distros (RHEL4, SLES9 SE2 and FC4)
2)x86_32p (PAE)
- SLES 9 SP2, RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4
* Able to build functional DomUs, networking and all
* ISSUE(S):
* Bugzilla #122
* Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode
''ON'';
3) x86_64
- SLES9 SP2, FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds and boots without problems on SLES 9 SP2 and FC4
* Able to build functional DomUs, networking and all
* ISSUE(S):
* Bugzilla #62 - Losing network when xend started on SLES9 SP2
* Not seeing this problem with FC4.
Regards,
Li
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
I sent this email out this morning but have not seen it showing up in the
mailing-list. So I am resending this... Sorry if it is a duplicate.
August 4, 2005 using latest HG source pull:
* changeset: 6012:f3f48305925034ce4a023bd0913ed4cf1866fccb
tag: tip
user: akw27@arcadians.cl.cam.ac.uk
date: Thu Aug 4 09:32:21 2005
summary: Fix two syntax errors in frame-and-sect decoding macros.
1) x86_32
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on dom0
* ISSUE(S):
* Bugzilla #141 (NEW)
* xc_console: Could not read tty from store
* Seeing this problem on all of my test boxes with all the distros;
2) x86_32p (PAE)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on dom0
* ISSUE(S):
* Bugzilla #122
* Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode
''ON''
3) x86_64
-- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds and boots without problems on SLES 9 SP2 and FC4
* Able to build functional DomUs, networking and all
* ISSUE(S):
* Bugzilla #62 - Losing network when xend started
* Seeing this problem on x86_64 box with SLES9 SP2 and x86_32 box
with SLES9.
Regards,
Li
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 5, 2005 using latest HG source pull:
* changeset: 6025:5a33233a608e9d790228d03a23f3407988f1577f
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Fri Aug 5 04:53:04 2005
summary: No need to define errno defined at the top of reboot.c.
1) x86_32
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4 and SLES9 SP2
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #141
* xc_console: Could not read tty from store
* It works for the boxes with FC4 and RHEL4 now
* Only seeing this problem on the boxes with SLESP9 SP2
2) x86_32p (PAE)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on dom0
* ISSUE(S):
* Bugzilla #122
* Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode
''ON''
3) x86_64
-- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds and boots without problems on SLES 9 SP2 and FC4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #62 - Losing network when xend started
* Seeing this problem on x86_64 box with SLES9 SP2 and x86_32 box
with SLES9.
Regards,
Li
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 8, 2005 using latest HG source pull:
* changeset: 6049:d4e19aca1f7240b07fe3839b673d985e5b4a12d9
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Mon Aug 8 09:13:36 2005
summary: Fix signedness issue in xenlinux timer interrupt handler.
1) x86_32
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4 and SLES9 SP2
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #141
* xc_console: Could not read tty from store
2) x86_32p (PAE)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #122
* Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode
''ON''
3) x86_64
-- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds without problems on SLES 9 SP2 and FC4
* ISSUE(S):* ISSUE(S):
* Bugzilla #147 (NEW)
* Dom0 kernel does not boot on x86-64
* Bugzilla #62 - Losing network when xend started
* Seeing this problem on x86_64 box with SLES9 SP2 and x86_32 box
with SLES9.
* Can not verify whether fixed or not in this build
Regards,
Li
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 9, 2005 using latest HG source pull:
* changeset: 6065:38c7c25b3cb9e1adf756497d37c02d462d8f41f6
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Tue Aug 9 08:53:15 2005
summary: Directly including ../tools breaks building in separate object
tree
1) x86_32
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4 and SLES9 SP2
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #141
* xc_console: Could not read tty from store
2) x86_32p (PAE)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #122
* Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode
''ON''
* Dom0 WILL BOOT on SLES9 box using Linux kernel and Xen compiled on
RHEL system with PAE ON
3) x86_64
-- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds without problems on SLES 9 SP2 and FC4
* ISSUE(S):* ISSUE(S):
* Bugzilla #147
* Dom0 kernel does not boot on x86-64
* Bugzilla #62 - Losing network when xend started
* Seeing this problem on x86_64 box with SLES9 SP2 and x86_32 box
with SLES9.
* Can not verify whether fixed or not in this build (blocked by bug
#147)
Regards,
Li____________________________________________
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 10, 2005 using latest HG source pull:
* changeset: 6079:4fa90e2a32578379e196bc7d856cf09b87a53277
tag: tip
user: kaf24§firebug.cl.cam.ac.uk
date: Wed Aug 10 09:11:40 2005
summary: Fix domain0 builder for PAE.
1) x86_32
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4 and SLES9 SP2
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #141 (FIXED)
* xc_console: Could not read tty from store
2) x86_32p (PAE)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4 and SLES9 SP2
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #122 (FIXED)
* Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode
''ON''
3) x86_64
-- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds and boots without problems on SLES 9 SP2 and FC4
* ISSUE(S):* ISSUE(S):
* Bugzilla #147 (FIXED)
* Dom0 kernel does not boot on x86-64
* Bugzilla #62 - Losing network when xend started
* Not seeing this problem happening today. Need more investigation.
Will try out Ian''s new network script as well.
Regards,
Li_________________________________________
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
> August 10, 2005 using latest HG source pull: > * changeset: 6079:4fa90e2a32578379e196bc7d856cf09b87a53277 > tag: tip > user: kaf24§firebug.cl.cam.ac.uk > date: Wed Aug 10 09:11:40 2005 > summary: Fix domain0 builder for PAE.So, I think your report is saying "everything now works for me!". There''s been several niggling bugs fixed today, which is great news. Have you got any machines with >4GB? It would be good to add PAE and x86_64 tests on such a machine, as this is a high risk area -- we need daily testing on as many different big memory machines as possible. Also, please let me know how you get on with the new network script. I''ll check it tomorrow if no one complains... Thanks, Ian> 1) x86_32 > > -- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and > 235 (1G RAM) > * Builds and boots without problems on RHEL4 and SLES9 SP2 > * Able to build functional DomUs, networking and all > * Able to complete LTP runalltests.sh on both dom0 and domU > * ISSUE(S): > * Bugzilla #141 (FIXED) > * xc_console: Could not read tty from store > > > 2) x86_32p (PAE) > > -- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and > 235 (1G RAM) > * Builds and boots without problems on RHEL4 and SLES9 SP2 > * Able to build functional DomUs, networking and all > * Able to complete LTP runalltests.sh on both dom0 and domU > * ISSUE(S): > * Bugzilla #122 (FIXED) > * Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode ''ON'' > > > > 3) x86_64 > > -- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM) > * Builds and boots without problems on SLES 9 SP2 and FC4 > * ISSUE(S):* ISSUE(S): > > * Bugzilla #147 (FIXED) > * Dom0 kernel does not boot on x86-64 > > * Bugzilla #62 - Losing network when xend started > * Not seeing this problem happening today. Need more > investigation. Will try out Ian''s new network script as well. > > > Regards, > Li_________________________________________ >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Yup. This is the best daily build report I''ve had so far:-)
I will try to get the system with >4GB installed today or tomorrow and
start to report status of it as well.
I will try out your network scripts this afternoon.
Li
"Ian Pratt"
<m+Ian.Pratt@cl.c
am.ac.uk> To
Li Ge/Austin/IBM@IBMUS,
08/10/2005 12:08 <xen-devel@lists.xensource.com>
PM cc
<ian.pratt@cl.cam.ac.uk>
Subject
RE: [Xen-devel] Daily Xen Builds
> August 10, 2005 using latest HG source pull:
> * changeset: 6079:4fa90e2a32578379e196bc7d856cf09b87a53277
> tag: tip
> user: kaf24§firebug.cl.cam.ac.uk
> date: Wed Aug 10 09:11:40 2005
> summary: Fix domain0 builder for PAE.
So, I think your report is saying "everything now works for me!".
There''s been several niggling bugs fixed today, which is great news.
Have you got any machines with >4GB? It would be good to add PAE and x86_64
tests on such a machine, as this is a high risk area -- we need daily
testing on as many different big memory machines as possible.
Also, please let me know how you get on with the new network script.
I''ll
check it tomorrow if no one complains...
Thanks,
Ian
> 1) x86_32
>
> -- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and
> 235 (1G RAM)
> * Builds and boots without problems on RHEL4 and SLES9 SP2
> * Able to build functional DomUs, networking and all
> * Able to complete LTP runalltests.sh on both dom0 and domU
> * ISSUE(S):
> * Bugzilla #141 (FIXED)
> * xc_console: Could not read tty from store
>
>
> 2) x86_32p (PAE)
>
> -- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and
> 235 (1G RAM)
> * Builds and boots without problems on RHEL4 and SLES9 SP2
> * Able to build functional DomUs, networking and all
> * Able to complete LTP runalltests.sh on both dom0 and domU
> * ISSUE(S):
> * Bugzilla #122 (FIXED)
> * Dom0 WILL NOT BOOT on SLES 9 boxes built with PAE mode
''ON''
>
>
>
> 3) x86_64
>
> -- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
> * Builds and boots without problems on SLES 9 SP2 and FC4
> * ISSUE(S):* ISSUE(S):
>
> * Bugzilla #147 (FIXED)
> * Dom0 kernel does not boot on x86-64
>
> * Bugzilla #62 - Losing network when xend started
> * Not seeing this problem happening today. Need more
> investigation. Will try out Ian''s new network script as well.
>
>
> Regards,
> Li_________________________________________
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 11, 2005 using latest HG source pull:
* changeset: 6093:10b395bc465ea7ac73302d4987b05f40ee023b22
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Aug 11 08:07:08 2005
summary: More time fixes. Now time is set properly in domU''s, and
1) x86_32
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on SLES9 SP2
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
2) x86_32p (PAE)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on RHEL4 and SLES9 SP2
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
3) x86_64
-- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds and boots without problems on SLES 9 SP2 and FC4
* Able to build functional DomUs, networking and all
* Able to complete LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Bugzilla #62 - Losing network when xend started
* Seeing this problem happening on a SLES9 SP2 x86-64 box.
Regards,
Li
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 12, 2005 using latest HG source pull: * changeset: 6124:38bee85ddeb83378eb9ba9b692cc39499d6a05d4 tag: tip parent: 6120:f6d6d17eaeb5f04efea7f9d8f753a91ffff0479d parent: 6123:1fb1877ed6d1b2ae5b130e4d3e29fc06ef58db3c user: kaf24@firebug.cl.cam.ac.uk date: Fri Aug 12 08:29:57 2005 summary: merge 1) x86_32 -- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM) * Builds and boots without problems on SLES9 SP2 * Able to build functional DomUs, networking and all * Able to complete LTP runalltests.sh on both dom0 and domU * ISSUE(S): 2) x86_32p (PAE) -- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM) * Builds and boots without problems on RHEL4 and SLES9 SP2 * Able to build functional DomUs, networking and all * Able to complete LTP runalltests.sh on both dom0 and domU * ISSUE(S): 3) x86_64 -- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM) * Builds and boots without problems on SLES 9 SP2 and FC4 * Able to build functional DomUs, networking and all * Able to complete LTP runalltests.sh on both dom0 and domU * ISSUE(S): * Bugzilla #62 - Losing network when xend started * Not seeing this problem happening today on SLES9 SP2 x86-64 boxes. Regards, Li _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
August 15, 2005 using latest HG source pull:
changeset: 6171:5311d81c1e8e35eee40b76e117ab4c596ed7d409
tag: tip
user: iap10@firebug.cl.cam.ac.uk
date: Mon Aug 15 03:55:11 2005
summary: Add a few options to the Linux x86_64 domU config.
1) x86_32 (no PAE support)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* Builds and boots without problems on SLES9 SP2
* Able to build functional DomUs, networking and all
* Running LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
2) x86_32p (PAE)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G RAM)
* The SLES 9 SP2 boxes FAILED TO BOOT Dom0 when built with PAE
* Two (2) machines exhibiting this problem
* Last message on console is the ''xen memory scrubbing'' line
* The RHEL 4 box builds and boots without problems with PAE
* Able to build functional DomUs, networking and all
* Running LTP runalltests.sh on both dom0 and domU
* ISSUE(S):
* Reopening Bugzilla #122 -Dom0 fails to boot on SLES 9 machines
compiled with x86 PAE mode ON
3) x86_64
-- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds and boots on SLES 9 SP2
* Problems starting xend (below)
* ISSUE(S):
* Bugzilla #62 - Losing network when starting xend.
* Still experiencing this problem on the SLES9 SP2 x86-64 boxes.
* Both SLES 9 SP2 boxes lose networking when ''xend start'' is
entered.
* Problem appears worse now. The network-bridge script has been
changed recently.
* Bugzilla #161 - x86_64 - Dom0 will not boot on FC4 box
* New issue
* We have previously built and booted Dom0 (and DomUs) on this box
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
> 2) x86_32p (PAE) > > -- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and > 235 (1G RAM) > * The SLES 9 SP2 boxes FAILED TO BOOT Dom0 when built with PAE > * Two (2) machines exhibiting this problem > * Last message on console is the ''xen memory scrubbing'' linePlease can you investigate by building and test booting versions between when it last worked for you and today -- it would really help us narrow this down quickly. Doing binary chop you should be able to narrow it down to a handul changesets without too many boots.> 3) x86_64 > > -- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM) > * Builds and boots on SLES 9 SP2 > * Problems starting xend (below) > > * ISSUE(S): > > * Bugzilla #62 - Losing network when starting xend. > * Still experiencing this problem on the SLES9 SP2 x86-64 boxes. > * Both SLES 9 SP2 boxes lose networking when ''xend start'' > is entered.Please can you post xend.log, plus also the result of ''ifconfig'' and ''brctl'' before and after running ''xend start''. Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2005-08-15 at 20:42 +0100, Ian Pratt wrote:> > 2) x86_32p (PAE) > > > > -- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and > > 235 (1G RAM) > > * The SLES 9 SP2 boxes FAILED TO BOOT Dom0 when built with PAE > > * Two (2) machines exhibiting this problem > > * Last message on console is the ''xen memory scrubbing'' line > > Please can you investigate by building and test booting versions between > when it last worked for you and today -- it would really help us narrow > this down quickly. Doing binary chop you should be able to narrow it > down to a handul changesets without too many boots.As I understand, it worked for Li Ge last week while I was at LWE, so I should start with Friday''s build.> > > 3) x86_64 > > > > -- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM) > > * Builds and boots on SLES 9 SP2 > > * Problems starting xend (below) > > > > * ISSUE(S): > > > > * Bugzilla #62 - Losing network when starting xend. > > * Still experiencing this problem on the SLES9 SP2 x86-64 boxes. > > * Both SLES 9 SP2 boxes lose networking when ''xend start'' > > is entered. > > Please can you post xend.log, plus also the result of ''ifconfig'' and > ''brctl'' before and after running ''xend start''.The machine uses eth1, so I changed this line in the network-bridge script: netdev=${netdev:-eth1} Q. Do I also need to change this line (line #191) in the current script in unstable (I tried both eth0 and eth1--both times networking stopped): ip link set veth0 name eth1 ifconfig (before): bl2-1:~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:610 errors:0 dropped:0 overruns:0 frame:0 TX packets:68 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:87998 (85.9 Kb) TX bytes:7413 (7.2 Kb) Interrupt:78 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1512 (1.4 Kb) TX bytes:1512 (1.4 Kb) brctl (before): bl2-1:~ # brctl show bridge name bridge id STP enabled interfaces bl2-1:~ # xend start ifconfig (after) bl2-1:~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 inet addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:882 (882.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:26 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2664 (2.6 Kb) TX bytes:2664 (2.6 Kb) peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:1141 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:251046 (245.1 Kb) TX bytes:0 (0.0 b) Interrupt:78 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:756 (756.0 b) TX bytes:0 (0.0 b) brctl (after) bl2-1:~ # brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.feffffffffff no vif0.0 peth1> > Thanks, > Ian >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> The machine uses eth1, so I changed this line in the network-bridge > script: > netdev=${netdev:-eth1} > > Q. Do I also need to change this line (line #191) in the > current script in unstable (I tried both eth0 and eth1--both > times networking stopped): > ip link set veth0 name eth1Hmm, good point -- that''s a bug in the script. It should be: ip link set veth0 name ${netdev} The only thing wrong with the ''after'' set up is that xen-br0 is missing from ifconfig, though brctl shows the bridge as existing. No idea why. What happens if you do: ifconfig xen-br0 ifconfig xen-br0 up Best, Ian> ifconfig (after) > bl2-1:~ # ifconfig > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 > inet addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:882 (882.0 b) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:26 errors:0 dropped:0 overruns:0 frame:0 > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2664 (2.6 Kb) TX bytes:2664 (2.6 Kb) > > peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:1141 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:251046 (245.1 Kb) TX bytes:0 (0.0 b) > Interrupt:78 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:756 (756.0 b) TX bytes:0 (0.0 b) > > > brctl (after) > bl2-1:~ # brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.feffffffffff no vif0.0 > peth1 > > > > > > Thanks, > > Ian > > > -- > Regards, > > David F Barrera > Linux Technology Center > Systems and Technology Group, IBM > > "The wisest men follow their own direction. " > Euripides > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2005-08-15 at 21:46 +0100, Ian Pratt wrote:> > The machine uses eth1, so I changed this line in the network-bridge > > script: > > netdev=${netdev:-eth1} > > > > Q. Do I also need to change this line (line #191) in the > > current script in unstable (I tried both eth0 and eth1--both > > times networking stopped): > > ip link set veth0 name eth1 > > Hmm, good point -- that''s a bug in the script. It should be: > ip link set veth0 name ${netdev} > > > The only thing wrong with the ''after'' set up is that xen-br0 is missing > from ifconfig, though brctl shows the bridge as existing. No idea why. > > What happens if you do: > > ifconfig xen-br0 > ifconfig xen-br0 upbl2-1:~ # ifconfig xen-br0xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) bl2-1:~ # ifconfig xen-br0 up At this point, networking is up. But we knew that--we put that on the bug--when we manually bring up xen-br0, networking resumes. I guess the question is why xen-br0 is not coming up.> > Best, > Ian > > > ifconfig (after) > > bl2-1:~ # ifconfig > > eth1 Link encap:Ethernet HWaddr 00:11:25:9D:69:87 > > inet addr:9.3.192.194 Bcast:9.3.192.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:882 (882.0 b) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:26 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:2664 (2.6 Kb) TX bytes:2664 (2.6 Kb) > > > > peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > > RX packets:1141 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:251046 (245.1 Kb) TX bytes:0 (0.0 b) > > Interrupt:78 > > > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:756 (756.0 b) TX bytes:0 (0.0 b) > > > > > > brctl (after) > > bl2-1:~ # brctl show > > bridge name bridge id STP enabled interfaces > > xen-br0 8000.feffffffffff no vif0.0 > > peth1 > > > > > > > > > > Thanks, > > > Ian > > > > > -- > > Regards, > > > > David F Barrera > > Linux Technology Center > > Systems and Technology Group, IBM > > > > "The wisest men follow their own direction. " > > Euripides > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> bl2-1:~ # ifconfig xen-br0 up > > At this point, networking is up. But we knew that--we put > that on the bug--when we manually bring up xen-br0, > networking resumes. I guess the question is why xen-br0 is > not coming up.I''ve tweaked the script. It''s possibly a difference in brctl version between suse and rhel. Hopefully this work for you. Best, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>> What happens if you do: >> >> ifconfig xen-br0 >> ifconfig xen-br0 upbl2-1:~ # ifconfig xen-br0 > >xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > >bl2-1:~ # ifconfig xen-br0 up > >At this point, networking is up. But we knew that--we put that on the >bug--when we manually bring up xen-br0, networking resumes. I guess the >question is why xen-br0 is not coming up. >I meet this problem both on X86 and X86_64 platform. I also tried "ifconfig xen-br0 up", but network still couldn''t work. I noticed that after xend start, both eth0 and peth0 have the same IP address. "route" command won''t display default gateway. "route -n" could see peth0 has the 0.0.0.0 destination. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
August 16, 2005 using latest HG source pull:
changeset: 6192:3d187585c1415fbb14cb285cc71e0ff0faf81e67
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Tue Aug 16 06:20:47 2005
summary: Use a SWIOTLB to use pre-reserved bounce buffers for high
1) x86_32 (no PAE support)
-- SLES 9 SP2 on IBM xSeries 305s (512M RAM)
* Builds and boots without problems on SLES9 SP2
* Able to create a functional domU
* Running LTP on both dom0 and domu
* * ISSUE(S):
* x86 - Oops - Unable to handle kernel NULL pointer dereference at
virtual address 0000001c
* Bugzilla #167 - **Ian Pratt believes it may already have been
fixed, but I haven''t verified yet.
2) x86_32p (PAE)
-- SLES 9 SP2 and RHEL 4 on IBM xSeries 305s (512M RAM) and 235 (1G
RAM)
* The SLES 9 SP2 boxes FAILED TO BOOT Dom0 when built with PAE
* Two (2) machines exhibiting this problem
* Last message on console is the ''xen memory
scrubbing'' line
* Bugzilla #125 -REOPENED
* The FC3 and RHEL 4 boxex build and boot without problems with PAE
* However, Dom0 crashes as soon as a DomU is attempted to
create
* Bugzilla #168 kernel BUG at arch/xen/i386/kernel/pci-dma.c:30
(iommu_bug)!
* ISSUE(S):
* Reopening Bugzilla #122 -Dom0 fails to boot on SLES 9
machines compiled with x86 PAE mode ON
* Bugzilla #62 - Losing network when starting xend.
* New network-bridge script
* Appears to have fixed the SLES 9 problems, but
* FC3 box loses network connectivity now.
* Working the issue
3) x86_64
-- SLES9 SP2 and FC4 on IBM HS20 EMT64 blades (1G RAM)
* Builds and boots on SLES 9 SP2
* Able to create functional domains
* New network-bridge scripts seems to work on the SLE 9 SP2 boxes
* ISSUE(S):
* Two DomUs on separate boxes lack networking
* setups worked previously; investigating
* Bugzilla #166 - UnicodeError: label too long
* Error appears when typing ''xm list'' on x86_64
SLES 9 SP2
* This error does not seem to affect functionality
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 17, 2005 using hg source as of:
changeset: 6216:69f00d6ab5dcdfb440482315715522ee85e86f84
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Wed Aug 17 08:34:42 2005
summary: Fix module build by removing duplicate EXPORT_SYMBOL
x86_32 (no PAE support)
1. SLES 9 SP2 on IBM xSeries 305 (512M RAM)
2. Builds and boots without problems
3. Able to create domU
4. Ran LTP on both dom0 and domU
5. No problems observed
x86_32 (PAE)
1. SLES 9 SP2, FC3, and RHEL 4 IBM xSeries 305, 235, and
ThinkCentre
2. Boots on RHEL 4 and FC3 boxes only.
3. ISSUES:
1. Does NOT boot on SLES 9 SP2 boxes, Bugzilla #122
2. DomU boot crashes Dom0, Bugzilla #168
1. Workaround: use swiotlb=force as a kernel
parameter when booting Dom0
2. DomU boots up normally if using swiotlb=force
3. X server will not come up on Dom0 on a FC3 box when Xen
built with PAE ''on'', Bugzilla #137
x86_64
1. SLES 9 SP2 and FC4 on IBM HS20 Blades
2. Xen builds and boots without problems
3. Able to create domUs, with network connectivity
1. ''xend start'' does not break the networking on
the SLES 9
boxes now. Yay!
2. Ran LTP on domU. Need to investigate why LTP seems not
to have completed.
4. ISSUES:
1. Bugzilla #169 - x86_64 - Unable to handle kernel paging
request at ffff8000003e0000 RIP:
<ffffffff8015d16c>{unmap_vmas+1084}
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
August 18, 2005 using hg source as of:
changeset: 6228:1a94949348ff52863b9fbef4eaf102c7e46a345d
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Aug 18 05:41:55 2005
summary: Fix range_straddles_boundary() check to exclude regions that
x86_32 (no PAE support)
1. SLES 9 SP2 on IBM xSeries 305 (512M RAM)and FC3 on IBM ThinkCentre
2. Builds and boots without problems
3. Able to create domU
4. Ran LTP on both dom0 and domU
5. No problems observed
Last good changeset for x86_32, non-PAE:
changeset: 6228:1a94949348ff52863b9fbef4eaf102c7e46a345d
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Aug 18 05:41:55 2005
summary: Fix range_straddles_boundary() check to exclude regions that
x86_32 (PAE)
1. SLES 9 SP2, FC3, and RHEL 4 IBM xSeries 305, 235, and
ThinkCentre
2. Boots on RHEL 4 and FC3 boxes only.
* Booted DomU using swiotlb=force
* Ran LTP on both Dom0 and DomU
3. ISSUES:
1. Does NOT boot on SLES 9 SP2 boxes, Bugzilla #122
2. DomU boot crashes Dom0, Bugzilla #168
1. Workaround: use swiotlb=force as a kernel
parameter when booting Dom0
2. DomU boots up normally if using swiotlb=force
3. X server will not come up on Dom0 on a FC3 box when Xen
built with PAE ''on'', Bugzilla #137
4. Possible networking issue on FC3 when Xen built with PAE
* DomU unable to get dhcp address
* tcpdump shows lots of networking activity being ''heard''
* DomU has no trouble getting IP address when Xen built non-PAE, however
* **Further investigating at the moment
Last good changeset for x86_32, PAE: Unknown
x86_64
1. SLES 9 SP2 and FC4 on IBM HS20 Blades
2. Xen builds and boots without problems
3. Able to create domUs, with network connectivity
4. Ran LTP on Dom0s and DomUs
5. ISSUES:
1. Bugzilla #169 - x86_64 - Unable to handle kernel paging
request at ffff8000003e0000 RIP:
<ffffffff8015d16c>{unmap_vmas+1084}
2. Seeing this Oops on a SLES 9 SP2 box
3. Machine seems unaffected, however
Last good changeset for x86_64:
changeset: 6228:1a94949348ff52863b9fbef4eaf102c7e46a345d
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Aug 18 05:41:55 2005
summary: Fix range_straddles_boundary() check to exclude regions that
-- Regards, David F Barrera Linux Technology Center Systems and
Technology Group, IBM "The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
David,
The latest good changeset for x86_32 (PAE) should be 6124 according
to the build report of August 12.
Thanks,
Li
dfbp@us.ltcfwd.li
nux.ibm.com
Sent by: To
xen-devel-bounces xen-devel@lists.xensource.com
@lists.xensource. cc
com
Subject
[Xen-devel] Daily Xen Builds
08/18/2005 01:39
PM
August 18, 2005 using hg source as of:
changeset: 6228:1a94949348ff52863b9fbef4eaf102c7e46a345d
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Aug 18 05:41:55 2005
summary: Fix range_straddles_boundary() check to exclude regions that
x86_32 (no PAE support)
1. SLES 9 SP2 on IBM xSeries 305 (512M RAM)and FC3 on IBM ThinkCentre
2. Builds and boots without problems
3. Able to create domU
4. Ran LTP on both dom0 and domU
5. No problems observed
Last good changeset for x86_32, non-PAE:
changeset: 6228:1a94949348ff52863b9fbef4eaf102c7e46a345d
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Aug 18 05:41:55 2005
summary: Fix range_straddles_boundary() check to exclude regions that
x86_32 (PAE)
1. SLES 9 SP2, FC3, and RHEL 4 IBM xSeries 305, 235, and
ThinkCentre
2. Boots on RHEL 4 and FC3 boxes only.
* Booted DomU using swiotlb=force
* Ran LTP on both Dom0 and DomU
3. ISSUES:
1. Does NOT boot on SLES 9 SP2 boxes, Bugzilla #122
2. DomU boot crashes Dom0, Bugzilla #168
1. Workaround: use swiotlb=force as a kernel
parameter when booting Dom0
2. DomU boots up normally if using swiotlb=force
3. X server will not come up on Dom0 on a FC3 box when Xen
built with PAE ''on'', Bugzilla #137
4. Possible networking issue on FC3 when Xen built with
PAE
* DomU unable to get dhcp address
* tcpdump shows lots of networking activity being
''heard''
* DomU has no trouble getting IP address when Xen
built non-PAE, however
* **Further investigating at the moment
Last good changeset for x86_32, PAE: Unknown
x86_64
1. SLES 9 SP2 and FC4 on IBM HS20 Blades
2. Xen builds and boots without problems
3. Able to create domUs, with network connectivity
4. Ran LTP on Dom0s and DomUs
5. ISSUES:
1. Bugzilla #169 - x86_64 - Unable to handle kernel paging
request at ffff8000003e0000 RIP:
<ffffffff8015d16c>{unmap_vmas+1084}
2. Seeing this Oops on a SLES 9 SP2 box
3. Machine seems unaffected, however
Last good changeset for x86_64:
changeset: 6228:1a94949348ff52863b9fbef4eaf102c7e46a345d
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Aug 18 05:41:55 2005
summary: Fix range_straddles_boundary() check to exclude regions that
-- Regards, David F Barrera Linux Technology Center Systems and
Technology Group, IBM "The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
> David, > The latest good changeset for x86_32 (PAE) should be 6124 > according to the build report of August 12.On machines with <4GB (and no memory mapped above 4GB) PAE is believed stable (after some checkins today). The funs starts when >4GB is used. We''re still not quite there yet, but getting close. It would be goos if the daily reports said how much memory each machine has, and what hardware e.g. 4GB DMA capable or not [SATA/IDE controllers are probably the biggest offenders here.] Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt wrote:> > > >>David, >>The latest good changeset for x86_32 (PAE) should be 6124 >>according to the build report of August 12. >> >> > >On machines with <4GB (and no memory mapped above 4GB) PAE is believed >stable (after some checkins today). > >I have verified on one machine, SLES 9 SP2 based, that previously crashed on boot, and it has booted just fine. Creating a domU crashes dom0, however, unless dom0 is booted with swiotlb=force as a kernel parameter. This machine has 1GB of memory, SCSI (Adaptec), and Intel Gigabit Ethernet card 82547GI.>The funs starts when >4GB is used. We''re still not quite there yet, but >getting close. > >It would be goos if the daily reports said how much memory each machine >has, and what hardware e.g. 4GB DMA capable or not [SATA/IDE controllers >are probably the biggest offenders here.] > >Thanks, >Ian > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> >On machines with <4GB (and no memory mapped above 4GB) PAE > is believed > >stable (after some checkins today). > > > > > I have verified on one machine, SLES 9 SP2 based, that > previously crashed on boot, and it has booted just fine. > Creating a domU crashes dom0, however, unless dom0 is booted > with swiotlb=force as a kernel parameter. > This machine has 1GB of memory, SCSI (Adaptec), and Intel > Gigabit Ethernet card 82547GI.What happens if you don''t have swiotlb=force and hammer the IO devices in domain 0? I can''t see why creating a domU would be helped by a swiotlb. Precisely which adaptec card is it, what driver? Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt wrote:>What happens if you don''t have swiotlb=force and hammer the IO devices >in domain 0? > >I am running LTP on dom0 and copied a couple of 500MB files over nfs to the host machine as well as some other files. Dom0 still up.>I can''t see why creating a domU would be helped by a swiotlb. > >Without it, dom0 crashes. I reported on Bugzilla #168 a couple of days ago the following crash when creating a domU on machines built with PAE: Fatal DMA error! Please use ''swiotlb=force'' kernel BUG at arch/xen/i386/kernel/pci-dma.c:30 (iommu_bug)! [<c010ea0b>] iommu_bug+0x3b/0x50 [<c010eb6a>] dma_map_sg+0x14a/0x170 [<c02f5023>] ide_map_sg+0xa3/0xb0 [<c02fe86c>] ide_build_sglist+0x7c/0xd0 [<c02fe8ff>] ide_build_dmatable+0x3f/0x190 [<c02fedda>] ide_dma_setup+0x3a/0xe0 [<c0301120>] __ide_do_rw_disk+0x3d0/0x5a0 [<c02f6f00>] ide_wait_stat+0+30/0x230 [<c02837fc>] as_move_to_dispatch+0xec/0x220 [<c02f5550>] start_request+0x270/0x290 [<c02f581c>] ide_do_request+0x27c/0x470 [<c027940c>] elv_next_request+0x3c/0x1b0 [<c02f5a34>] do_ide_request+0x24/0x30 [<c027c62a>] generic_unplug_device+0x2a/0x70 [<c027c600>] generic_unplug_device+0x0/0x70 [<c02e74b6>] blkio_schedule+0x186/0x190 [<c011e070>] default_wake_function+0x0/0x20 [<c010a662>] ret_from_fork+0x6/0x14 [<c011e070>] default_wake_function+0x0/0x20 [<c02e7330>] blkio_schedule+0x0/0x190 [<c0108615>] kernel_thread_helper+0x5/0x10 Kernel panic - not syncing: BUG!>Precisely which adaptec card is it, what driver? > >SCSI storage controller: Adaptec AIC-7901 U320 (rev 10)>Thanks, >Ian > > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> >I can''t see why creating a domU would be helped by a swiotlb. > > > Without it, dom0 crashes. I reported on Bugzilla #168 a > couple of days ago the following crash when creating a domU > on machines built with PAE: > > Fatal DMA error! Please use ''swiotlb=force'' > kernel BUG at arch/xen/i386/kernel/pci-dma.c:30 (iommu_bug)! > [<c010ea0b>] iommu_bug+0x3b/0x50 > [<c010eb6a>] dma_map_sg+0x14a/0x170 > [<c02f5023>] ide_map_sg+0xa3/0xb0 > [<c02fe86c>] ide_build_sglist+0x7c/0xd0 [<c02fe8ff>] > ide_build_dmatable+0x3f/0x190 [<c02fedda>] > ide_dma_setup+0x3a/0xe0 [<c0301120>] > __ide_do_rw_disk+0x3d0/0x5a0 [<c02f6f00>] > ide_wait_stat+0+30/0x230 [<c02837fc>] > as_move_to_dispatch+0xec/0x220 [<c02f5550>] > start_request+0x270/0x290 [<c02f581c>] > ide_do_request+0x27c/0x470 [<c027940c>] > elv_next_request+0x3c/0x1b0 [<c02f5a34>] > do_ide_request+0x24/0x30 [<c027c62a>] > generic_unplug_device+0x2a/0x70 [<c027c600>] > generic_unplug_device+0x0/0x70 [<c02e74b6>] > blkio_schedule+0x186/0x190 [<c011e070>] > default_wake_function+0x0/0x20 [<c010a662>] > ret_from_fork+0x6/0x14 [<c011e070>] > default_wake_function+0x0/0x20 [<c02e7330>] > blkio_schedule+0x0/0x190 [<c0108615>] > kernel_thread_helper+0x5/0x10 Kernel panic - not syncing: BUG! > > >Precisely which adaptec card is it, what driver? > > > SCSI storage controller: Adaptec AIC-7901 U320 (rev 10)This backtrace looks like its doing ide transfers. Have you got active ide devices in this system? Also, please can you rerun this test as the debugging output has been improved. Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt wrote:> > > > >>>I can''t see why creating a domU would be helped by a swiotlb. >>> >>> >>> >>Without it, dom0 crashes. I reported on Bugzilla #168 a >>couple of days ago the following crash when creating a domU >>on machines built with PAE: >> >>Fatal DMA error! Please use ''swiotlb=force'' >>kernel BUG at arch/xen/i386/kernel/pci-dma.c:30 (iommu_bug)! >> [<c010ea0b>] iommu_bug+0x3b/0x50 >> [<c010eb6a>] dma_map_sg+0x14a/0x170 >> [<c02f5023>] ide_map_sg+0xa3/0xb0 >> [<c02fe86c>] ide_build_sglist+0x7c/0xd0 [<c02fe8ff>] >>ide_build_dmatable+0x3f/0x190 [<c02fedda>] >>ide_dma_setup+0x3a/0xe0 [<c0301120>] >>__ide_do_rw_disk+0x3d0/0x5a0 [<c02f6f00>] >>ide_wait_stat+0+30/0x230 [<c02837fc>] >>as_move_to_dispatch+0xec/0x220 [<c02f5550>] >>start_request+0x270/0x290 [<c02f581c>] >>ide_do_request+0x27c/0x470 [<c027940c>] >>elv_next_request+0x3c/0x1b0 [<c02f5a34>] >>do_ide_request+0x24/0x30 [<c027c62a>] >>generic_unplug_device+0x2a/0x70 [<c027c600>] >>generic_unplug_device+0x0/0x70 [<c02e74b6>] >>blkio_schedule+0x186/0x190 [<c011e070>] >>default_wake_function+0x0/0x20 [<c010a662>] >>ret_from_fork+0x6/0x14 [<c011e070>] >>default_wake_function+0x0/0x20 [<c02e7330>] >>blkio_schedule+0x0/0x190 [<c0108615>] >>kernel_thread_helper+0x5/0x10 Kernel panic - not syncing: BUG! >> >> >> >>>Precisely which adaptec card is it, what driver? >>> >>> >>> >>SCSI storage controller: Adaptec AIC-7901 U320 (rev 10) >> >> > >This backtrace looks like its doing ide transfers. Have you got active >ide devices in this system? > >Actually, the trace was obtained from a machine that has an IDE drive. It was one of two that exhibited this behavior (the other has the SCSI drive), and the only one where I could capture the console log.>Also, please can you rerun this test as the debugging output has been >improved. > > >I''ll do that as soon as I can get the machine back; it is being used to look into another issue at the moment.>Thanks, >Ian > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
August 19, 2005 using hg source as of:
changeset: 6276:87dec3b9c54609eb913b9776020bf040ecec476c
tag: tip
parent: 6275:6c8c3df37bfe5f8d1fa29409e454172e1bc29f21
parent: 6274:3c1cd2486b7fecd5d97378a7d52e5bfb8eb7c718
user: cl349@firebug.cl.cam.ac.uk
date: Fri Aug 19 10:22:05 2005
summary: merge?
x86_32 (no PAE support)
1. SLES 9 SP2 on IBM xSeries 235 (512M RAM)and FC3 on IBM ThinkCentre
2. Builds and boots without problems
3. Able to create domU
4. Ran LTP on both dom0 and domU
5. No problems observed
Last good changeset for x86_32, non-PAE:
changeset: 6276:87dec3b9c54609eb913b9776020bf040ecec476c
tag: tip
parent: 6275:6c8c3df37bfe5f8d1fa29409e454172e1bc29f21
parent: 6274:3c1cd2486b7fecd5d97378a7d52e5bfb8eb7c718
user: cl349@firebug.cl.cam.ac.uk
date: Fri Aug 19 10:22:05 2005
summary: merge?
x86_32 (PAE)
1. SLES 9 SP2, FC3, and RHEL 4 IBM xSeries 305, and
ThinkCentre
* Machines boot up now
* Ran LTP on dom0 without swiotlb=force and machine stayed up
2. Boots on RHEL 4, SLES 9 SP2 and FC3.
* Booted Dom0 using swiotlb=force
* Ran LTP on both Dom0 and DomU
3. ISSUES:
1. DomU boot crashes Dom0, Bugzilla #168
1. Workaround: use swiotlb=force as a kernel
parameter when booting Dom0
2. DomU boots up normally if using swiotlb=force
2. X server will not come up on Dom0 on a FC3 box when Xen
built with PAE ''on'', Bugzilla #137
3. Networking issue on FC3 when Xen built with PAE, Bugzilla
#173
* DomU unable to get dhcp address
* tcpdump shows lots of networking activity being
''heard''
* ping from external box shows corrupt packets
* DomU has no trouble getting IP address when Xen built
non-PAE, however
Last good changeset for x86_32, PAE:
changeset: 6124:38bee85ddeb83378eb9ba9b692cc39499d6a05d4
tag: tip
parent: 6120:f6d6d17eaeb5f04efea7f9d8f753a91ffff0479d
parent: 6123:1fb1877ed6d1b2ae5b130e4d3e29fc06ef58db3c
user: kaf24@firebug.cl.cam.ac.uk
date: Fri Aug 12 08:29:57 2005
summary: merge
x86_64
1. SLES 9 SP2 and FC4 on IBM HS20 Blades
2. Xen build break on both distros
3. ISSUES:
* Bugzilla #169 - x86_64 - Unable to handle kernel paging
request at ffff8000003e0000 RIP:
<ffffffff8015d16c>{unmap_vmas+1084}
* Bugzilla #175 - x86_64 Build break - undefined reference to
`HYPERVISOR_vcpu_pickle''
o Some work going on to fix
o jun.nakajima@intel.com and ryanh@us.ibm.com working to
fix it
Last good changeset for x86_64:
changeset: 6228:1a94949348ff52863b9fbef4eaf102c7e46a345d
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Thu Aug 18 05:41:55 2005
summary: Fix range_straddles_boundary() check to exclude regions that
-- Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. " Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel