The text describing `create' qemu-img subcommand refers to backing_file, but it is not mentioned anywhere in the syntax for this subcommand.
Signed-off-by: Michael Tokarev <[email protected]> diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx index 39419a0..82c6e38 100644 --- a/qemu-img-cmds.hx +++ b/qemu-img-cmds.hx @@ -16,9 +16,9 @@ STEXI ETEXI DEF("create", img_create, - "create [-f fmt] [-o options] filename [size]") + "create [-f fmt] [-o options] [-b backing_file] filename [size]") STEXI -@item create [-f @var{fmt}] [-o @var{options}] @var{filename} [@var{size}] +@item create [-f @var{fmt}] [-o @var{options}] [-b @var{backing_file}] @var{filename} [@var{size}] ETEXI DEF("commit", img_commit, diff --git a/qemu-img.texi b/qemu-img.texi index 6b42e35..4fbf2ed 100644 --- a/qemu-img.texi +++ b/qemu-img.texi @@ -92,7 +92,7 @@ wrong fix or hiding corruption that has already occured. Only the formats @code{qcow2}, @code{qed} and @code{vdi} support consistency checks. -@item create [-f @var{fmt}] [-o @var{options}] @var{filename} [@var{size}] +@item create [-f @var{fmt}] [-o @var{options}] [-b @var{backing_file}] @var{filename} [@var{size}] Create the new disk image @var{filename} of size @var{size} and format @var{fmt}. Depending on the file format, you can add one or more @var{options}
