From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Butterworth Subject: Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt Date: Wed, 24 May 2006 10:52:52 +0100 Message-ID: <1148464373.7791.4.camel@localhost.localdomain> References: <1148380556.10003.4.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1148380556.10003.4.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Signed-off-by: Harry Butterworth On Tue, 2006-05-23 at 11:35 +0100, Harry Butterworth wrote: > The only difference from the last version of the patch is that the minor > version number in configure.ac is incremented. > > >From the patch: > > +# This test imports a ram disk device as a physical device into a domU. > +# The domU initialises the ram disk with data from /dev/urandom and > calculates > +# the md5 checksum of the data (using tee as it is written so as to > avoid > +# reading it back from the device which might potentially mask > problems). > +# The domU is stopped and the md5 checksum of the data on the device is > +# calculated by dom0. The test succeeds if the checksums match, > indicating > +# that all the data written by domU was sucessfully committed to the > device. > + > > This patch also enables tee and fancy head in busybox on the ramdisk. I > have tested the patch with both `make existing' where the tests run but > the new test fails because the ramdisk is missing tee and fancy head and > `make` where the test passes successfully. > > The patch also installs the block-integrity tests in the default test > set so they get executed. > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel