# virsh list --all Id Name State ---------------------------------- 0 Domain-0 running - windows-xen shut off - windows-xen2 no state # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3489 4 r----- 853.6 windows-xen 1 512 0 -b-s-d 39.4 windows-xen2 4 512 0 ------ 22.5 The windows-xen, and windows-xen2 domains were installed the very same way, except I've had a Dom0 reboot since I've installed windows-xen, so xen has had the opportunity to sort it's state out, whil the windows-xen2 domain is a fresh install. Starting and stopping (by xm) a freshly installed windows hvm domain does not sort out the state, only a Dom0 reboot (or a xend restart) does. I have attached the output of xm list --long command.

This problem indeed does look like a Xend bug, but it turns out that it does not actually affect virsh. (It does affect virt-manager, as I've written to the other list)

The other problem is I am pretty sure, a virsh logic bug, and is independent of the first one.

and I get this: ./virsh start windows-xen <warnings> error: Domain is already active virDomainGetID(dom) returns 1 ./virsh start windows-xen2 <warnings> error: Domain is already active virDomainGetID(dom) returns 3 so virDomainGetID() does not return -1, but returns the actual xen domain id of the managed, but inactive xen domain, and I believe this is what it should do, as it's job is not to tell us about the state of the domain, but to tell the id of the domain, regardles of its state.