Ok, so the problem is the special way inactive domains are handled in xend. And
one expectation which is wrong. I don't have any xen versions older than 3, so
I cannot really check backwards. But from other places in the current code
there was a change about then to have no state and domid presented for inactive
domains. This is handled by assigning new connections a domain->id of -1.
As soon as an instance is started, this gets replaced by the id which is then
assigned. At this point I am not sure whether and where this should get reset
to -1 as soon as the instance goes down.
But fact is that when the instance is shut down, and an established
connection calls GetDomainInfo, the unified driver calls out to its
various sub-drivers. The hypervisor driver won't find the domain
anymore, so the next in sequence is the xend driver. That checks for
different states looking at the domain/state node (which is not present
anymore after shutdown) and then checks for domain->id to be -1 in order
to handle the inactive instance. But this only works as long as the
instance has not been started before.
>From my hosts it seems that there is an additional node (domain/status)
which is always present and contains 0 for inactive instances (2 for
running). So I replaced the check by looking for that.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929626
Title:
virt-manager misses xen guests shutting down
To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/929626/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
