search

QubesOS / qubes-issues

The Qubes OS Project issue tracker
https://www.qubes-os.org/doc/issue-tracking/
541 stars 48 forks source link

sys-gui-gpu & sys-usb HVM autostart race condition fails #7954

Open ZYousef opened 1 year ago

ZYousef commented 1 year ago

How to file a helpful issue

Qubes OS release

QR4.1

Brief summary

When having sys-gui-gpu and sys-usb set to start automatically they endup crashing 20% of the times.

Steps to reproduce

set both sys-usb & sys-gui-gpu autostart to true. set sys-usb target to sys-gui-gpu (/etc/qubes/input-proxy-target in dom0) try to boot up into sys-gui-gpu

Expected behavior

The guivm starts up and has access to the keyboard & mouse from sys-usb

Actual behavior

20% of the time the system fails when running AppVMs startup sequence. Sometimes the guivm runs without access to usbvm keyboard or mouse, deeming it unusable.

Note: Currently if disable the qubes-vm@sys-usb service it works fine most of the time, but takes a much longer time to fully boot up.

marmarek commented 1 year ago

What if you setup a ordering dependency between those two? You can do this by creating /etc/systemd/system/qubes-vm@sys-usb.service.d/30_order.conf with:

[Service]
After=qubes-vm@sys-gui-gpu.service
ZYousef commented 1 year ago

Thanks! this works fine. If guivm is set to sys-gui-gpu the usbvm sls formula should install this service instead.

What if you setup a ordering dependency between those two? You can do this by creating /etc/systemd/system/qubes-vm@sys-usb.service.d/30_order.conf with:

[Service]
After=qubes-vm@sys-gui-gpu.service