From: Eric Blake <eblake@redhat.com>
To: 陳培泓 <pahome.chen@mirlab.org>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Can I mount encrypt qcow2?
Date: Mon, 24 Jul 2017 07:25:39 -0500 [thread overview]
Message-ID: <deb984a7-3d71-9db0-f3fb-eaf12c13064e@redhat.com> (raw)
In-Reply-To: <CAB3eZfsDUpcYDLogUuz4H-X-petqnc4+hXwkXjO3v1jrRB=r2w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
On 07/23/2017 08:49 PM, 陳培泓 wrote:
> I check to the newest version of qemu.
You're still top-posting, which makes it really hard to answer your
questions.
>
> and do the cmds to install followed by the documents in github:
>
>> mkdir build
>> cd build
>> ../configure
>> make
>
>
> and it show nothing errors
> It's the version when I enter qemu-img --help:
>
> and I execute encrypt format(luks) to the qcow2 file:
>
>
Attaching inline images is a horrible waste of bandwidth, compared to
copying-and-pasting the terminal text directly. Furthermore, your email
is illegible in a plain-text client (like what I prefer to use), and
requires that I switch to html view to even understand what you are asking.
> always shows the error, how to solve it?
Transcribing one of your images:
> pahome@pahome-QW09:~/git/qemu/build$ ./qemu-img --help
> qemu-img version 2.9.0 (v2.9.0-dirty)
You aren't building the latest version of qemu.git. If you were, you'd
be getting something like this:
$ ./qemu-img --help | head -n1
qemu-img version 2.9.50 (v2.9.0-2519-gb52f59694d)
Before you can complain that something recently added isn't working, you
first have to make sure you are building the right version.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-07-24 12:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 2:43 [Qemu-devel] Can I mount encrypt qcow2? 陳培泓
2017-07-20 8:59 ` Daniel P. Berrange
2017-07-20 9:07 ` 陳培泓
2017-07-20 9:12 ` Daniel P. Berrange
2017-07-21 1:44 ` 陳培泓
2017-07-21 8:38 ` Daniel P. Berrange
2017-07-21 9:31 ` 陳培泓
2017-07-21 9:34 ` Daniel P. Berrange
2017-07-21 9:41 ` 陳培泓
2017-07-21 12:18 ` Eric Blake
2017-07-21 14:05 ` Eric Blake
2017-07-21 14:06 ` Daniel P. Berrange
2017-07-21 14:18 ` Eric Blake
2017-07-24 1:49 ` 陳培泓
2017-07-24 12:25 ` Eric Blake [this message]
2017-07-25 4:26 ` lampahome
2017-07-25 11:26 ` Eric Blake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=deb984a7-3d71-9db0-f3fb-eaf12c13064e@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=pahome.chen@mirlab.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).