-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
xenstore dirs in network backend are not cleaned up correctly #5369
Comments
Found it: there is xen-hotplug-cleanup script, patched in our package to specifically remove this cleanup as it didn't worked because of lack of permissions. And the script is gone in upstream Xen 4.12, as it wasn't called by anything anymore (and the actual commit removing it is mine...). |
Aha - this is the cause of the mirage-firewall crashes in mirage/qubes-mirage-firewall#35 too. We have to monitor all these empty directories in case new interfaces get added to them, but each one costs us a XenStore watch and if you ask for too many then XenStore returns |
Driver domain is responsible for xenstore cleanup, but it doesn't have access to remove (empty) parent directory. Do it in toolstack domain as the final step. Fixes QubesOS/qubes-issues#5369 (cherry picked from commit df0f102)
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Qubes OS version
R4.0
Affected component(s) or functionality
xen
Brief summary
Xenstore directories of network backends are not cleaned up after removing actual backend devices. Empty directories named after previously connected VM's IDs remains. After fair amount of VM startups, empty dirs trigger per-vm entries quota (1000 entries). User visible effect is failure to connect/start further VMs and
E2BIG
messages in network backend VM kernel log.To Reproduce
Start and stop a VM connected to sys-firewall a lot of times. Happens during integration tests.
Expected behavior
Old entries are removed.
Actual behavior
Actual entries are removed, but containing directory stays.
Additional context
I vaguely remember a call to remove this directory done by the backend, failing because of missing permission (would have worked with network backend in dom0). I can't find it right now.
Related, non-duplicate issues
Similar to #5343.
The text was updated successfully, but these errors were encountered: