Hi,
since the last upgrade, I get the error “external exception 80000004” in every Windows 11 VM, 23h2 and 24h2, with some installers. The same VMs with identical Libvirt configuration on Kubuntu 24.10 on the same hardware, does not have the problem.
Since QEMU was updated during the upgrade, I suspect this as a possible cause.
For example CrystalDiskMark can’t be installed under CachyOS, but no problem under Kubuntu
I was under the assumption that CrystalDiskMark was a Linux program, I guess not.
When you say this, do you mean that the configuration files were copied over? Since there is a one major version difference between Arch’s and Ubuntu’s libvirt, that may not work.
Hi @Janos I was googling because I had the exact same issue since the upgrade last week. It got so bad I even tried setting up a KVM to avoid my virtualized work OS issues.
I cannot install Citrix Workspace and maybe 50% of all my applications. Even dependencies are failing ever since I did my full system CachyOS upgrade.
I’m using VMWare btw, but with you on Libvirt this tells me its a dependency change that caused this.
warning: linux-cachyos-lts-6.12.12-1 is up to date – reinstalling
warning: linux-cachyos-lts-headers-6.12.12-1 is up to date – reinstalling
warning: linux-cachyos-nvidia-6.13.1-2 is up to date – reinstalling
resolving dependencies…
looking for conflicting packages…
:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring [--------------------------------] 100%
(2/2) checking package integrity [--------------------------------] 100%
(2/2) loading package files [--------------------------------] 100%
(2/2) checking for file conflicts [--------------------------------] 100%
:: Processing package changes…
(1/2) installing linux-cachyos-lts [--------------------------------] 100%
Optional dependencies for linux-cachyos-lts
wireless-regdb: to set the correct wireless channels of your country
linux-firmware: firmware images needed for some devices [installed]
modprobed-db: Keeps track of EVERY kernel module that has ever been probed - useful for those of
us who make localmodconfig
scx-scheds: to use sched-ext schedulers [installed]
(2/2) installing linux-cachyos-lts-headers [--------------------------------] 100%
:: Running post-transaction hooks…
(1/6) Arming ConditionNeedsUpdate…
(2/6) Updating module dependencies…
(3/6) Install DKMS modules
==> dkms install --no-depmod vmware-workstation/17.6.2_24409262 -k 6.12.12-1-cachyos-lts
==> depmod 6.12.12-1-cachyos-lts
(4/6) Updating linux initcpios…
==> Building image from preset: /etc/mkinitcpio.d/linux-cachyos-lts.preset: ‘default’
==> Using default configuration file: ‘/etc/mkinitcpio.conf’
→ -k /boot/vmlinuz-linux-cachyos-lts -g /boot/initramfs-linux-cachyos-lts.img
==> Using drop-in configuration file: ‘10-chwd.conf’
==> Starting build: ‘6.12.12-1-cachyos-lts’
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [autodetect]
→ Running build hook: [microcode]
→ Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: ‘nouveau’
→ Running build hook: [modconf]
→ Running build hook: [block]
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
→ Running build hook: [plymouth]
→ Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: ‘qat_420xx’
→ Running build hook: [filesystems]
==> ERROR: module not found: ‘nvidia’
==> ERROR: module not found: ‘nvidia_modeset’
==> ERROR: module not found: ‘nvidia_uvm’
==> ERROR: module not found: ‘nvidia_drm’
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: ‘/boot/initramfs-linux-cachyos-lts.img’
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux-cachyos-lts.preset: ‘fallback’
==> Using default configuration file: ‘/etc/mkinitcpio.conf’
→ -k /boot/vmlinuz-linux-cachyos-lts -g /boot/initramfs-linux-cachyos-lts-fallback.img -S autodetect
==> Using drop-in configuration file: ‘10-chwd.conf’
==> Starting build: ‘6.12.12-1-cachyos-lts’
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [microcode]
→ Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: ‘ast’
==> WARNING: Possibly missing firmware for module: ‘nouveau’
→ Running build hook: [modconf]
→ Running build hook: [block]
==> WARNING: Possibly missing firmware for module: ‘aic94xx’
==> WARNING: Possibly missing firmware for module: ‘bfa’
==> WARNING: Possibly missing firmware for module: ‘qed’
==> WARNING: Possibly missing firmware for module: ‘qla1280’
==> WARNING: Possibly missing firmware for module: ‘qla2xxx’
==> WARNING: Possibly missing firmware for module: ‘wd719x’
==> WARNING: Possibly missing firmware for module: ‘xhci_pci_renesas’
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
→ Running build hook: [plymouth]
→ Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: ‘qat_420xx’
→ Running build hook: [filesystems]
==> ERROR: module not found: ‘nvidia’
==> ERROR: module not found: ‘nvidia_modeset’
==> ERROR: module not found: ‘nvidia_uvm’
==> ERROR: module not found: ‘nvidia_drm’
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: ‘/boot/initramfs-linux-cachyos-lts-fallback.img’
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
(5/6) Refreshing PackageKit…
(6/6) Updating systemd-boot entries
~ 20s
❯
That last “error: command failed to execute correctly” is telling me they failed to install altogether? Is that why I’m not seeing them as boot entries in systemd?
EDIT:
I see the LTS option in systemd, I select it to boot and I can already tell from the stretched out decryption screen that there is a driver related issue. I enter my decryption password and get stuck on a black screen with just a white “_”.
It stays like this until I forcefully shutdown.
On reboot, I can go back to the latest regular cachyos kernel just fine, but again I am having odd issues in my VMs since I did a last full system upgrade. Unlike OP I am not using QEMU, I removed all packages just to make sure. I’m still having this persistent error in my win10 & 11 VMs via VMware.
Out of curiosity I copied these VMs to another computer (laptop) running fedora and they booted up just fine with no changes.
