Hi together, since my last dist upgrade from the community repo any guestmount command results in
The updates that were made:
After reverting the updates, everything works as expected.
I'm not sure if i'm alone with this issue and since my system is not security relevant, its no problem to hold back this updates, but maybe this indicates a serious issue, so i wanted to report it.
Alex
libguestfs: error: /usr/bin/qemu-system-x86_64 killed by signal 11 (Segmentation fault). The updates that were made:
Code:
Start-Date: 2021-11-13 17:16:18
Commandline: apt-get dist-upgrade -y
Install:
libzpool5linux:amd64 (2.1.1-pve3, automatic),
pve-kernel-5.11.22-7-pve:amd64 (5.11.22-12, automatic)
Upgrade:
corosync:amd64 (3.1.5-pve1, 3.1.5-pve2),
pve-firmware:amd64 (3.3-2, 3.3-3),
zfs-zed:amd64 (2.0.5-pve1, 2.1.1-pve3),
libldb2:amd64 (2:2.2.0-3.1, 2:2.2.3-2~deb11u1),
zfs-initramfs:amd64 (2.0.5-pve1, 2.1.1-pve3),
spl:amd64 (2.0.5-pve1, 2.1.1-pve3),
pve-qemu-kvm:amd64 (6.0.0-4, 6.1.0-1),
libnvpair3linux:amd64 (2.0.5-pve1, 2.1.1-pve3),
libuutil3linux:amd64 (2.0.5-pve1, 2.1.1-pve3),
libpve-storage-perl:amd64 (7.0-12, 7.0-13),
libwbclient0:amd64 (2:4.13.5+dfsg-2, 2:4.13.13+dfsg-1~deb11u2),
libvotequorum8:amd64 (3.1.5-pve1, 3.1.5-pve2),
libquorum5:amd64 (3.1.5-pve1, 3.1.5-pve2),
libsmbclient:amd64 (2:4.13.5+dfsg-2, 2:4.13.13+dfsg-1~deb11u2),
libcmap4:amd64 (3.1.5-pve1, 3.1.5-pve2),
proxmox-backup-file-restore:amd64 (2.0.11-1, 2.0.13-1),
libcfg7:amd64 (3.1.5-pve1, 3.1.5-pve2),
qemu-server:amd64 (7.0-16, 7.0-18),
libpve-access-control:amd64 (7.0-5, 7.0-6),
libcpg4:amd64 (3.1.5-pve1, 3.1.5-pve2),
proxmox-backup-client:amd64 (2.0.11-1, 2.0.13-1),
python3-ldb:amd64 (2:2.2.0-3.1, 2:2.2.3-2~deb11u1),
smbclient:amd64 (2:4.13.5+dfsg-2, 2:4.13.13+dfsg-1~deb11u2),
pve-manager:amd64 (7.0-13, 7.0-14+1),
libpve-common-perl:amd64 (7.0-10, 7.0-12),
samba-libs:amd64 (2:4.13.5+dfsg-2, 2:4.13.13+dfsg-1~deb11u2),
pve-kernel-5.11:amd64 (7.0-8, 7.0-10),
libzfs4linux:amd64 (2.0.5-pve1, 2.1.1-pve3),
samba-common:amd64 (2:4.13.5+dfsg-2, 2:4.13.13+dfsg-1~deb11u2),
pve-firewall:amd64 (4.2-4, 4.2-5),
libcorosync-common4:amd64 (3.1.5-pve1, 3.1.5-pve2),
libnozzle1:amd64 (1.22-pve1, 1.22-pve2),
libknet1:amd64 (1.22-pve1, 1.22-pve2),
pve-kernel-helper:amd64 (7.1-2, 7.1-4),
zfsutils-linux:amd64 (2.0.5-pve1, 2.1.1-pve3)
End-Date: 2021-11-13 17:17:56
Code:
guestmount -a debian-11-generic-amd64_game02.qcow2 -i /root/osinit/tempmount
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: create: flags = 0, handle = 0x55ea772a3930, program = guestmount
libguestfs: trace: set_recovery_proc false
libguestfs: trace: set_recovery_proc = 0
libguestfs: trace: add_drive "debian-11-generic-amd64_game02.qcow2"
libguestfs: trace: add_drive = 0
libguestfs: trace: launch
libguestfs: trace: max_disks
libguestfs: trace: max_disks = 255
libguestfs: trace: get_tmpdir
libguestfs: trace: get_tmpdir = "/tmp"
libguestfs: trace: version
libguestfs: trace: version = <struct guestfs_version = major: 1, minor: 44, release: 0, extra: , >
libguestfs: trace: get_backend
libguestfs: trace: get_backend = "direct"
libguestfs: launch: program=guestmount
libguestfs: launch: version=1.44.0
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=/tmp/libguestfse9Fihv
libguestfs: launch: umask=0022
libguestfs: launch: euid=0
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
libguestfs: begin building supermin appliance
libguestfs: run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/.guestfs-0/lock
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/x86_64-linux-gnu/guestfs/supermin.d
libguestfs: command: run: \ -o /var/tmp/.guestfs-0/appliance.d
supermin: version: 5.2.1
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/.guestfs-0/lock
supermin: if-newer: output does not need rebuilding
libguestfs: finished building supermin appliance
libguestfs: begin testing qemu features
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
libguestfs: checking for previously cached test results of /usr/bin/qemu-system-x86_64, in /var/tmp/.guestfs-0
libguestfs: command: run: /usr/bin/qemu-system-x86_64
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -help
libguestfs: command: run: /usr/bin/qemu-system-x86_64
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -machine accel=kvm:tcg
libguestfs: command: run: \ -device ?
libguestfs: error: /usr/bin/qemu-system-x86_64 killed by signal 11 (Segmentation fault), see debug messages above
libguestfs: trace: launch = -1 (error)
libguestfs: trace: close
libguestfs: closing guestfs handle 0x55ea772a3930 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfse9Fihv
Code:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
XDG_RUNTIME_DIR=/run/user/0
SELinux: sh: 1: getenforce: not found
guestfs_get_append: (null)
guestfs_get_autosync: 1
guestfs_get_backend: direct
guestfs_get_backend_settings: []
guestfs_get_cachedir: /var/tmp
guestfs_get_hv: /usr/bin/qemu-system-x86_64
guestfs_get_memsize: 1280
guestfs_get_network: 0
guestfs_get_path: /usr/lib/x86_64-linux-gnu/guestfs
guestfs_get_pgroup: 0
guestfs_get_program: libguestfs-test-tool
guestfs_get_recovery_proc: 1
guestfs_get_smp: 1
guestfs_get_sockdir: /tmp
guestfs_get_tmpdir: /tmp
guestfs_get_trace: 0
guestfs_get_verbose: 1
host_cpu: x86_64
Launching appliance, timeout set to 600 seconds.
libguestfs: launch: program=libguestfs-test-tool
libguestfs: launch: version=1.44.0
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=/tmp/libguestfskD9lhw
libguestfs: launch: umask=0022
libguestfs: launch: euid=0
libguestfs: begin building supermin appliance
libguestfs: run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/.guestfs-0/lock
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/x86_64-linux-gnu/guestfs/supermin.d
libguestfs: command: run: \ -o /var/tmp/.guestfs-0/appliance.d
supermin: version: 5.2.1
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/.guestfs-0/lock
supermin: if-newer: output does not need rebuilding
libguestfs: finished building supermin appliance
libguestfs: begin testing qemu features
libguestfs: checking for previously cached test results of /usr/bin/qemu-system-x86_64, in /var/tmp/.guestfs-0
libguestfs: command: run: /usr/bin/qemu-system-x86_64
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -help
libguestfs: command: run: /usr/bin/qemu-system-x86_64
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -machine accel=kvm:tcg
libguestfs: command: run: \ -device ?
libguestfs: error: /usr/bin/qemu-system-x86_64 killed by signal 11 (Segmentation fault), see debug messages above
libguestfs: closing guestfs handle 0x562cb1092820 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfskD9lhwAfter reverting the updates, everything works as expected.
I'm not sure if i'm alone with this issue and since my system is not security relevant, its no problem to hold back this updates, but maybe this indicates a serious issue, so i wanted to report it.
Alex
