out). So is there some other
state implied by domain_flags being 0? In all cases I have seen, the domain
is actually running -- accumulating CPU time, etc.
-
Russ Blaine | Solaris Kernel | [EMAIL PROTECTED]
--
Libvir-list mailing list
Libvir
Host is Solaris, guest is WinXP.
Richard W.M. Jones wrote:
Russ Blaine wrote:
Daniel P. Berrange wrote:
Can you edit the src/xen_internal.c file and in the
xenHypervisorGetDomInfo()
method, add a printf() for the 'domain_flags' flags variable. IMHO the
way we deal with this isn't quite
in getdomaininfo, from xen/common/domctl.c
-
Russ Blaine | Solaris Kernel | [EMAIL PROTECTED]
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
their act together, that do not always return a valid guest state. Is that
the case?
Is anyone else seeing this on Xen?
--
-
Russ Blaine | Solaris Kernel | [EMAIL PROTECTED]
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com
Richard W.M. Jones wrote:
Russ Blaine wrote:
On Solaris-based xen 3.1.2 I am seeing virDomainGetInfo() often
returning VIR_DOMAIN_NOSTATE in dominfo.state for domUs that are
powered on and running. What exactly does VIR_DOMAIN_NOSTATE mean? Why
does it exist? I suspect it is a catch-all
