|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] [Bug 287] New: No true noticfication mechanism for Xen tools
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=287
Summary: No true noticfication mechanism for Xen tools to
determine when a domain has completely been destroyed
Product: Xen
Version: unstable
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Tools
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: jyoung5@xxxxxxxxxx
Problem:
Today Xen tools depend on getting a VIRQ to determine if a domain has
completely gone away. The problem with this is that the VIRQ is given from the
hypervisor when a domain is asked to be destroyed. A domain is not compleltely
destroyed until all memory mapped in the domain is unmapped. The VIRQ that is
given to the tools is normally delivered before the domain is truly destroyed.
So there is a brief period of time after the domain VIRQ is delivered when the
domain has not actually gone away. There is no notification for the tools to
know that it has completley gone away, so today the tools have to assume that
once they receive a VIRQ then the domain is gone.
Possible Solution:
A robust event system so that tools can distinguish when a domain has
begun
dying & when the domain has died. Using another VIRQ to signal that the domain
is compeletely gone could be a solution.
--
Configure bugmail:
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-bugs] [Bug 287] New: No true noticfication mechanism for Xen tools to determine when a domain has completely been destroyed,
bugzilla-daemon <=
|
|
|
|
|