|
From: | lejeczek |
Subject: | Re: 'qemu-img create' to backup encrypted qcow2 - ? |
Date: | Sun, 15 Aug 2021 17:25:07 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 |
On 15/08/2021 13:17, Peter Maydell wrote:
Almost identical to the original, only take out 'options' out and put in front of '-b' (or any other place in cmd args order)On Sun, 15 Aug 2021 at 13:07, lejeczek <peljasz@yahoo.co.uk> wrote:On 14/08/2021 11:19, Peter Maydell wrote:On Sat, 14 Aug 2021 at 08:24, lejeczek <peljasz@yahoo.co.uk> wrote:-> $ qemu-img create -f qcow2 -b -o encrypt.key-secret=3fd57349-3671-4cf2-ab00-f13b8ba00a4d /00.GLUSTER-mnt/VMs3/enc.locallan.qcow2 -F qcow2 ./enc.locallan.qcow2.bkp qemu-img: Invalid image size specified. You may use k, M, G, T, P or E suffixes for qemu-img: kilobytes, megabytes, gigabytes, terabytes, petabytes and exabytes.The '-b' option needs a backing_file argument, but the next thing on your commandline is "-o". The option parser has thus assumed you meant to say that the backing-file is named "-o", and has then completely misinterpreted the rest of your commandline as a result. Delete the '-o', or, if you wanted to specify options, put "-o whatever-options-you-wanted" somewhere else than between the '-b' and its argument.There is no other syntax I could put together which would not end up in: ... qemu-img: ./enc.locallan.qcow2.bkp: Parameter 'encrypt.key-secret' is required for cipher Could not open backing image to determine size.How about you say what command line(s) you tried that gave that error message ? -- PMM
[Prev in Thread] | Current Thread | [Next in Thread] |