From: Eric Biggers <ebiggers@xxxxxxxxxx> Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx> --- Documentation/gce-xfstests.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/Documentation/gce-xfstests.md b/Documentation/gce-xfstests.md index becc23d..1b7fa3e 100644 --- a/Documentation/gce-xfstests.md +++ b/Documentation/gce-xfstests.md @@ -306,12 +306,14 @@ to be unpacked into a directory in /tmp instead. By default gce-xfstests uses the prebuilt image which is made available via the xfstests-cloud project. However, if you want to -build your own image, you must first build the xfstests tarball as -described in the [instructions for building -xfstests](building-xfstests.md). Then run the command "gce-xfstests -create-image". This will create a new GCE image with a name such as -"xfstests-201608132226" where 201608132226 indicates when the image -was created (in this case, August 13, 2016 at 22:26). +build your own image, you must first build a 64-bit (amd64) xfstests +tarball as described in the [instructions for building +xfstests](building-xfstests.md). Then copy any additional Debian +packages, for the amd64 architecture, you want to include in the GCE +image into the root directory of GS_BUCKET. Then run the command +"gce-xfstests create-image". This will create a new GCE image with a +name such as "xfstests-201608132226" where 201608132226 indicates when +the image was created (in this case, August 13, 2016 at 22:26). This image will be created as part of an image family called xfstests. By default, when you start a test using gce-xfstests, the most -- 2.8.0.rc3.226.g39d4020 -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
