device busy attribute to prevent attaching devices whose children are in use - #478
piotrbartman wants to merge 2 commits into
Conversation
mirror the qubes-core-admin change. add serialization/deserialization of `busy` property so that devices with a child currently passed through to a VM can be listed without being offered for attachment. Absence of the key means available (not busy).
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #478 +/- ##
==========================================
- Coverage 76.79% 76.48% -0.31%
==========================================
Files 53 53
Lines 9402 9543 +141
==========================================
+ Hits 7220 7299 +79
- Misses 2182 2244 +62 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026071723-devel&flavor=pull-requests Test run included the following:
Upload failures
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026050504-devel&flavor=update
Failed tests22 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/176874#dependencies 25 fixed
Unstable testsDetails
Performance TestsPerformance degradation:19 performance degradations
Remaining performance tests:91 tests
|
`--force` on `qvm-device attach`, resolved client-side: the device detached from the fron VM, and every subdevice of it attached elsewhere (via `admin.vm.device.<class>.Detach`). Then the attach.
mirror the qubes-core-admin change: QubesOS/qubes-core-admin/pull/840