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

Bug 1640479

Summary: Starting and stopping VM takes long time + 'QEMU Guest Agent failed' ERROR in vdsm.log
Product: [oVirt] ovirt-engine Reporter: Ilan Zuckerman <izuckerm>
Component: GeneralAssignee: Tomáš Golembiovský <tgolembi>
Status: CLOSED WORKSFORME QA Contact: Ilan Zuckerman <izuckerm>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.7.1CC: bugs, dagur, izuckerm, rbarry
Target Milestone: ovirt-4.3.1Keywords: Performance
Target Release: ---Flags: rule-engine: ovirt-4.3+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-24 13:04:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Manual stop / start
none
libvirt log for that vm
none
vdsm log from the host running vm
none
engine log none

Description Ilan Zuckerman 2018-10-18 08:07:41 UTC
Created attachment 1495174 [details]
Manual stop / start

Description of problem:
Starting and stopping vm from engine web admin takes very long time to complete.
I measured the avg time it takes for both operations to complete by executing a script which starts and then stops one particular vm (having only one vm on host) 5 times in a row (it verifies the vm is in appropriate state prior issuing it to stop / start).
AVG for start: 1min 10sec
AVG for stop:  1min 32sec

Looking at vdsm log of appropriate host we see the following error occurs 5 times (as amount of times 'stop' issued):

2018-10-18 06:51:54,620+0000 ERROR (Thread-39) [root] Shutdown by QEMU Guest Agent failed (vm:5413)

Version-Release number of selected component (if applicable):
-=>>rpm -qa vdsm
vdsm-4.20.42-1.el7ev.x86_64

-=>>rpm -q ovirt-engine
ovirt-engine-4.2.7.2-0.1.el7ev.noarch

How reproducible:
100%

#Topology
Engine / Engine DB (1 machine)
DWH DB (separate machine)
400 Hosts
4000 VMs
RHEL 7.6
The host on which the vm resides, doesnt have any other vms on it.

Steps to Reproduce:
1. From the web admin ui issue a start / stop for vm named 'VM_2_HDD_Guy_1'

Actual results:
AVG for start: 1min 10sec
AVG for stop:  1min 32sec

Expected results:
Should be much faster
No ERRORS should be logged

Additional info:
Video attached with manual stop / start with VM console point of vew.
Environment details are shared within private message.
Be Advised, the system is under continuous testing and BZs reproduction.

Comment 2 Ilan Zuckerman 2018-10-18 08:10:23 UTC
Created attachment 1495175 [details]
libvirt log for that vm

Comment 3 Ilan Zuckerman 2018-10-18 08:11:02 UTC
Created attachment 1495176 [details]
vdsm log from the host running vm

Comment 4 Ilan Zuckerman 2018-10-18 08:11:23 UTC
Created attachment 1495177 [details]
engine log

Comment 5 Ryan Barry 2018-10-19 10:50:05 UTC
Probable duplicate of rhbz#1640193

Comment 6 Ryan Barry 2019-01-21 14:54:23 UTC
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both

Comment 7 Ryan Barry 2019-01-24 00:12:55 UTC
Is this still reproducible?

Comment 8 Ilan Zuckerman 2019-01-24 09:27:16 UTC
(In reply to Ryan Barry from comment #7)
> Is this still reproducible?

Nope, couldnt reproduce this on latest downstream.