Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 778146[details]
logs
Description of problem:
When trying to run a VM which is in 'pause' state, the operation fails with this error on the machine's qemu log:
kvm: unhandled exit 80000021
kvm_run returned -22
libvirt.log:
2013-07-25 08:34:42.799+0000: 2476: error : qemuMonitorJSONCheckError:355 : internal error unable to execute QEMU command 'cont': Resetting the Virtual Machine is required
vdsm.log:
Thread-87607::ERROR::2013-07-25 11:33:57,055::BindingXMLRPC::989::vds::(wrapper) libvirt error
Traceback (most recent call last):
File "/usr/share/vdsm/BindingXMLRPC.py", line 984, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/BindingXMLRPC.py", line 227, in vmCont
return vm.cont()
File "/usr/share/vdsm/API.py", line 144, in cont
return v.cont()
File "/usr/share/vdsm/vm.py", line 2320, in cont
self._underlyingCont()
File "/usr/share/vdsm/vm.py", line 3377, in _underlyingCont
self._dom.resume()
File "/usr/share/vdsm/vm.py", line 824, in f
ret = attr(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 76, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1306, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirtError: internal error unable to execute QEMU command 'cont': Resetting the Virtual Machine is required
Version-Release number of selected component (if applicable):
rhevm-3.3.0-0.9.master.el6ev.noarch
vdsm-4.12.0-rc3.el6.x86_64
libvirt-0.10.2-18.el6_4.9.x86_64
qemu-kvm-rhev-0.12.1.2-2.355.el6_4.5.x86_64
How reproducible:
100%
Steps to Reproduce:
1. on a RHEV setup: have a data center (iscsi) with a vdsm hypervisor and 2 storage domain created from 2 different storage servers
2. run a VM on the host (with a disk located on the master storage domain)
3. block connectivity from host to the non master storage domain using iptables
4. when VM enters to 'pause' state, resume connectivity to storage, and activate the host again
5. when host is active again, try to activate the VM
Actual results:
VM activating is failing, and user has to restart the VM
Expected results:
VM activating should work
Additional info: logs
According to comment #2, this bug should be closed as a duplicate of Bug 888767 or a duplicate of the new bug created: Bug 1011472. Is there anything you still want from us (qemu-kvm?)
(In reply to Ademar de Souza Reis Jr. from comment #3)
> According to comment #2, this bug should be closed as a duplicate of Bug
> 888767 or a duplicate of the new bug created: Bug 1011472. Is there anything
> you still want from us (qemu-kvm?)
According to bug 1011472, we cannot run vm from pause state. After deeper investigation, we concluded that it has nothing to do with our problem here. I'm removing the depends on flag.
Regarding to this bug issue, I checked the scenario with qemu-kvm-rhev-0.12.1.2-2.396.el6.x86_64 according to Chao's request and it does not seem to reproduce.
(In reply to Elad from comment #4)
>
> Regarding to this bug issue, I checked the scenario with
> qemu-kvm-rhev-0.12.1.2-2.396.el6.x86_64 according to Chao's request and it
> does not seem to reproduce.
Closing then. Please reopen if there's anything pending from our side.
Created attachment 778146 [details] logs Description of problem: When trying to run a VM which is in 'pause' state, the operation fails with this error on the machine's qemu log: kvm: unhandled exit 80000021 kvm_run returned -22 libvirt.log: 2013-07-25 08:34:42.799+0000: 2476: error : qemuMonitorJSONCheckError:355 : internal error unable to execute QEMU command 'cont': Resetting the Virtual Machine is required vdsm.log: Thread-87607::ERROR::2013-07-25 11:33:57,055::BindingXMLRPC::989::vds::(wrapper) libvirt error Traceback (most recent call last): File "/usr/share/vdsm/BindingXMLRPC.py", line 984, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/BindingXMLRPC.py", line 227, in vmCont return vm.cont() File "/usr/share/vdsm/API.py", line 144, in cont return v.cont() File "/usr/share/vdsm/vm.py", line 2320, in cont self._underlyingCont() File "/usr/share/vdsm/vm.py", line 3377, in _underlyingCont self._dom.resume() File "/usr/share/vdsm/vm.py", line 824, in f ret = attr(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 76, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1306, in resume if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self) libvirtError: internal error unable to execute QEMU command 'cont': Resetting the Virtual Machine is required Version-Release number of selected component (if applicable): rhevm-3.3.0-0.9.master.el6ev.noarch vdsm-4.12.0-rc3.el6.x86_64 libvirt-0.10.2-18.el6_4.9.x86_64 qemu-kvm-rhev-0.12.1.2-2.355.el6_4.5.x86_64 How reproducible: 100% Steps to Reproduce: 1. on a RHEV setup: have a data center (iscsi) with a vdsm hypervisor and 2 storage domain created from 2 different storage servers 2. run a VM on the host (with a disk located on the master storage domain) 3. block connectivity from host to the non master storage domain using iptables 4. when VM enters to 'pause' state, resume connectivity to storage, and activate the host again 5. when host is active again, try to activate the VM Actual results: VM activating is failing, and user has to restart the VM Expected results: VM activating should work Additional info: logs