-
-
Notifications
You must be signed in to change notification settings - Fork 22
Fix handling of already assigned PCI devices #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
assign() raises DeviceAlreadyAssigned exception, not DeviceAlreadyAttached. While at it, fix reporting changed devices (report no change if nothing was changed), and also skip re-assigning if options didn't change.
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025041016-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025031804-4.3&flavor=update
Failed tests15 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/132953#dependencies 8 fixed
Unstable testsPerformance TestsPerformance degradation:26 performance degradations
Remaining performance tests:46 tests
|
Stop pretending qubes API uses BDF directly, as now with conversion to PCI paths it's not plausible anymore. And with a change in grains to list qubes's API identifiers it's not matching anymore anyway. But more importantly, using consistent identifiers is important if device need to have options changed, as the "old" device id need to match the "new" one - otherwise removing old one from list of assigned devices (value_combined variable) would fail. QubesOS/qubes-issues#8681
assign() raises DeviceAlreadyAssigned exception, not
DeviceAlreadyAttached. While at it, fix reporting changed devices
(report no change if nothing was changed), and also skip re-assigning if
options didn't change.