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>
Made it a minor release bump for xm-test so old ramdisk will work. The
ramdisk is functionally the same.
Signed-off-by: Daniel Stekloff <dsteklof@us.ibm.com>
was getting is no longer there, they've pruned the snapshots. This patch
adds a new buildroot and updates the buildroot configuration. I also
incremented the xm-test release version to 0.8.
Signed-off-by: Daniel Stekloff <dsteklof@us.ibm.com>
to 15feb06, update to Makefile.am. The original gcc-mirror patch is
removed and the buildroot configuration updated.
Signed-off-by: Woody Marvel <marvel@us.ibm.com>
because the create script doesn't load the pcnet32 driver to the disk.img
when it copies the kernel there. This is the first step to make network
support possible for VMX guest testing.
This patch adds busybox support for loading 2.6 kernel modules. Since the
image changes, I have adjusted the xm-test version too.
Signed-off-by: Daniel Stekloff <dsteklof@us.ibm.com>
This is the first change to the ramdisk since v0.1.0. So, we now build
the image as initrd-X.Y.img, and link initrd.img to it. This lets us
have a few checks to make sure that people rebuild their ramdisks when
necessary.