Recurring update issue: the qemu-base issue

Kernel: 6.5.7-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: hpet available: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4fdf9e35-eb8e-4181-93e8-eae07da02c42 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
amd_iommu=on ibt=off
Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Type: Laptop System: LENOVO product: 82KC v: Lenovo V14 G2 ALC
serial: <superuser required> Chassis: type: 10 v: Lenovo V14 G2 ALC
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <superuser required>
UEFI: LENOVO v: GLCN46WW date: 04/29/2022
ID-1: BAT0 charge: 37.8 Wh (97.7%) condition: 38.7/38.0 Wh (101.9%)
volts: 8.1 min: 7.7 model: LGC L20L2PF0 type: Li-poly serial: <filter>
status: not charging cycles: 65
Info: model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 2 gen: 3 level: v3 note: check built: 2020-22
process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x68 (104) stepping: 1
microcode: 0x8608103
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB
desc: 2x4 MiB
Speed (MHz): avg: 3150 high: 4045 min/max: 400/4056 scaling:
driver: amd-pstate-epp governor: performance cores: 1: 4043 2: 4043 3: 3347
4: 2859 5: 2980 6: 3335 7: 2434 8: 2268 9: 4045 10: 4042 11: 2257 12: 2148
bogomips: 50307
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5
code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s
lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1,eDP-1
empty: none bus-ID: 04:00.0 chip-ID: 1002:164c class-ID: 0300 temp: 45.0 C
Device-2: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:2 chip-ID: 5986:2137
class-ID: 0e02
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x2160 s-dpi: 96 s-size: 506x570mm (19.92x22.44")
s-diag: 762mm (30.01")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 pos: top model: Dell P2417H
serial: <filter> built: 2017 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: eDP-1 mapped: eDP pos: primary,bottom
model: AU Optronics 0x208d built: 2019 res: 1920x1080 hz: 60 dpi: 158
gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9
modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (renoir LLVM
16.0.6 DRM 3.54 6.5.7-zen2-1-zen) device-ID: 1002:164c memory: 1.95 GiB
unified: no
API: Vulkan v: 1.3.264 layers: 3 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RENOIR) driver: mesa radv v: 23.2.1-arch1.2
device-ID: 1002:164c surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 04:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x,
snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir,
snd_sof_amd_rembrandt pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max:
gen: 4 speed: 16 GT/s bus-ID: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.5.7-zen2-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.82 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8168 v: 8.052.01-NAPI modules: r8169 pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp1s0 state: down mac: <filter>
Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: Lenovo driver: rtw_8822ce v: N/A modules: rtw88_8822ce pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:c822
class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4:3 chip-ID: 0bda:c123
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: no pairing: no
Local Storage: total: 476.94 GiB used: 326.77 GiB (68.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lenovo
model: UMIS RPJTJ512MEE1OWX size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2.1C0628 temp: 48.9 C scheme: GPT
ID-1: / raw-size: 256.64 GiB size: 256.64 GiB (100.00%)
used: 174.07 GiB (67.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 256.64 GiB size: 256.64 GiB (100.00%)
used: 174.07 GiB (67.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 256.64 GiB size: 256.64 GiB (100.00%)
used: 174.07 GiB (67.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 256.64 GiB size: 256.64 GiB (100.00%)
used: 174.07 GiB (67.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 21.37 GiB used: 690.5 MiB (3.2%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12
dev: /dev/zram0
System Temperatures: cpu: 50.5 C mobo: N/A gpu: amdgpu temp: 42.0 C
Fan Speeds (rpm): N/A
Processes: 390 Uptime: 23m wakeups: 1 Memory: total: 24 GiB note: est.
available: 21.37 GiB used: 5.72 GiB (26.8%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 1532 libs: 417
tools: octopi,paru,yay pm: rpm pkgs: 0 Shell: fish v: 3.6.1
running-in: yakuake inxi: 3.3.30
Garuda (2.6.17-1):
System install date:     2023-06-28
Last full system update: 2023-10-18 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:


For a few months now, once every few updates I get the issue described in many different posts on the forum, see e.g., [1], [2], [3], and [4].

The issue is that garuda-update fails due to a missing qemu-base dependency. Here is the console output of running garuda-update, just to have the full context:

garuda downloading...
core downloading...
extra downloading...
multilib downloading...
chaotic-aur downloading...
:: Starting full system upgrade...
:: Replace libinput_gestures_qt with chaotic-aur/libinput-gestures-qt? [Y/n] y
warning: qemu-base: ignoring package upgrade (8.1.1-2 => 8.1.2-1)
warning: virt-manager-meta: local (5-4.3) is newer than garuda (5-4)
resolving dependencies...
warning: ignoring package qemu-base-8.1.2-1
warning: cannot resolve "qemu-base=8.1.2-1", a dependency of "qemu-desktop"
:: The following package cannot be upgraded due to unresolvable dependencies:

:: Do you want to skip the above package for this upgrade? [y/N] n
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'qemu-base=8.1.2-1' required by qemu-desktop

The recommended solution has always been to remove virt-manager and virt-manager-meta and then to reinstall them. I have been doing that each time. However, it’s getting tedious. I need virt-manager for my VMs, so I can’t permanently uninstall it.

I’d like not to have to uninstall it every time there’s a qemu update available. Is there a more permanent solution to the problem?

The problem might be due to this condition in the garuda-update:

qemu-base is ignored but there might be other updates e.g. in qemu-desktop which get blocked.
I don’t remember why this was introduced and don’t know if this is still needed.
I think we should consider also this:

OK, now I’m lost :slight_smile:


I was able to solve this issue by running :

sudo pacman -Syu

Edit : type i to ignore the warning message .


I’m very much assuming that the --ignore flag of the first link @filo posted is the culprit here. So updating via pacman -Syu should be the solution. There were no apparent issues while installing virt-manager-meta yesterday for me.


Is this a one-time solution or would I have to run the command every time I use garuda-update and get the qemu-base error?

I think if we don’t fix garuda-update for that matter, running a sudo pacman -Syu would be only a workaround, necessary every time qemu has been updated.


I now i’m just a noob, but you can’t modify the update somehow, to check if there is a warning, if yes, then remove qemu, do the update, then reinstall qemu?

sometimes automating the “pick it up and then reinstall” can cause issues in software. care must be taken, a big reason behind the “never use (program X) to do updates, always use garuda-update(or symlinks/renames) to upgrade your system”


its one time solution , it fixes every issue you mention .

no @wWolfff32 , there is no need for that , its an aggressive way to solve issues , so its a little problem no need for this ,but it works in other things so yeah :wink:

Octopi does that, no? If i hit check updates, and install… I always do update with octopi. It was a mistake?

OK. Next question. What is quemu anyway. I mean i now what it is, but it is really necessary to be in stock for a basic game edition user, who just want to play? I use vmware for some basic winows c# dev, but nothing more. So why it’s in there in a first place???

it is one of those things that isn’t a problem, until it is. before others can jump in on you let me put it nicely. Please don’t use octopi to do updates, things can “break” and render your system to be a mystery when you ask for help. Octopi can be used for installing applications(insert snark about using pacman in the commandline) but using it to do updates really isn’t a good idea.


If you don’t know what qemu is and are not using virt-manager you might as well uninstall virt-manager-meta - I’m not 100% sure it’s included, but that’s one package pulling those packages.

# Anything printed by this script into stdout will be added as a pacman parameter to pacman -Syu
    if [[ "$packages" =~ (^| )qemu-base($| ) ]] && [[ "$packages" =~ (^| )virt-manager-meta($| ) ]]; then
        echo --ignore
        echo qemu-base

This may be a dumb question, but do we still want this?

What is the situation where this provides a benefit?

1 Like

it is included by “default” in both kde dragonized and dragonized gaming.

For sure not in the regular one. I’ve installed that just yesterday :eyes:

1 Like

odd, i swear i remember it in both… but for certain it IS in the one i recently used to build out a new vm as part of a conversation in another thread. which is “fully-updated” without going through the first boot setup wizard

Its like vmware but better cause its virtualization in kernel level , its like the VM running in bare metal , its so fast , and why its there ? like i said its kernel based VM manager so you can run VMs without third party apps , but still can be removed if it is not necessary for you and you don’t use it .
but i really recommend it if you want a better and more secure/private VMs running in your system .

I understand, but i’am speaking now like a complete noob here, who just dropped windows, like 3/4 year ago. But I used linux before. In my last 25 years or so, tried many of it, when they come with Computer magazines. Mandrake, Suse, Fedora (when i want to try ot, how Autodesk Maya works), Ubuntu, Debian, Mint… and now this Garuda KDE-Gaming…

But you know, how i ended up here? I did a goggle search about “gamin on linux” and almost every sites what i read praised Garuda. So downloaded it, installed it. And… I was amazed how linux desktop evolved from that to this. Now instead of lightroom, i’m using rawtherapee, instead of sony vegas i’m using Kdenlive, and so on. Only have Windows just for some silly windows developing in visual studio, and for photoshop. (just because I didn’t found any substituton yet), and for autodesk maya. And youre right, i’m using this, because used under windows as well and it’s familiar.

And trully believe that, in the near feature more and more average win users gonna turn to linux, and while i wanna learn how linux works inside and out, so maybe in a far feature i can contribute somehow, most of us don’t. We are not hackers. We hate typeing, we need buttons, and something what is working out of the box. But the most important thing, we hate bloats. And we just wanna play, listen music, and watch movies, or edit our music, video or photoshoots, or doodleing with blender. We wanna use apps, we wanna use, and not what is forced to us.

So asking again like a complete noob, (and this is not like if i wanna tell you, how should it be) : Why is quemu needed in a Gaming-editition, what title obviously gonna pull in gamers and average users not IT gurus. Why it is uninstall if you don’t need it, and not install it if you need it? Why it is not a checkbox in the assistant, or the installer, or wherever.