-
Notifications
You must be signed in to change notification settings - Fork 15
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
go to state closed and wait for ack before removing vif #105
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I unfortunately don't know this part of xen :/
What I can confirm just now is that in Qubes dom0, when I busy-loop reading the I still want to see what the current mirage-firewall is doing in that scenario, and whether this fix fixes it. Any pointers to the state machine transitions of xen devices would be appreciated -- I've read chapter 6 in Chisnall's "The Definitive Guide to the Xen Hypervisor" (thanks to the pointer from @reynir), but still fail to understand what the desired interaction of the state should be. |
See: mirage/mirage-qubes#25 (comment) (and https://github.com/xen-project/xen/blob/e61a78981364925a43c9cc24dc77b62ff7b93c9f/xen/include/public/io/blkif.h#L482) |
Thanks @talex5, unfortunately that refered diagram is only for startup, and stops at |
I unfortunately have no documentation, it's just from the following commands:
The main motivation for setting to state But when setting to state closed before removing I have:
This now introduce the line The |
Thanks, I verified that this patch works with qubes-mirage-firewall. The xenstore-read is also as expected. Changing forth and back between sys-firewall and mirage-firewall works nicely with this patch applied. |
CHANGES: * netback: go to closed state before removing vif from xenstore (@palainp, mirage/mirage-net-xen#105, addresses mirage/qubes-mirage-firewall#157)
This PR is needed to change the state to closing and wait for the frontend to be ready before removing the vif. This should fix mirage/qubes-mirage-firewall#157.