[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [PATCH for-2.10 v3] block: Skip implicit nodes in query
Re: [Qemu-block] [PATCH for-2.10 v3] block: Skip implicit nodes in query-block/blockstats
Thu, 20 Jul 2017 10:37:50 -0500
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
On 07/20/2017 08:11 AM, Kevin Wolf wrote:
> Commits 0db832f and 6cdbceb introduced the automatic insertion of filter
> nodes above the top layer of mirror and commit block jobs. The
> assumption made there was that since libvirt doesn't do node-level
> management of the block layer yet, it shouldn't be affected by added
> This is true as far as commands issued by libvirt are concerned. It only
> uses BlockBackend names to address nodes, so any operations it performs
> still operate on the root of the tree as intended.
> However, the assumption breaks down when you consider query commands,
> which return data for the wrong node now. These commands also return
> information on some child nodes (bs->file and/or bs->backing), which
> libvirt does make use of, and which refer to the wrong nodes, too.
> One of the consequences is that oVirt gets wrong information about the
> image size and stops the VM in response as long as a mirror or commit
> job is running:
> This patch fixes the problem by hiding the implicit nodes created
> automatically by the mirror and commit block jobs in the output of
> query-block and BlockBackend-based query-blockstats as long as the user
> doesn't indicate that they are aware of those nodes by providing a node
> name for them in the QMP command to start the block job.
> The node-based commands query-named-block-nodes and query-blockstats
> with query-nodes=true still show all nodes, including implicit ones.
> This ensures that users that are capable of node-level management can
> still access the full information; users that only know BlockBackends
> won't use these commands.
> Cc: address@hidden
> Signed-off-by: Kevin Wolf <address@hidden>
I ran libvirt against qemu with this patch applied, and tested that I
was able to use the block threshold events through libvirt both on a
domain with no jobs, and then again after I created a mirror job after
setting the threshold (for some reason, libvirt didn't like me setting a
threshold after starting the mirror - but that's a pre-existing
limitation in libvirt). At any rate, the thresholds behaved the way I
expected, so it looks like libvirt is okay with the change in output.
That, plus your testsuite additions (qemu-iotests passed for me), means
you can add:
Tested-by: Eric Blake <address@hidden>
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
Description: OpenPGP digital signature