jamke

I have the same message: `qrexec-daemon startup failed: 2022-11-16 12:17:08.046 qrexec-daemon[26396]: qrexec-daemon.c:135:sigchld_parent_handler: Connection to the VM failed` on up-to-date R4.1.1 with fedora-36 or other template (e.g. fedora-35) when I'm trying...

Well. After `sudo qubes-dom0-update kernel-latest` I can't boot at all with eGPU installed (even not connected to display, nor selected in BIOS as default one). I have Kernel panic after...

> * From time to time cursor is not being cleared properly. Yes, I still have it on a clean up-to-date R4.1.1 installation, it's not fixed. The movement over desktop...

On the other hand - the described problem with insanely slow redrawing and 100% CPU consumption gone, probably due to kernel version being updated.

I checked the situation with current Qubes OS USB installer with only iGPU (Intel) being used, without eGPU. The installer uses kernel `5.15.52-1.fc32q.qubes.x86_64`. I saw no major issues with super-slow...

I cannot start Windows 10 with USB controller even with **1800 MB**, it shows `no bootable device` error. And running Windows 10 with something useful on less than 2 GiB...

Is it a diagnosed problem knowing that the bug is in `xen-hvm-stubdom-linux` and there is some patch about it: https://github.com/QubesOS/qubes-vmm-xen-stubdom-linux/commit/be8896ba2fae2e377aa236df4407bc7dbdcec60b Or is it not a working fix? Why is the...

Sorry for several posts in a row, but I want also note, that the **topic's workaround does not work anymore** (`qubes-dom0-update --action=downgrade xen-hvm-stubdom-linux`). Because the last working `xen-hvm-stubdom-linux` seems to...

Can somebody with R4.2 check this, maybe it is somehow miraculously fixed? Or add `affects-4.2` if needed.

> it works for me on R4.2 with these USB controllers: Thanks, do any of these USB controllers have PCIe physical connection (so that you can populate PCIe slot of...