Hide Forgot
Description of problem: I find it when I test vm installation with perl-sys-virt, after vm finishing installing and shutdown, the perl function get_state() still show that the vm state is running; If I destroy the vm during installation, then get_state() show the vm state is blocked; If I then restart libvirtd, then get_state() will show that vm state is nostate Version-Release number of selected component (if applicable): perl-Sys-Virt-0.9.10-4.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. run script with perl-sys-virt 2. 3. Actual results: get_state() return confusing Expected results: get_state() can return the real vm state when domain is shutdown Additional info:
The 'get_state' function doesn't do anything special - it just calls into the virDomainGetState() C API. So if there is a flaw here, it is probably in the libvirt layer. Can you try creating a simple demo in C that reproduces the problem, or see if 'virsh dominfo' shows the same behaviour
(In reply to comment #2) > The 'get_state' function doesn't do anything special - it just calls into the > virDomainGetState() C API. So if there is a flaw here, it is probably in the > libvirt layer. > > Can you try creating a simple demo in C that reproduces the problem, or see if > 'virsh dominfo' shows the same behaviour # virsh dominfo rhel6 Id: - Name: rhel6 UUID: 8f7d7e4c-2c44-49f8-9c59-09b609b00ebd OS Type: hvm State: shut off CPU(s): 1 Max memory: 1048576 kB Used memory: 524288 kB Persistent: yes Autostart: disable Managed save: no Security model: selinux Security DOI: 0 At the same time, run dom->get_state() return 0, which means nostate
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.