Re: [Xen-devel] [PATCH] xm-test block device write verify test

[Harry Butterworth <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

OK.  I'll do another patch tomorrow.

On Mon, 2006-05-22 at 12:02 -0700, Daniel Stekloff wrote:
> Hi Harry,
> 
> We usually bump the xm-test version in configure.ac when we change the
> ramdisk, for compatibility reasons.
> 
> Thanks,
> 
> Dan
> 
> 
> On Mon, 2006-05-22 at 17:51 +0100, Harry Butterworth wrote:
> > >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@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> 
> 
> _______________________________________________
> 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