[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-block] [Qemu-devel] [PATCH 0/2] qemu-img: Let "info" warn and

From: Daniel P. Berrange
Subject: Re: [Qemu-block] [Qemu-devel] [PATCH 0/2] qemu-img: Let "info" warn and go ahead without -U
Date: Wed, 10 Jan 2018 12:49:13 +0000
User-agent: Mutt/1.9.1 (2017-09-22)

On Mon, Jan 08, 2018 at 03:41:36PM +0100, Kevin Wolf wrote:
> Am 05.01.2018 um 07:55 hat Fam Zheng geschrieben:
> > Management and users are accustomed to "qemu-img info" to query status of
> > images even when they are used by guests. Since image locking was added, 
> > the -U
> > (--force-share) option is needed for that to work. The reason has been that 
> > due
> > to possible race with image header update, the output can be misleading.
> > 
> > But what are likely to happen after we emit the error are that, for 
> > interactive
> > users, '-U' will be used and the command retried; for management (nova, RHV,
> > etc.), the operation is broken with no knob to workaround this.
> > 
> > This series changes that error to a warning so that it doesn't get in the 
> > way.
> Are management tools actually doing this? There is no good reason to
> call 'qemu-img info' for an image that is in use by a VM.

OpenStack will frequently call 'qemu-img info' for disks that are in use by
VMs. It is looking at the sizes to understand the relation between the current
size used by qcow2 vs the possible future usage. In this context, it does not
matter if the data is slightly outdated, as it will catch up next time it reads
it a few mins later.

It has been patched to just retry with -U to avoid this error on new

> If no, NACK. Automatically disabling locking because it can be
> inconvenient defeats the purpose of locking.

|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

reply via email to

[Prev in Thread] Current Thread [Next in Thread]