Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 872205

Summary: [RHEVM] libvirt , cannot unpause VM started in paused mode (_readPauseCode unsupported by libvirt vm)
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Pavlik <mpavlik>
Component: ovirt-engineAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: Ido Begun <ibegun>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.1.0CC: abaron, acathrow, bazulay, cpelland, danken, dyasny, gklein, iheim, jdenemar, lpeer, michal.skrivanek, ofrenkel, oramraz, pstehlik, rgolan, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 20:12:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sosreport
none
screenshot 1 none

Description Martin Pavlik 2012-11-01 14:42:36 UTC
Created attachment 636693 [details]
sosreport

Description of problem:
When VM is stater in paused mode and user tries to unpause it, follwoing error appears in GUI (see screenshot)

Error while executing action: Cannot run VM. There are no available running Hosts in the Host Cluster.


Version-Release number of selected component (if applicable):
RHEV-M
rhevm-3.1.0-25.el6ev.noarch.rpm
LIBVIRT
libvirt-0.9.10-21.el6.x86_64.rpm
VDSM
vdsm-4.9.6-40.0.el6_3.x86_64.rpm
QEMU-KVM
qemu-kvm-rhev-0.12.1.2-2.295.el6_3.4.x86_64.rpm


How reproducible:
100%

Steps to Reproduce:
1. Create new VM with disk
2. Run once -> start in paused mode
3. Try to run the machine
  
Actual results:
Error message appears, VM does not start

Expected results:
VM starts


Additional info:
logs from host are in following path in attache logcollector
/mp-rhevm31-2012110115261351779964/tmp/logcollector/RHEVH-and-PostgreSQL-reports/dell-r210ii-05.rhev.lab.eng.brq.redhat.com/

vdsm.log 
Thread-1823::WARNING::2012-11-01 14:20:46,124::libvirtvm::1622::vm.Vm::(_readPauseCode) vmId=`a7efc488-0442-49bd-ad5b-b8e334ffc3d1`::_readPauseCode unsupported by libvirt vm

engine.log
2012-11-01 15:20:45,436 INFO  [org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (ajp-/127.0.0.1:8702-8) [3e5835e9] IncreasePendingVms::CreateVmIncreasing vds dell-r210ii-05.rhev.lab.eng.brq.redhat.com pending vcpu count, now 1. Vm: START_PAUSED

Comment 1 Martin Pavlik 2012-11-01 14:45:56 UTC
Created attachment 636694 [details]
screenshot 1

Comment 3 Jiri Denemark 2012-11-01 15:32:26 UTC
This is not a libvirt bug. The functionality works as expected when libvirt is used directly. Moreover, according to the logs nothing even tried to call any API for that domain except for getting block stats. Also, the message from vdsm.log is just a warning and it does not in fact have anything to do with libvirt. Look at _readPauseCode implementation in libvirtvm.py:

     def _readPauseCode(self, timeout):
         self.log.warning('_readPauseCode unsupported by libvirt vm')
         return 'NOERR'

I'm moving this bug to vdsm so that they can check where the real issue is.

Comment 5 Dan Kenigsberg 2012-11-01 19:20:32 UTC
I'm afraid this has to go further up the management stack as - at least in the attached logs - there is no trace of someone requesting to "cont" the vm a7efc488-0442-49bd-ad5b-b8e334ffc3d1.

I vdsm reporting the Paused state, but no attempt to change it later.

engine.log:2012-11-01 15:20:47,477 INFO  [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (QuartzScheduler_Worker-86) VM START_PAUSED a7efc488-0442-49bd-ad5b-b8e334ffc3d1 moved from WaitForLaunch --> Paused

Comment 9 Michal Skrivanek 2012-11-02 14:30:17 UTC
happens when you have only one host in a cluster and you have different available hosts in other clusters. Then resume fails in CanDoAction.

Comment 10 Tomas Jelinek 2012-11-02 16:19:17 UTC
http://gerrit.ovirt.org/#/c/8994/

Comment 14 Martin Pavlik 2012-11-05 08:34:20 UTC
Verified on si24, VM can be started in paused mode and resumed on setup with one host.