Cole Robinson <crobinso@xxxxxxxxxx> writes: >> thanks, in fact it doesn't seem to be the issue. Only the debugging >> message prints it as VIR_DOMAIN_NOSTATE, while the rest of the code >> considers it as VIR_DOMAIN_RUNNING. Something else is going on, as >> calling virDomainInfo twice, "fix" the problem, and that is why >> re-enabling polling fix the issue. I will look more into it. > > A long time ago I encountered similar issues with RHEL5 xen, after a domain > state change an info() call could report totally bogus data, basically > everything was zeros IIRC. I think I even patches virt-install to try info() a > few times while we were waiting for the VM to change state after install > completed. > > Disabling polling might be kinda drastic, but I'd rather do that than > conditionally call info() twice or something like that. and since it was ok before, I am going to push this version and let successive invocations of virDomainInfo fix the bogus state. Thanks, Giuseppe _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
