Am 22.02.2018 um 12:40 schrieb Daniel P. Berrangé:
> On Thu, Feb 22, 2018 at 12:32:04PM +0100, Kevin Wolf wrote:
>> Am 22.02.2018 um 12:01 hat Peter Lieven geschrieben:
>>> Am 22.02.2018 um 11:57 schrieb Kevin Wolf:
>>>> Am 20.02.2018 um 22:54 hat Paolo Bonzini gesch
Am 22.02.2018 um 12:32 schrieb Kevin Wolf:
> Am 22.02.2018 um 12:01 hat Peter Lieven geschrieben:
>> Am 22.02.2018 um 11:57 schrieb Kevin Wolf:
>>> Am 20.02.2018 um 22:54 hat Paolo Bonzini geschrieben:
>>>> On 20/02/2018 18:04, Peter Lieven wrote:
>>>>
Hi,
I stumbled across the MAX_INFLIGHT_IO field that was introduced in 2015 and was
curious what was the reason
to choose 512MB as readahead? The question is that I found that the source VM
gets very unresponsive I/O wise
while the initial 512MB are read and furthermore seems to stay
Am 22.02.2018 um 11:57 schrieb Kevin Wolf:
> Am 20.02.2018 um 22:54 hat Paolo Bonzini geschrieben:
>> On 20/02/2018 18:04, Peter Lieven wrote:
>>> Hi,
>>>
>>> I remember we discussed a long time ago to limit the stack usage of all
>>> functions
Hi,
I remember we discussed a long time ago to limit the stack usage of all
functions that are executed in a coroutine
context to a very low value to be able to safely limit the coroutine stack size
as well.
I checked through all functions in block/, migration/ and nbd/ and there are
only
Am 15.02.2018 um 18:27 schrieb Stefan Hajnoczi:
On Thu, Feb 15, 2018 at 03:24:54PM +0100, Peter Lieven wrote:
Am 15.02.2018 um 12:15 schrieb Stefan Hajnoczi:
The libiscsi iscsi_task_mgmt_async() API documentation says:
abort_task will also cancel the scsi task. The callback for the scsi
this patch makes the bulk phase of a block migration to take
place before we start transferring ram. As the bulk block migration
can take a long time its pointless to transfer ram during that phase.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
migration/ram.c | 8
1 file chan
Am 12.02.2018 um 17:13 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (p...@kamp.de) wrote:
>> Am 06.02.2018 um 20:14 schrieb Michael Roth:
>>> Hi everyone,
>>>
>>> The following new patches are queued for QEMU stable v2.11.1:
>>>
>>>http
Am 15.02.2018 um 12:15 schrieb Stefan Hajnoczi:
The libiscsi iscsi_task_mgmt_async() API documentation says:
abort_task will also cancel the scsi task. The callback for the scsi
task will be invoked with SCSI_STATUS_CANCELLED
The libiscsi implementation does not fulfil this promise. The
Am 13.02.2018 um 23:23 schrieb Michael S. Tsirkin:
> On Tue, Feb 13, 2018 at 09:53:58PM +0100, Peter Lieven wrote:
>> Am 21.12.2017 um 15:29 schrieb Michael S. Tsirkin:
>>> Backends don't need to know what frontend requested a reset,
>>> and notifying then from vi
Am 21.12.2017 um 15:29 schrieb Michael S. Tsirkin:
> Backends don't need to know what frontend requested a reset,
> and notifying then from virtio_error is messy because
> virtio_error itself might be invoked from backend.
>
> Let's just set the status directly.
>
> Cc: qemu-sta...@nongnu.org
>
Am 06.02.2018 um 20:14 schrieb Michael Roth:
Hi everyone,
The following new patches are queued for QEMU stable v2.11.1:
https://github.com/mdroth/qemu/commits/stable-2.11-staging
The release is planned for 2017-02-14:
https://wiki.qemu.org/Planning/2.11
Please respond here or CC
> Am 07.02.2018 um 19:29 schrieb Dr. David Alan Gilbert <dgilb...@redhat.com>:
>
> * Peter Lieven (p...@kamp.de) wrote:
>> Am 12.12.2017 um 18:05 schrieb Dr. David Alan Gilbert:
>>> * Peter Lieven (p...@kamp.de) wrote:
>>>> Am 21.09.2017 um 14:36 sch
Am 12.12.2017 um 18:05 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 21.09.2017 um 14:36 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 19.09.2017 um 16:41 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 19.09.2017
Am 08.01.2018 um 16:55 schrieb Eric Blake:
On 01/08/2018 09:27 AM, Peter Lieven wrote:
in case of unaligned requests or on a target that does not support
block provisioning we leave iTask uninitialized and check iTask.task
for NULL later.
Fixes: e38bc23454ef763deb4405ebdee6a1081aa00bc8
Cc
in case of unaligned requests or on a target that does not support
block provisioning we leave iTask uninitialized and check iTask.task
for NULL later.
Fixes: e38bc23454ef763deb4405ebdee6a1081aa00bc8
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven <p...@kamp.de>
Reviewed-by: Eric
csilun);
- iscsi_co_init_iscsitask(iscsilun, );
qemu_mutex_lock(>mutex);
retry:
if (iscsi_get_lba_status_task(iscsilun->iscsi, iscsilun->lun,
Peter
--
Mit freundlichen Grüßen
Peter Lieven
...
KAMP Netzwerkdienste GmbH
Vesti
Am 18.09.2017 um 12:50 schrieb Kevin Wolf:
> Am 18.09.2017 um 12:09 hat Peter Lieven geschrieben:
>> Am 11.09.2017 um 16:22 schrieb Kevin Wolf:
>>> Am 25.07.2017 um 16:41 hat Peter Lieven geschrieben:
>>>> Signed-off-by: Peter Lieven <p...@kamp.de>
>>
Am 08.12.2017 um 18:03 schrieb Eric Blake:
> On 12/08/2017 10:14 AM, Peter Lieven wrote:
>> Am 08.12.2017 um 16:11 schrieb Eric Blake:
>>> On 12/08/2017 05:51 AM, Peter Lieven wrote:
>>>> we currently report an "iSCSI Failure" in iscsi_co_gene
Am 12.12.2017 um 18:05 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (p...@kamp.de) wrote:
>> Am 21.09.2017 um 14:36 schrieb Dr. David Alan Gilbert:
>>> * Peter Lieven (p...@kamp.de) wrote:
>>>> Am 19.09.2017 um 16:41 schrieb Dr. David Alan Gilbert:
>>>
Am 08.12.2017 um 16:11 schrieb Eric Blake:
> On 12/08/2017 05:51 AM, Peter Lieven wrote:
>> we currently report an "iSCSI Failure" in iscsi_co_generic_cb if the task
>> hasn't completed with SCSI_STATUS_GOOD. However, we expect a failure in
>> some cases and handle
n the
logs can be quite misleading.
While we are at it improve the logging to reveal which operation failed
at what LBA.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/iscsi.c | 43 ---
1 file changed, 32 insertions(+), 11 deletions(-)
diff --git
we forgot to set the allocmap to invalid if an UNMAP call fails.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/iscsi.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/block/iscsi.c b/block/iscsi.c
index 4683f3b..c532ec7
fix a bug leaving the allocmap in a wrong state if an UNMAP fails and
improve the logging of iscsi failures.
Peter Lieven (2):
block/iscsi: dont leave allocmap in an invalid state on UNMAP failure
block/iscsi: only report an iSCSI Failure if we don't handle it
gracefully
block/iscsi.c
DIV_ROUND_UP(st.st_size, BDRV_SECTOR_SIZE) was overflowing ret (int) if
st.st_size is greater than 1TB.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/nfs.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/block/nfs.c b/block/nfs.c
Am 16.11.2017 um 15:47 schrieb Stefan Hajnoczi:
On Wed, Nov 15, 2017 at 11:52:46AM +, Richard W.M. Jones wrote:
[CC to qemu-devel since I'm obviously doing something wrong here,
I'm just not sure what.]
I was getting ready to add multiple threads to ‘qemu-img convert’ (the
longest part of
Am 07.11.2017 um 12:02 schrieb Markus Armbruster:
Peter Lieven <p...@kamp.de> writes:
Am 07.11.2017 um 11:22 schrieb Markus Armbruster:
Stefan Hajnoczi <stefa...@gmail.com> writes:
On Tue, Oct 17, 2017 at 01:46:25PM +0200, Kevin Wolf wrote:
Am 17.10.2017 um 12:33 hat
Am 07.11.2017 um 11:22 schrieb Markus Armbruster:
Stefan Hajnoczi <stefa...@gmail.com> writes:
On Tue, Oct 17, 2017 at 01:46:25PM +0200, Kevin Wolf wrote:
Am 17.10.2017 um 12:33 hat Peter Lieven geschrieben:
I noticed that Qemu quits at several points with an exit() if the
su
Am 17.10.2017 um 13:46 schrieb Kevin Wolf:
Am 17.10.2017 um 12:33 hat Peter Lieven geschrieben:
I noticed that Qemu quits at several points with an exit() if the
supplied parameters in the commandline are incorrect. This at some
stages happens after there have already been connections
Hi,
I noticed that Qemu quits at several points with an exit() if the supplied
parameters in the commandline are incorrect.
This at some stages happens after there have already been connections to
storage backends established.
These connections are not cleanly shut down in this case. For posix
Am 21.09.2017 um 14:36 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 19.09.2017 um 16:41 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 19.09.2017 um 16:38 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi,
I just
Am 25.09.2017 um 22:53 schrieb Michael Roth:
Quoting Peter Lieven (2017-09-21 07:32:32)
auto-converge and block migration currently do not play well together.
During block migration the auto-converge logic detects that ram
migration makes no progress and thus throttles down the vm until
of the block migration.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven <p...@kamp.de>
---
V1->V2: add comment why we disable auto-converge during bulk block migration
[Stefan]
V2->V3: add missing patch for migration/block.h
migration/block.c | 5 +
migration
Am 26.09.2017 um 12:16 schrieb Peter Lieven:
auto-converge and block migration currently do not play well together.
During block migration the auto-converge logic detects that ram
migration makes no progress and thus throttles down the vm until
it nearly stalls completely. Avoid
of the block migration.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven <p...@kamp.de>
---
V1->V2: add comment why we disable auto-converge during bulk block migration
[Stefan]
migration/block.c | 5 +
migration/ram.c | 6 +-
2 files changed, 10 insertions(+), 1 deletion
Am 25.09.2017 um 22:53 schrieb Michael Roth:
Quoting Peter Lieven (2017-09-21 07:32:32)
auto-converge and block migration currently do not play well together.
During block migration the auto-converge logic detects that ram
migration makes no progress and thus throttles down the vm until
Am 21.09.2017 um 14:36 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 19.09.2017 um 16:41 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 19.09.2017 um 16:38 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi,
I just
of the block migration.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven <p...@kamp.de>
---
migration/block.c | 5 +
migration/block.h | 7 +++
migration/ram.c | 3 ++-
3 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/migration/block.c b/migration/block.c
index 9
Am 19.09.2017 um 16:41 schrieb Paolo Bonzini:
> On 19/09/2017 15:36, Peter Lieven wrote:
>> Hi,
>>
>> I just noticed that CPU throttling and Block Migration don't work
>> together very well.
>> During block migration the throttling heuristic detects that we
>&g
Am 19.09.2017 um 16:41 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (p...@kamp.de) wrote:
>> Am 19.09.2017 um 16:38 schrieb Dr. David Alan Gilbert:
>>> * Peter Lieven (p...@kamp.de) wrote:
>>>> Hi,
>>>>
>>>> I just noticed that CPU throttl
Am 19.09.2017 um 16:38 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi,
I just noticed that CPU throttling and Block Migration don't work together very
well.
During block migration the throttling heuristic detects that we obviously make
no progress
in ram transfer
Hi,
I just noticed that CPU throttling and Block Migration don't work together very
well.
During block migration the throttling heuristic detects that we obviously make
no progress
in ram transfer. But the reason is the running block migration and not a too
high dirty pages rate.
The result
Am 11.09.2017 um 16:22 schrieb Kevin Wolf:
Am 25.07.2017 um 16:41 hat Peter Lieven geschrieben:
Signed-off-by: Peter Lieven <p...@kamp.de>
---
docs/interop/qcow2.txt | 51 +-
roms/ipxe | 2 +-
2 files changed, 51 insertions
Am 29.08.2017 um 02:13 schrieb Michael Roth:
> Hi everyone,
>
> The following new patches are queued for QEMU stable v2.9.1:
>
> https://github.com/mdroth/qemu/commits/stable-2.9-staging
>
> The release is planned for 2017-09-07:
>
> http://wiki.qemu.org/Planning/2.9
>
> Please respond here or
urn ret;
}
-qemu_mutex_init(>mutex);
+
bs->total_sectors = ret;
ret = 0;
return ret;
Reviewed-by: Peter Lieven <p...@kamp.de>
Also CC'ing qemu-stable as this affects 2.9.0 as well.
Peter
Am 04.08.2017 um 12:43 schrieb Paolo Bonzini:
> On 04/08/2017 12:27, Peter Lieven wrote:
>> Am 04.08.2017 um 12:23 schrieb Paolo Bonzini:
>>> On 04/08/2017 11:58, Peter Lieven wrote:
>>>> Am 29.10.2013 um 10:59 schrieb Paolo Bonzini:
>>>>> Il 29/10/2
Am 04.08.2017 um 12:23 schrieb Paolo Bonzini:
> On 04/08/2017 11:58, Peter Lieven wrote:
>> Am 29.10.2013 um 10:59 schrieb Paolo Bonzini:
>>> Il 29/10/2013 10:48, Peter Lieven ha scritto:
>>>> Hi all,
>>>>
>>>> this question might seem a b
Am 29.10.2013 um 10:59 schrieb Paolo Bonzini:
> Il 29/10/2013 10:48, Peter Lieven ha scritto:
>> Hi all,
>>
>> this question might seem a bit weird, but does anyone see a good way to
>> avoid
>> that Windows is able to boot inside qemu?
>>
>> W
Am 25.07.2017 um 23:55 schrieb Eric Blake:
> On 07/25/2017 09:41 AM, Peter Lieven wrote:
>> Signed-off-by: Peter Lieven <p...@kamp.de>
>> ---
>> block/qcow2.c| 7 +++
>> qapi/block-core.json | 6 +-
>> 2 files changed, 12 insertions(+
Am 25.07.2017 um 23:55 schrieb Eric Blake:
> On 07/25/2017 09:41 AM, Peter Lieven wrote:
>> Signed-off-by: Peter Lieven <p...@kamp.de>
>> ---
>> block/qcow2.c| 7 +++
>> qapi/block-core.json | 6 +-
>> 2 files changed, 12 insertions(+
Am 25.07.2017 um 17:03 schrieb Eric Blake:
> On 07/25/2017 09:41 AM, Peter Lieven wrote:
>> Signed-off-by: Peter Lieven <p...@kamp.de>
>> ---
>> docs/interop/qcow2.txt | 51
>> +-
>> roms/ipxe |
Signed-off-by: Peter Lieven <p...@kamp.de>
---
qemu-img.texi | 26 ++
1 file changed, 26 insertions(+)
diff --git a/qemu-img.texi b/qemu-img.texi
index 72dabd6..3612c59 100644
--- a/qemu-img.texi
+++ b/qemu-img.texi
@@ -676,6 +676,32 @@ file which is COW and ha
we now read the extension on open and write it on update, but
do not yet use it.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 92 +++
block/qcow2.h | 21 ++
2 files changed, 108 insertions(+), 5 del
we now pass the parameters to the zlib compressor if the
extension is present and use the old default values if
the extension is absent.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2-cluster.c | 58 ++-
block/qcow2.c
if we specify exactly one iov of s->cluster_size bytes we can avoid
the bounce buffer.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index ffe609d..a12b3
this adds parsing and validation for the compress create
options. They are only validated but not yet used.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 86 +--
include/block/block_int.h | 39 +++--
2
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c| 7 +++
qapi/block-core.json | 6 +-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 0e9c2b8..7e03877 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -3968,6 +3
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2-cluster.c | 15 +++
block/qcow2.c | 25 -
configure | 2 +-
docs/interop/qcow2.txt | 2 ++
qapi/block-core.json | 15 ---
qemu-img.texi | 1 +
6
Signed-off-by: Peter Lieven <p...@kamp.de>
---
qapi/block-core.json | 40
1 file changed, 40 insertions(+)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 833c602..f652206 100644
--- a/qapi/block-core.json
+++ b/qapi/block-cor
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 7fd52e1..ffe609d 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -3031,7 +3031,7 @@ static int qcow2_create
Signed-off-by: Peter Lieven <p...@kamp.de>
---
docs/interop/qcow2.txt | 51 +-
roms/ipxe | 2 +-
2 files changed, 51 insertions(+), 2 deletions(-)
diff --git a/docs/interop/qcow2.txt b/docs/interop/qcow2.txt
index d7fdb1f..d
header extensions
- added missing lzo_init and fixed compress overhead for lzo
Peter Lieven (10):
specs/qcow2: add compress format extension
qapi/block-core: add Qcow2Compress parameters
block/qcow2: parse compress create options
qemu-img: add documentation for compress settings
Am 20.07.2017 um 21:19 schrieb Eric Blake:
> On 07/20/2017 11:30 AM, Peter Lieven wrote:
>
>>> The new code is now unconditionally initializing with -15 instead of
>>> -12. Does that matter, or does decompression work regardless of window
>>> size used at creation
Am 20.07.2017 um 20:31 schrieb Eric Blake:
> On 07/20/2017 11:26 AM, Peter Lieven wrote:
>>> I haven't yet checked your code implementation to see where you are
>>> setting window sizes, to know if window size is something that should be
>>> a tunable in the file
Am 20.07.2017 um 18:05 schrieb Eric Blake:
> On 07/20/2017 09:20 AM, Peter Lieven wrote:
>> Signed-off-by: Peter Lieven <p...@kamp.de>
>> ---
>> block/qcow2.c| 9 +
>> qapi/block-core.json | 6 +-
>> 2 files changed, 14 insertions(+)
Am 20.07.2017 um 18:03 schrieb Eric Blake:
> On 07/20/2017 09:20 AM, Peter Lieven wrote:
>> Signed-off-by: Peter Lieven <p...@kamp.de>
>> ---
>> block/qcow2-cluster.c | 15 +++
>> block/qcow2.c | 42 +++-
Am 20.07.2017 um 18:00 schrieb Eric Blake:
> On 07/20/2017 09:20 AM, Peter Lieven wrote:
>> we now pass the parameters to the zlib compressor if the
>> extension is present and use the old default values if
>> the extension is absent.
>>
>> Signed-o
Am 20.07.2017 um 17:52 schrieb Eric Blake:
> On 07/20/2017 09:20 AM, Peter Lieven wrote:
>> Signed-off-by: Peter Lieven <p...@kamp.de>
>> ---
>> docs/interop/qcow2.txt | 43 ++-
>> 1 file changed, 42 insertions(+), 1 dele
this adds parsing and validation for the compress create
options. They are only validated but not yet used.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 53 +--
include/block/block_int.h | 2 ++
2 files chang
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c| 9 +
qapi/block-core.json | 6 +-
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 0ba5977..59cf3b3 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2-cluster.c | 15 +++
block/qcow2.c | 42 +++---
configure | 2 +-
qapi/block-core.json | 14 --
qemu-img.texi | 1 +
5 files changed, 64 inse
Signed-off-by: Peter Lieven <p...@kamp.de>
---
docs/interop/qcow2.txt | 43 ++-
1 file changed, 42 insertions(+), 1 deletion(-)
diff --git a/docs/interop/qcow2.txt b/docs/interop/qcow2.txt
index d7fdb1f..ef5abb2 100644
--- a/docs/interop/qcow2.txt
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 1dff87e..67e48e1 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -2996,7 +2996,7 @@ static int qcow2_create
we now read the extension on open and write it on update, but
do not yet use it.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 94 +++
block/qcow2.h | 21 +
2 files changed, 105 insertions(+), 10 del
ing lzo_init and fixed compress overhead for lzo
Peter Lieven (10):
specs/qcow2: add compress format extension
qapi/block-core: add Qcow2Compress parameters
block/qcow2: parse compress create options
qemu-img: add documentation for compress settings
block/qcow2: read and write the com
if we specify exactly one iov of s->cluster_size bytes we can avoid
the bounce buffer.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 67e48e1..978e8
we now pass the parameters to the zlib compressor if the
extension is present and use the old default values if
the extension is absent.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2-cluster.c | 58 ++-
block/qcow2.c
Signed-off-by: Peter Lieven <p...@kamp.de>
---
qapi/block-core.json | 38 ++
1 file changed, 38 insertions(+)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index ff8e2ba..95e5393 100644
--- a/qapi/block-core.json
+++ b/qapi/block-cor
Signed-off-by: Peter Lieven <p...@kamp.de>
---
qemu-img.texi | 20
1 file changed, 20 insertions(+)
diff --git a/qemu-img.texi b/qemu-img.texi
index 72dabd6..fcc4c1d 100644
--- a/qemu-img.texi
+++ b/qemu-img.texi
@@ -676,6 +676,26 @@ file which is COW and has data
Am 14.07.2017 um 16:52 schrieb Eric Blake:
> On 07/14/2017 04:56 AM, Peter Lieven wrote:
>> Signed-off-by: Peter Lieven <p...@kamp.de>
>> ---
>> docs/interop/qcow2.txt | 35 ++-
>> 1 file changed, 34 insertions(+), 1 deletion(-
Signed-off-by: Peter Lieven <p...@kamp.de>
---
qemu-img.texi | 20
1 file changed, 20 insertions(+)
diff --git a/qemu-img.texi b/qemu-img.texi
index f11f603..79b0182 100644
--- a/qemu-img.texi
+++ b/qemu-img.texi
@@ -669,6 +669,26 @@ file which is COW and has data
if we specify exactly one iov of s->cluster_size bytes we can avoid
the bounce buffer.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 04b03de..ecb4b
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 1dd2a48..04b03de 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -2996,7 +2996,7 @@ static int qcow2_create
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2-cluster.c | 15 +++
block/qcow2.c | 42 +++---
configure | 2 +-
qapi/block-core.json | 14 --
qemu-img.texi | 1 +
5 files changed, 64 inse
Signed-off-by: Peter Lieven <p...@kamp.de>
---
qapi/block-core.json | 38 ++
1 file changed, 38 insertions(+)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index c437aa5..d6703a2 100644
--- a/qapi/block-core.json
+++ b/qapi/block-cor
we now pass the parameters to the zlib compressor if the
extension is present and use the old default values if
the extension is absent.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2-cluster.c | 58 ++-
block/qcow2.c
we now read the extension on open and write it on update, but
do not yet use it.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 94 +++
block/qcow2.h | 21 +
2 files changed, 105 insertions(+), 10 del
ved extra reservations for header extensions
- added missing lzo_init and fixed compress overhead for lzo
Peter Lieven (9):
specs/qcow2: add compress format extension
qapi/block-core: add Qcow2Compress parameters
block/qcow2: parse compress create options
qemu-img: add documentation for compress
this adds parsing and validation for the compress create
options. They are only validated but not yet used.
Signed-off-by: Peter Lieven <p...@kamp.de>
---
block/qcow2.c | 53 +--
include/block/block_int.h | 2 ++
2 files chang
Signed-off-by: Peter Lieven <p...@kamp.de>
---
docs/interop/qcow2.txt | 35 ++-
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git a/docs/interop/qcow2.txt b/docs/interop/qcow2.txt
index d7fdb1f..c2d3dab 100644
--- a/docs/interop/qcow2.txt
+++
Am 13.07.2017 um 17:06 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 05:02:51PM +0200, Peter Lieven wrote:
Am 13.07.2017 um 17:01 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 05:00:39PM +0200, Peter Lieven wrote:
Am 13.07.2017 um 16:58 schrieb Daniel P. Berrange:
On Thu, Jul 13
Am 13.07.2017 um 17:01 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 05:00:39PM +0200, Peter Lieven wrote:
Am 13.07.2017 um 16:58 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 04:18:13PM +0200, Peter Lieven wrote:
Okay, so it has to be a mix of QAPI parsing and manual parameter
Am 13.07.2017 um 16:58 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 04:18:13PM +0200, Peter Lieven wrote:
Okay, so it has to be a mix of QAPI parsing and manual parameter checking,
right?
Yeah. It does feel like a valid RFE for QAPI to add a permitted range to
'int' types though, which
Am 13.07.2017 um 17:17 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 05:13:23PM +0200, Peter Lieven wrote:
Am 13.07.2017 um 17:06 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 05:02:51PM +0200, Peter Lieven wrote:
Am 13.07.2017 um 17:01 schrieb Daniel P. Berrange:
On Thu, Jul 13
Am 13.07.2017 um 16:07 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 04:03:47PM +0200, Peter Lieven wrote:
Am 13.07.2017 um 16:00 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 03:49:09PM +0200, Peter Lieven wrote:
Am 13.07.2017 um 11:21 schrieb Daniel P. Berrange:
On Thu, Jul 13
Am 13.07.2017 um 16:00 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 03:49:09PM +0200, Peter Lieven wrote:
Am 13.07.2017 um 11:21 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 10:44:53AM +0200, Peter Lieven wrote:
Am 10.07.2017 um 15:55 schrieb Daniel P. Berrange:
On Mon, Jul 10
Am 13.07.2017 um 11:21 schrieb Daniel P. Berrange:
On Thu, Jul 13, 2017 at 10:44:53AM +0200, Peter Lieven wrote:
Am 10.07.2017 um 15:55 schrieb Daniel P. Berrange:
On Mon, Jul 10, 2017 at 03:52:18PM +0200, Kevin Wolf wrote:
Am 10.07.2017 um 15:44 hat Daniel P. Berrange geschrieben:
On Mon
Am 10.07.2017 um 15:30 schrieb Kevin Wolf:
Am 10.07.2017 um 15:24 hat Peter Lieven geschrieben:
Am 10.07.2017 um 15:10 schrieb Kevin Wolf:
Am 29.06.2017 um 12:57 hat Peter Lieven geschrieben:
Signed-off-by: Peter Lieven <p...@kamp.de>
---
qapi/block-core.jso
Am 10.07.2017 um 15:55 schrieb Daniel P. Berrange:
On Mon, Jul 10, 2017 at 03:52:18PM +0200, Kevin Wolf wrote:
Am 10.07.2017 um 15:44 hat Daniel P. Berrange geschrieben:
On Mon, Jul 10, 2017 at 03:34:59PM +0200, Kevin Wolf wrote:
Am 10.07.2017 um 15:29 hat Peter Lieven geschrieben:
Am
Am 10.07.2017 um 15:44 schrieb Daniel P. Berrange:
On Mon, Jul 10, 2017 at 03:34:59PM +0200, Kevin Wolf wrote:
Am 10.07.2017 um 15:29 hat Peter Lieven geschrieben:
Am 10.07.2017 um 15:25 schrieb Kevin Wolf:
Am 29.06.2017 um 12:57 hat Peter Lieven geschrieben:
we now read the extension
201 - 300 of 2519 matches
Mail list logo
