Skip to contentSkip to conversation

xm-test block device write verify test

PATCH In review Harry Butterworth 2 participants 3 messages May 22, 2006

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 xm-test block device write verify test

Quoted 1 line

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.

tools/xm-test/grouptest/default +1 -0
diff -r 14717dedba02 -r 431fef753c71 tools/xm-test/grouptest/default
@@ -1,6 +1,7 @@
 block-create
 block-destroy
 block-list
+block-integrity
 console
 create
 destroy
tools/xm-test/ramdisk/configs/busybox +3 -3
diff -r 14717dedba02 -r 431fef753c71 tools/xm-test/ramdisk/configs/busybox
@@ -92,7 +92,7 @@
 CONFIG_FALSE=y
 # CONFIG_FOLD is not set
 CONFIG_HEAD=y
-# CONFIG_FEATURE_FANCY_HEAD is not set
+CONFIG_FEATURE_FANCY_HEAD=y
 CONFIG_HOSTID=y
 CONFIG_ID=y
 CONFIG_INSTALL=y
@@ -127,8 +127,8 @@
 CONFIG_SYNC=y
 CONFIG_TAIL=y
 CONFIG_FEATURE_FANCY_TAIL=n
-CONFIG_TEE=n
-CONFIG_FEATURE_TEE_USE_BLOCK_IO=n
+CONFIG_TEE=y
+CONFIG_FEATURE_TEE_USE_BLOCK_IO=y
 CONFIG_TEST=y
 
 #
tools/xm-test/tests/block-integrity/Makefile.am +2 -1
diff -r 14717dedba02 -r 431fef753c71 tools/xm-test/tests/block-integrity/Makefile.am
@@ -1,7 +1,8 @@
 
 SUBDIRS =
 
-TESTS = 01_block_device_read_verify.test
+TESTS = 01_block_device_read_verify.test \
+        02_block_device_write_verify.test
 
 XFAIL_TESTS = 
 
tools/xm-test/tests/block-integrity/02_block_device_write_verify.py new file +63 -0

63 lines not on this page · raw message

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

#1 lore raw

Hi Harry,

We usually bump the xm-test version in configure.ac when we change the ramdisk, for compatibility reasons.

Thanks,

Dan

Quoted 27 lines · Harry Butterworth
Quoted 1 line

From the patch:

(quoted diff) +2 -0
+# 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).

(quoted diff) +2 -0
+# 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
[email protected]
http://lists.xensource.com/xen-devel

#2 lore raw

OK. I'll do another patch tomorrow.

Quoted 45 lines · Daniel Stekloff

Hi Harry,

We usually bump the xm-test version in configure.ac when we change the ramdisk, for compatibility reasons.

Thanks,

Dan

Quoted 21 lines · Harry Butterworth
Quoted 1 line

From the patch:

(quoted diff) +2 -0
+# 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).

(quoted diff) +2 -0
+# 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.

Quoted 6 lines

The patch also installs the block-integrity tests in the default test set so they get executed.
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel