aboutsummaryrefslogtreecommitdiffstats
path: root/tools/xm-test/tests/block-integrity
Commit message (Collapse)AuthorAgeFilesLines
* Update all block tests to use the Xen Virtual Block Device (xvd) rather than ↵Ewan Mellor2006-11-012-4/+4
| | | | | | | | | | | | IDEor SCSI. This patch also modifies 09_block_attach_and_dettach_device_check_data_pos.py to force / to be read-write otherwise the mkdir fails. Also Whistspace cleanups. Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
* [XM-TEST] Fix 02_block_device_write_verify.py test to parse md5sum output ↵kaf24@firebug.cl.cam.ac.uk2006-06-132-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | correctly. The 02_block_device_write_verify.py test that I wrote is failing because the regular expression to extract the md5sum is only looking at the first line of output and the sum is in a subsequent line (after the output from dd). This patch fixes the test by adding the multiline flag to the search parameters so that the search looks in all lines of the output for the md5sum. I added the multiline flag in all searches to make the tests more robust against changes in the output format of the commands used. I'm not exactly sure how this slipped through my testing. I suspect that I forgot to install the new python file after updating the test to use dd and then tested the old version a second time by accident. Either that or it really did work when I tested it and the output format has changed for some reason. I tested this patch against xen-unstable 10326 and the 02 test fails without the patch and succeeds with it. Thanks to James Dykman for some help with this. Signed-off-by Harry Butterworth <butterwo@uk.ibm.com>
* Block device write-verify test.emellor@leeni.uk.xensource.com2006-06-012-1/+65
| | | | | | | | | | | | | | | | | | | | | | 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 in BusyBox on the ramdisk and increments the xm-test version number to 0.8.0. The patch also installs the block-integrity tests in the default test set so they get executed. Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com> Signed-off-by: Ewan Mellor <ewan@xensource.com>
* Add a read-verify block device test to xm-test.harry@localhost.localdomain2006-05-192-0/+83