Merhaba: just upgraded one of the Linux servers running Arch Linux with the latest GCC toolchain and QEMU packages.
Now while running the following command :: qemu-system-x86_64 --version I encounter the following error qemu-system-x86_64: error while loading shared libraries: libvfio-user.so.0: cannot open shared object file: No such file or directory Taking a closer look at the dependencies :: ldd /usr/bin/qemu-system-x86_64 linux-vdso.so.1 (0x0000772a961a8000) libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x0000772a960da000) libcapstone.so.5 => /usr/lib/libcapstone.so.5 (0x0000772a94200000) libbpf.so.1 => /usr/lib/libbpf.so.1 (0x0000772a9499e000) libgnutls.so.30 => /usr/lib/libgnutls.so.30 (0x0000772a94006000) libpng16.so.16 => /usr/lib/libpng16.so.16 (0x0000772a94964000) libz.so.1 => /usr/lib/libz.so.1 (0x0000772a960bf000) libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x0000772a93f6a000) libsasl2.so.3 => /usr/lib/libsasl2.so.3 (0x0000772a94945000) libfdt.so.1 => /usr/lib/libfdt.so.1 (0x0000772a960b4000) libudev.so.1 => /usr/lib/libudev.so.1 (0x0000772a948ff000) libsnappy.so.1 => /usr/lib/libsnappy.so.1 (0x0000772a93f5e000) liblzo2.so.2 => /usr/lib/liblzo2.so.2 (0x0000772a93f3d000) libdaxctl.so.1 => /usr/lib/libdaxctl.so.1 (0x0000772a93f31000) libseccomp.so.2 => /usr/lib/libseccomp.so.2 (0x0000772a93f11000) libnuma.so.1 => /usr/lib/libnuma.so.1 (0x0000772a93f03000) libkeyutils.so.1 => /usr/lib/libkeyutils.so.1 (0x0000772a960ab000) libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x0000772a93d36000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x0000772a93cd7000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x0000772a93b89000) libzstd.so.1 => /usr/lib/libzstd.so.1 (0x0000772a93aaa000) libslirp.so.0 => /usr/lib/libslirp.so.0 (0x0000772a93a88000) libvdeplug.so.3 => /usr/lib/libvdeplug.so.3 (0x0000772a93a80000) libxdp.so.1 => /usr/lib/libxdp.so.1 (0x0000772a93a6a000) libdw.so.1 => /usr/lib/libdw.so.1 (0x0000772a939d9000) liburing.so.2 => /usr/lib/liburing.so.2 (0x0000772a939d2000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x0000772a939cb000) libm.so.6 => /usr/lib/libm.so.6 (0x0000772a938dc000) libpam.so.0 => /usr/lib/libpam.so.0 (0x0000772a938cb000) libfuse3.so.3 => /usr/lib/libfuse3.so.3 (0x0000772a9388b000) libaio.so.1 => /usr/lib/libaio.so.1 (0x0000772a93884000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x0000772a93856000) libc.so.6 => /usr/lib/libc.so.6 (0x0000772a93665000) /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x0000772a961aa000) libelf.so.1 => /usr/lib/libelf.so.1 (0x0000772a93649000) libp11-kit.so.0 => /usr/lib/libp11-kit.so.0 (0x0000772a934e6000) libidn2.so.0 => /usr/lib/libidn2.so.0 (0x0000772a934c4000) libunistring.so.5 => /usr/lib/libunistring.so.5 (0x0000772a93312000) libtasn1.so.6 => /usr/lib/libtasn1.so.6 (0x0000772a932fd000) I can't seem to find anything amiss or am I just too sleepy :( Anyone remembers which package has 'libvfio-user.so' ? Is this a cause of a partially successful upgrade ? warm regards Saifi.