Re: Failing QEMU iotests

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

On Wed, Nov 17, 2021 at 01:50:12PM +0100, Thomas Huth wrote:
> On 17/11/2021 11.59, Hanna Reitz wrote:
> > On 17.11.21 11:07, Thomas Huth wrote:
> > > 
> > >  Hi!
> > > 
> > > I think it has been working fine for me a couple of weeks ago,
> > > but when I now run:
> > > 
> > >  make check SPEED=slow
> > > 
> > > I'm getting a couple of failing iotests... not sure whether
> > > these are known issues already, so I thought I'd summarize them
> > > here:
> ...
> > > --- /home/thuth/devel/qemu/tests/qemu-iotests/206.out
> > > +++ 206.out.bad
> > > @@ -99,55 +99,19 @@
> > > 
> > >  {"execute": "blockdev-create", "arguments": {"job-id": "job0",
> > > "options": {"driver": "qcow2", "encrypt": {"cipher-alg":
> > > "twofish-128", "cipher-mode": "ctr", "format": "luks", "hash-alg":
> > > "sha1", "iter-time": 10, "ivgen-alg": "plain64", "ivgen-hash-alg":
> > > "md5", "key-secret": "keysec0"}, "file": {"driver": "file",
> > > "filename": "TEST_DIR/PID-t.qcow2"}, "size": 33554432}}}
> > >  {"return": {}}
> > > +Job failed: Unsupported cipher algorithm twofish-128 with ctr mode
> > >  {"execute": "job-dismiss", "arguments": {"id": "job0"}}
> > >  {"return": {}}
> > > 
> > >  image: TEST_IMG
> > >  file format: IMGFMT
> > >  virtual size: 32 MiB (33554432 bytes)
> > > -encrypted: yes
> > >  cluster_size: 65536
> > >  Format specific information:
> > >      compat: 1.1
> > >      compression type: zlib
> > >      lazy refcounts: false
> > >      refcount bits: 16
> > > -    encrypt:
> > > -        ivgen alg: plain64
> > > -        hash alg: sha1
> > > -        cipher alg: twofish-128
> > > -        uuid: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
> > > -        format: luks
> > > -        cipher mode: ctr
> > > -        slots:
> > > -            [0]:
> > > -                active: true
> > > -                iters: XXX
> > > -                key offset: 4096
> > > -                stripes: 4000
> > > -            [1]:
> > > -                active: false
> > > -                key offset: 69632
> > > -            [2]:
> > > -                active: false
> > > -                key offset: 135168
> > > -            [3]:
> > > -                active: false
> > > -                key offset: 200704
> > > -            [4]:
> > > -                active: false
> > > -                key offset: 266240
> > > -            [5]:
> > > -                active: false
> > > -                key offset: 331776
> > > -            [6]:
> > > -                active: false
> > > -                key offset: 397312
> > > -            [7]:
> > > -                active: false
> > > -                key offset: 462848
> > > -        payload offset: 528384
> > > -        master key iters: XXX
> > >      corrupt: false
> > >      extended l2: false
> > 
> > I doubt this worked a couple of weeks ago, but it’s definitely one that
> > we should just get around to fixing. :/
> 
> Hm, maybe I've did the successful run on a different system last time ... I
> even slightly remember now having seen this before in the past on my current
> system, so yes, likely not something new.

Triggered by me switching QEMU to prefer GNUTLS for crypto by default
in 6.1, as it doesn't bother to support obscure crypto algs that no
one uses in practice for LUKS.


Regards,
Daniel
-- 
|: 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 :|