block read verify patch for xm-test
PATCH 1/1 block read verify patch for xm-test
Quoted 1 line
From the patch:
+# This test initialises a ram disk in dom0 with data from /dev/urandom and
+# then imports the ram disk device as a physical device into a domU. The md5
+# checksum of the data in the ramdisk is calculated in dom0 and also +# calculated by the domU reading the data through the blk frontend and +# backend drivers. The test succeeds if the checksums match indicating that
+# the domU successfully read all the correct data from the device.
# HG changeset patch
# User [email protected]
# Node ID 338e4db7e21bcb37917f2eaaccab6eaa7950e69b # Parent 062d109ce87292cef784db169add4c649879200d Add a read-verify block device test to xm-test.
tools/xm-test/configure.ac +1 -0
@@ -99,6 +99,7 @@ tests/block-list/Makefile tests/block-create/Makefile tests/block-destroy/Makefile + tests/block-integrity/Makefile tests/console/Makefile tests/create/Makefile tests/destroy/Makefile
tools/xm-test/tests/Makefile.am +4 -3
@@ -1,14 +1,15 @@ SUBDIRS = \ block-create \ - block-list \ - block-destroy \ + block-list \ + block-destroy \ + block-integrity \ console \ create \ destroy \ dmesg \ domid \ domname \ - help \ + help \ info \ list \ memmax \
tools/xm-test/tests/block-integrity/01_block_device_read_verify.py new file +62 -0
62 lines not on this page · raw message
tools/xm-test/tests/block-integrity/Makefile.am new file +21 -0
@@ -0,0 +1,21 @@ + +SUBDIRS = + +TESTS = 01_block_device_read_verify.test + +XFAIL_TESTS = + +EXTRA_DIST = $(TESTS) $(XFAIL_TESTS) + +TESTS_ENVIRONMENT=@TENV@ + +%.test: %.py + cp $< $@ + chmod +x $@ + +clean-local: am_config_clean-local + +am_config_clean-local: + rm -f *test + rm -f *log + rm -f *~
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Ewan Mellor
AppliedQuoted 12 lines · Harry Butterworth
Quoted 1 line
From the patch:
+# This test initialises a ram disk in dom0 with data from
/dev/urandomand
+# then imports the ram disk device as a physical device into a domU. The md5tools/xm-test/tests/block-integrity/01_block_device_read_verify.py new file +3
-0+# checksum of the data in the ramdisk is calculated in dom0 and also +# calculated by the domU reading the data through the blk frontend and +# backend drivers. The test succeeds if the checksums match indicatingthat
+# the domU successfully read all the correct data from the device.
Quoted 2 lines
Signed-off-by Harry Butterworth <[email protected]>
Applied, thanks Harry.
Ewan.