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

Bug 1335840

Summary:	VMs reported as paused after libvirtd restart
Product:	[oVirt] vdsm	Reporter:	Milan Zamazal <mzamazal>
Component:	Core	Assignee:	Milan Zamazal <mzamazal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.18.0	CC:	bugs, mgoldboi, michal.skrivanek
Target Milestone:	ovirt-3.6.7	Flags:	rule-engine: ovirt-3.6.z+ rule-engine: planning_ack+ michal.skrivanek: devel_ack+ rule-engine: testing_ack+
Target Release:	4.17.29
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When libvirtd was restarted and some VMs with disabled balloon device were running at the time of the restart, those VMs started to be incorrectly reported as paused even when they were actually running. This has been fixed and the correct state is reported for the VMs after libvirtd restart.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-04 12:32:49 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:

Description Milan Zamazal 2016-05-13 11:00:01 UTC

Description of problem:

When libvirtd is restarted on a host where a VM with memory balloon device disabled is running, then the VM gets reported as paused in Vdsm and Engine despite it is actually running.

Version-Release number of selected component (if applicable):

All versions.

How reproducible:

Always.

Steps to Reproduce:
1. Disable memory balloon device for a VM in Engine.
2. Run the VM from Engine and wait until it's up.
3. Run `systemctl restart libvirtd' on the host running the VM.
4. Wait for a while.

Actual results:

The VM is reported as paused in Engine.

Expected results:

The VM remains reported as up in Engine.

Additional info:

The problem is that Vdsm fails in Balloon.update_device_info due to a missing device alias in the domain XML obtained from libvirt.

Comment 1 Israel Pinto 2016-06-21 09:39:30 UTC

Verify with:
RHEVM Version: 3.6.7.4-0.1.el6
Host:
OS Version: RHEL - 7.2 - 9.el7_2.1
Kernel Version: 3.10.0 - 327.22.2.el7.x86_64
KVM Version: 2.3.0 - 31.el7_2.16
LIBVIRT Version: libvirt-1.2.17-13.el7_2.5
VDSM Version: vdsm-4.18.999-106.git558fe3a.el7.centos

Steps to Reproduce:
1. Disable memory balloon device for a VM in Engine.
2. Run the VM from Engine and wait until it's up.
3. Run `systemctl restart libvirtd' on the host running the VM.
4. Wait for a while.
Result:
VM is reported as UP all the restart process.