The crash is reproducible with the current version:

wesley@jv0:~$ apt policy qemu-system-x86
qemu-system-x86:
  Installed: 1:6.2+dfsg-2ubuntu6.28
  Candidate: 1:6.2+dfsg-2ubuntu6.28
  Version table:
 *** 1:6.2+dfsg-2ubuntu6.28 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:6.2+dfsg-2ubuntu6 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

### Verification done Jammy ###

wesley@jv0:~$ apt policy qemu-system-x86
qemu-system-x86:
  Installed: 1:6.2+dfsg-2ubuntu6.29
  Candidate: 1:6.2+dfsg-2ubuntu6.29
  Version table:
 *** 1:6.2+dfsg-2ubuntu6.29 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1:6.2+dfsg-2ubuntu6.28 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     1:6.2+dfsg-2ubuntu6 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

wesley@jv0:~$ ./provision.sh
+ wget 
https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.img
--2026-03-26 08:56:52--  
https://cloud-images.ubuntu.com/daily/server/noble/current/noble-server-cloudimg-amd64.img
Resolving cloud-images.ubuntu.com (cloud-images.ubuntu.com)... 185.125.190.37, 
185.125.190.40, 2620:2d:4000:1::1a, ...
Connecting to cloud-images.ubuntu.com 
(cloud-images.ubuntu.com)|185.125.190.37|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 629987328 (601M) [application/octet-stream]
Saving to: ‘noble-server-cloudimg-amd64.img.1’

noble-server-cloudimg-amd64.img.1
100%[=========================================================================>]
600.80M  22.0MB/s    in 42s

2026-03-26 08:57:35 (14.2 MB/s) - ‘noble-server-cloudimg-amd64.img.1’
saved [629987328/629987328]

+ sudo cp noble-server-cloudimg-amd64.img /var/lib/libvirt/images/n0-root.qcow2
+ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/n0-blk0.qcow2 10G
Formatting '/var/lib/libvirt/images/n0-blk0.qcow2', fmt=qcow2 
cluster_size=65536 extended_l2=off compression_type=zlib size=10737418240 
lazy_refcounts=off refcount_bits=16
+ touch network-config
+ touch meta-data
+ touch user-data
+ virt-install -n n0 --description 'Test noble minimal' 
--os-variant=ubuntu24.04 --ram=1024 --vcpus=2 --import --disk 
path=/var/lib/libvirt/images/n0-root.qcow2,bus=virtio,cache=writethrough,size=10
 --disk 
path=/var/lib/libvirt/images/n0-blk0.qcow2,bus=virtio,cache=writethrough,size=10
 --graphics none --network network=default --cloud-init 
user-data=user-data,meta-data=meta-data,network-config=network-config
...

wesley@jv0:~$ virsh list
 Id   Name   State
----------------------
 2    n0     running

wesley@jv0:~$ ./blockrebase-crash.sh n0
...

My connection to the testbed died about 5 hours in to the test; it
filled up 8GB with snapshots and didn't crash:

wesley@jv0:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        20G  9.0G   11G  47% /

wesley@jv0:~$ virsh list
 Id   Name   State
----------------------
 2    n0     running

### Verification done Jammy ###

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2126951

Title:
  `block-stream` segfault with concurrent `query-named-block-nodes`

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/2126951/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to