From: Roman Penyaev <rpenyaev@suse.de>
To: Manuel Bentele <manuel-bentele@web.de>
Cc: Hannes Reinecke <hare@suse.de>,
linux-block@vger.kernel.org, linux-block-owner@vger.kernel.org
Subject: Re: Adding QCOW2 reading/writing support
Date: Tue, 14 May 2019 16:28:45 +0200 [thread overview]
Message-ID: <7a74dd35a390df25f2874aa7b4f8547e@suse.de> (raw)
In-Reply-To: <762bceb9-c66c-0a45-7d6b-e5ed0df56cbf@web.de>
On 2019-04-17 23:53, Manuel Bentele wrote:
[cut]
> If you have an idea to solve the opposition for file formats that are
> acting as a container or virtual disk node for various data, please let
> me know.
If you need a raw block device you can export qcow2 image as a network
block
device, something as the following:
# modprobe nbd
# qemu-nbd --connect=/dev/nbd0 image.qcow2
# fdisk -l /dev/nbd0
I suppose simplest variant.
--
Roman
next prev parent reply other threads:[~2019-05-14 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 21:30 Adding QCOW2 reading/writing support Manuel Bentele
2019-04-17 1:35 ` Ming Lei
2019-04-17 11:32 ` Manuel Bentele
2019-04-17 12:16 ` Hannes Reinecke
2019-04-17 21:04 ` Manuel Bentele
2019-04-18 1:05 ` Ming Lei
2019-04-18 10:02 ` Manuel Bentele
2019-05-14 8:56 ` Manuel Bentele
2019-04-17 11:58 ` Hannes Reinecke
2019-04-17 21:53 ` Manuel Bentele
2019-05-14 14:28 ` Roman Penyaev [this message]
2019-05-20 13:05 ` Manuel Bentele
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=7a74dd35a390df25f2874aa7b4f8547e@suse.de \
--to=rpenyaev@suse.de \
--cc=hare@suse.de \
--cc=linux-block-owner@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=manuel-bentele@web.de \
/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).