Re: [Qemu-devel] nbd: Possible regression in 2.9 RCs

["Daniel P. Berrange" <berrange@redhat.com>]

On Tue, Apr 04, 2017 at 01:00:08PM +0200, Paolo Bonzini wrote:
> 
> 
> On 04/04/2017 10:17, ciprian.barbu wrote:
> >>
> >> but we do NOT make any guarantees of supporting
> >>
> >> new qemu, old libvirt
> > 
> > Sounds reasonable enough, I guess we didn't look at it this way.
> 
> Yes, but usually it's "new qemu, very old libvirt", like several years
> old.  I think this should be treated as a regression.
> 
> Between this issue and the problem with snapshots, it seems to me that
> the op blockers was really, really premature.

I think this kind of issue is inevitable when introducing this kind of
feature in to QEMU - no matter how well we think we've identified the
edge cases during development, this kind of issue would inevitably crop
up somewhere.

Even if we had libvirt support already, chances are we would have missed
handling of this edge case.

This feels like a case where the new feature needs to have a different
default - ie default to old behavior and require explicit opt-in to use
of the op-blockers. This allows people to opt-in to test the feature in
real-world & identify problems without risk of breaking the everyone else
out of the box.

Can we get this disabled by default to 2.9, with a view to having some
time for testing before enabling it by default in 2.10 / 2.11

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|