| To: | Harry Butterworth <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] [PATCH] xm-test block device write verify test |
| From: | Daniel Stekloff <dsteklof@xxxxxxxxxx> |
| Date: | 2006年5月22日 12:02:47 -0700 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | 2006年5月22日 12:03:18 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <1148316664.7701.41.camel@xxxxxxxxxxxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <1148316664.7701.41.camel@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] Q: How to find own domid or uuid from domU? , Andrew D. Ball |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] Make "xm mem-set" be lowerboundondomX-min-mem , Ky Srinivasan |
| Previous by Thread: | [Xen-devel] [PATCH] xm-test block device write verify test , Harry Butterworth |
| Next by Thread: | Re: [Xen-devel] [PATCH] xm-test block device write verify test , Harry Butterworth |
| Indexes: | [Date] [Thread] [Top] [All Lists] |