On 2016-09-15 at 18:34, Denis V. Lunev wrote:
They should work very similar, covering same areas if backing store is
shorter than the image. This change is necessary for the followup patch
switching to bdrv_get_block_status_above() in mirror to avoid assert
in check_block.
This change should be
On 19.09.2016 23:21, John Snow wrote:
>
>
> On 09/19/2016 04:58 PM, Max Reitz wrote:
>> On 19.09.2016 18:44, John Snow wrote:
>>> Final re-send for wording.
>>>
>>> The move to blk_flush altered the behavior of migration and flushing
>>> nodes that are not reachable via the guest, but are still
On 09/19/2016 04:58 PM, Max Reitz wrote:
On 19.09.2016 18:44, John Snow wrote:
Final re-send for wording.
The move to blk_flush altered the behavior of migration and flushing
nodes that are not reachable via the guest, but are still reachable
via QEMU and may or may not need to be flushed.
On 19.09.2016 13:39, Peter Maydell wrote:
> On 17 September 2016 at 23:05, Max Reitz wrote:
>> The following changes since commit e3571ae30cd26d19efd4554c25e32ef64d6a36b3:
>>
>> Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20160916' into
>> staging (2016-09-16
On 19.09.2016 18:44, John Snow wrote:
> Final re-send for wording.
>
> The move to blk_flush altered the behavior of migration and flushing
> nodes that are not reachable via the guest, but are still reachable
> via QEMU and may or may not need to be flushed.
>
> This is likely the simplest
On 09/18/2016 11:37 PM, Denis V. Lunev wrote:
> On 09/19/2016 04:21 AM, Fam Zheng wrote:
>> On Thu, 09/15 19:34, Denis V. Lunev wrote:
>>> They should work very similar, covering same areas if backing store is
>>> shorter than the image. This change is necessary for the followup patch
>>>
On 09/17/2016 11:25 PM, Fam Zheng wrote:
> sscanf is relatively loose (tolerate) on some invalid formats that we
> should fail instead of generating a wrong uuid structure, like with
> whitespaces and short strings.
>
> Add and use a helper function to first check the format.
>
> Signed-off-by:
On 09/19/2016 12:35 PM, Daniel P. Berrange wrote:
> The 'check' program records timings for each test that
> is run. These timings are only valid, however, for a
> particular format/protocol combination. So if frequently
> running 'check' with a variety of different formats or
> protocols, the
On 09/19/2016 11:54 AM, Kevin Wolf wrote:
> In order to remove the necessity to use BlockBackend names in the
> external API, we want to allow qdev device names in all device related
> commands.
>
> This converts blockdev-change-medium to accept a qdev device name.
>
> Signed-off-by: Kevin Wolf
On 09/19/2016 11:54 AM, Kevin Wolf wrote:
> In order to remove the necessity to use BlockBackend names in the
> external API, we want to allow qdev device names in all device related
> commands.
>
> This converts eject to accept a qdev device name.
>
> Signed-off-by: Kevin Wolf
On 09/19/2016 11:54 AM, Kevin Wolf wrote:
> We just added the option to use qdev device names in all device related
> block QMP commands. This patch converts some of the test cases in 118 to
> use qdev device names instead of BlockBackend names to cover the new
> way. It converts cases for each of
On 09/19/2016 11:54 AM, Kevin Wolf wrote:
> In order to remove the necessity to use BlockBackend names in the
> external API, we want to allow qdev device names in all device related
> commands.
>
> This converts x-blockdev-remove-medium to accept a qdev device name.
>
> As the command is
On 09/19/2016 11:54 AM, Kevin Wolf wrote:
> In order to remove the necessity to use BlockBackend names in the
> external API, we want to allow qdev device names in all device related
> commands.
>
> This converts block_set_io_throttle to accept a qdev device name.
>
> Signed-off-by: Kevin Wolf
On 09/19/2016 11:54 AM, Kevin Wolf wrote:
> In order to remove the necessity to use BlockBackend names in the
> external API, we want to allow qdev device names in all device related
> commands.
>
> This converts blockdev-open/close-tray to accept a qdev device name.
>
> Signed-off-by: Kevin
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [PATCH v2 00/10] block: Accept qdev IDs in device level
QMP commands
Message-id:
On 09/19/2016 02:15 PM,
no-re...@ec2-52-6-146-230.compute-1.amazonaws.com wrote:
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
lies and slander!
Subject:
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [PATCH v4 0/2] block: allow flush on devices with open
tray
Message-id:
On 09/16/2016 11:22 AM, Kevin Wolf wrote:
> Am 16.09.2016 um 10:15 hat Denis V. Lunev geschrieben:
>> On 09/16/2016 11:08 AM, Kevin Wolf wrote:
>>> Am 15.09.2016 um 18:39 hat Denis V. Lunev geschrieben:
On 09/15/2016 07:09 PM, Kevin Wolf wrote:
> Am 15.09.2016 um 15:19 hat Denis V. Lunev
On some distros, whenever you close a block device file
descriptor there is a udev rule that resets the file
permissions. This can race with the test script when
we run qemu-io multiple times against the same block
device. Occassionally the second qemu-io invokation
will find udev has reset the
The tests 033, 120, 140, 145 and 157 were all broken
when run with LUKS, since they did not correctly use
the required image opts args syntax to specify the
decryption secret.
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/033 | 16
The 'check' program records timings for each test that
is run. These timings are only valid, however, for a
particular format/protocol combination. So if frequently
running 'check' with a variety of different formats or
protocols, the times printed can be very misleading.
Record the
The main goal of this series is to get the I/O tests passing
100% with LUKS when run with './check -luks'.
In testing this I noticed that test timings are cached
across runs with different block backends which is very
misleading.
It adds a few more combinations to the LUKS/dmcrypt
In order to remove the necessity to use BlockBackend names in the
external API, we want to allow qdev device names in all device related
commands.
This converts blockdev-open/close-tray to accept a qdev device name.
Signed-off-by: Kevin Wolf
---
blockdev.c | 61
By default the PBKDF algorithm used with LUKS is tuned
based on the number of iterations to produce 1 second
of running time. This makes running the I/O test with
the LUKS format orders of magnitude slower than with
qcow2/raw formats.
When creating LUKS images, set the iteration time to
a 10ms to
When run on a loaded host, QEMU may print
main-loop: WARNING: I/O thread spun for 10 iterations
so we must take care to filter that message.
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/140 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Add tests for sha224, sha512, sha384 and ripemd160 hash
algorithms.
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/149 | 10 +-
tests/qemu-iotests/149.out | 482 -
2 files changed, 484 insertions(+), 8 deletions(-)
This finds a BlockBackend given the device model that is attached to it.
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
---
block/block-backend.c | 19 +++
include/sysemu/block-backend.h | 1 +
2 files changed, 20 insertions(+)
In order to remove the necessity to use BlockBackend names in the external API,
we already converted all block layer QMP commands on the node level to accept
node names instead of BlockBackend names. This series converts the second part,
device level commands, to allow qdev device names instead of
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
---
qdev-monitor.c | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/qdev-monitor.c b/qdev-monitor.c
index e19617f..bc0213f 100644
--- a/qdev-monitor.c
+++ b/qdev-monitor.c
In order to remove the necessity to use BlockBackend names in the
external API, we want to allow qdev device names in all device related
commands.
This converts x-blockdev-insert-medium to accept a qdev device name.
As the command is experimental, we can still remove the 'device' option
that
In order to remove the necessity to use BlockBackend names in the
external API, we want to allow qdev device names in all device related
commands.
This converts x-blockdev-remove-medium to accept a qdev device name.
As the command is experimental, we can still remove the 'device' option
that
This finds the BlockBackend attached to the device model identified by
its qdev ID.
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
---
include/sysemu/block-backend.h | 1 +
qdev-monitor.c | 18 ++
2 files changed, 19
In order to remove the necessity to use BlockBackend names in the
external API, we want to allow qdev device names in all device related
commands.
This converts blockdev-change-medium to accept a qdev device name.
Signed-off-by: Kevin Wolf
---
blockdev.c | 18
We just added the option to use qdev device names in all device related
block QMP commands. This patch converts some of the test cases in 118 to
use qdev device names instead of BlockBackend names to cover the new
way. It converts cases for each of the media change commands, but only
for CD-ROM
In order to remove the necessity to use BlockBackend names in the
external API, we want to allow qdev device names in all device related
commands.
This converts block_set_io_throttle to accept a qdev device name.
Signed-off-by: Kevin Wolf
---
blockdev.c | 12
In order to remove the necessity to use BlockBackend names in the
external API, we want to allow qdev device names in all device related
commands.
This converts eject to accept a qdev device name.
Signed-off-by: Kevin Wolf
---
blockdev.c | 10 +++---
hmp.c
Commit fe1a9cbc moved the flush_all routine from the bdrv layer to the
block-backend layer. In doing so, however, the semantics of the routine
changed slightly such that flush_all now used blk_flush instead of
bdrv_flush.
blk_flush can fail if the attached device model reports that it is not
Final re-send for wording.
The move to blk_flush altered the behavior of migration and flushing
nodes that are not reachable via the guest, but are still reachable
via QEMU and may or may not need to be flushed.
This is likely the simplest solution for now until we nail down our
policy a bit
On Wed, Sep 14, 2016 at 07:03:37AM -0400, Yaowei Bai wrote:
> This patchset change to check epoll's enablement first before nodes
> iteration to improve aio_poll()'s performance.
>
> Also fix a wrong comment of mirror_start().
>
> Yaowei Bai (2):
> block: mirror: fix wrong comment of
Am 15.09.2016 um 17:51 hat Eric Blake geschrieben:
> On 09/15/2016 03:35 AM, Kevin Wolf wrote:
>
> >>>
> >>> -- "device": block device name (json-string)
> >>> +- "device": block device name (deprecated, use @id instead)
> >>> +(json-string, optional)
> >>> +- "id": the name or QOM
On 17 September 2016 at 23:05, Max Reitz wrote:
> The following changes since commit e3571ae30cd26d19efd4554c25e32ef64d6a36b3:
>
> Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20160916' into
> staging (2016-09-16 16:54:50 +0100)
>
> are available in the git
Am 16.09.2016 um 18:17 hat John Snow geschrieben:
>
>
> On 09/15/2016 07:42 PM, John Snow wrote:
> >Bypass the usual check to see if we are "allowed" to flush via the
> >block model, and manually flush the BDS nodes themselves instead.
> >
> >This allows us to do things like migrate when we have
42 matches
Mail list logo