From: Matt Ayres <matta@tektonic.net>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [Xen-users] xen 3.0 Test CD v1 released
Date: Fri, 25 Nov 2005 12:33:48 -0500 [thread overview]
Message-ID: <43874AFC.7030604@tektonic.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32EBA8@liverpoolst.ad.cl.cam.ac.uk>
Ian,
Can you comment if the bugs I've reported in bugzilla #'s 402, 405, and
406 have been fixed/assigned? I tried to change a few of our
(unixshell.com) users over to a 3.0 server and it turned out poorly. We
have serial console (with logging) setup for our servers so when a
system panics or sends an oops so I am more than capable of capturing it
submitting bugs for any troubles, but I received those different 3
panics and the system couldn't stay up for more than a few hours (I had
even tried turning off PAE and SMP support). This was all using
snapshots from around 11/13. I know there have been many, many commits
since then.
Thanks,
Matt
Ian Pratt wrote:
> Folks,
>
> As you're probably aware we've been running a number of different
> initiatives to test the xen -unstable tree prior to release as 3.0.0: We
> have the XenRT automated regression test suite which gives Xen a
> thorough workout on a range of different machines every night. Among
> other tests, XenRT incorporates the excellent xm-test suite to stress
> xend. We're also running various ISV application validation suites over
> Xen. There's also all the testing that's going on in the community, and
> the daily reports from IBM and Intel. All indications are that we're
> getting very close to release quality.
>
next prev parent reply other threads:[~2005-11-25 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 14:18 xen 3.0 Test CD v1 released Ian Pratt
2005-11-25 17:33 ` Matt Ayres [this message]
2005-11-25 17:39 ` Re: [Xen-users] " Keir Fraser
2005-11-27 20:35 ` Matt Ayres
2005-11-28 16:54 ` Fraser Campbell
2005-11-30 11:51 ` Chris Bainbridge
2005-11-30 18:32 ` Joe Ammond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43874AFC.7030604@tektonic.net \
--to=matta@tektonic.net \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.