[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] Re: block: format vs. protocol, and how they stack
From: |
Kevin Wolf |
Subject: |
[Qemu-devel] Re: block: format vs. protocol, and how they stack |
Date: |
Tue, 22 Jun 2010 10:10:27 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Thunderbird/3.0.4 |
Am 21.06.2010 17:34, schrieb Anthony Liguori:
> On 06/21/2010 09:01 AM, Kevin Wolf wrote:
>>
>> No, what I'm saying is that even in your model
>>
>> -blockdev format=qcow2,file=image.qcow2,id=blk1
>>
>> becomes qcow2 -> file automatically, whereas
>>
>> -blockdev format=vvfat,file=/tmp/dir/,id=blk1
>>
>> doesn't become vvfat -> file, but stays just vvfat.
>>
>
> I should say, that -blockdev format= vs. -blockdev transport= is
> definitely at a place where I don't care that much.
>
> The things that I think are most important are:
>
> 1) That we have structured options that map well to config file without
> trickery to do nesting
> 2) That we don't automagically pass options through from the first layer
> down to subsequent layers
Does this mean that you need to specify the protocol explicitly for any
non-trivial case? So if you want to use just default for everything you
can use
-blockdev id=foo,format=qcow2,file=foo.qcow2
and it will be turned into something sensible automagically (namely
adding a file blockdev underneath and passing the file parameter to that
one), but if you want to change an option, you need to specify both?
-blockdev id=foo,format=qcow2,parent=foo_file
-blockdev id=foo_file,format=file,file=foo.qcow2,cache=off
What about read-only? Is it something that must be specified for each
single node in the chain to actually get the right semantics?
Kevin
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, (continued)
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Anthony Liguori, 2010/06/21
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Christoph Hellwig, 2010/06/21
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Anthony Liguori, 2010/06/21
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Markus Armbruster, 2010/06/21
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Markus Armbruster, 2010/06/21
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Kevin Wolf, 2010/06/22
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Markus Armbruster, 2010/06/22
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Christoph Hellwig, 2010/06/28
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Jamie Lokier, 2010/06/22
- [Qemu-devel] Re: block: format vs. protocol, and how they stack, Anthony Liguori, 2010/06/21
- [Qemu-devel] Re: block: format vs. protocol, and how they stack,
Kevin Wolf <=
- [Qemu-devel] Re: block: format vs. protocol, and how they stack, Anthony Liguori, 2010/06/22
- [Qemu-devel] Re: block: format vs. protocol, and how they stack, Kevin Wolf, 2010/06/22
- [Qemu-devel] Re: block: format vs. protocol, and how they stack, Anthony Liguori, 2010/06/22
- [Qemu-devel] Re: block: format vs. protocol, and how they stack, Markus Armbruster, 2010/06/21
- [Qemu-devel] Re: block: format vs. protocol, and how they stack, Kevin Wolf, 2010/06/22
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Jamie Lokier, 2010/06/22
- Re: [Qemu-devel] Re: block: format vs. protocol, and how they stack, Daniel P. Berrange, 2010/06/22