[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Purpose of stacking block devices
|
From: |
Raphael Pour |
|
Subject: |
Re: Purpose of stacking block devices |
|
Date: |
Wed, 21 Oct 2020 10:57:04 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1 |
I messed up the order of the block devices. However this is the original
statement I meant:
"Driver-specific options for raw
This is the image format block driver for raw images. It is usually
stacked on top of a protocol level block driver such as file."
On 10/21/20 8:23 AM, Raphael Pour wrote:
> Hello,
>
> could someone explain me the purpose of stacking block devices on top of
> each other?
>
> A block device with driver file or qcow2 "is usually" stacked on top of
> a block device with driver raw as stated in the docs[1].
>
> The related sentence came with [2] within the batch [3]. I couldn't
> figure out why this 'stacking' might be useful.
>
> Thanks and kind regards,
> Raphael
>
>
> [1] Driver-specific options for raw:
> https://qemu.weilnetz.de/doc/latest/system/invocation.html#hxtool-1
> [2] doc: Document driver-specific -blockdev option:
> https://lists.nongnu.org/archive/html/qemu-devel/2017-06/msg05325.html
> [3] [Qemu-devel] [PULL 00/61] Block layer patches:
> https://lists.nongnu.org/archive/html/qemu-devel/2017-06/msg05319.html
>
--
Hetzner Online GmbH
Am Datacenter-Park 1
08223 Falkenstein/Vogtland
raphael.pour@hetzner.com
www.hetzner.com
Registergericht Ansbach, HRB 6089
Geschäftsführer: Martin Hetzner, Stephan Konvickova, Günther Müller