Bug 1297414 - vmchannel thread consumes 100% of CPU
Summary: vmchannel thread consumes 100% of CPU
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ovirt-3.5.8
: ---
Assignee: Vinzenz Feenstra [evilissimo]
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On: 1226911
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-11 13:08 UTC by rhev-integ
Modified: 2019-10-10 10:51 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1226911
Environment:
Last Closed: 2016-02-29 14:49:55 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0317 0 normal SHIPPED_LIVE vdsm 3.5.8 - bug fix and enhancement update 2016-02-29 19:48:53 UTC
oVirt gerrit 51521 0 master MERGED virt: Correct epoll unregistration usage in vmchannels 2016-01-14 10:43:20 UTC
oVirt gerrit 51841 0 ovirt-3.5 MERGED virt: Correct epoll unregistration usage in vmchannels 2016-01-15 15:53:19 UTC
oVirt gerrit 51878 0 ovirt-3.5 MERGED virt: Set cloexec flag on channel sockets 2016-01-15 15:31:22 UTC

Comment 3 Israel Pinto 2016-01-28 15:42:50 UTC 
verify with:
RHEVM: 3.5.7-0.1.el6ev 
vdsm: vdsm-4.16.33-1.el6ev
libvirt: libvirt-0.10.2-54.el6_7.2

Steps to Reproduce:
1. Two host environment. Put one host to maintenance mode (second host doesn't have enough resources to run all VMs so migration(s) is failed)
2. Wait until migration is failed
3. Power the VM(s) off
4. Activate the host

Actual results:
The VM is down, Host is up and running.
No 'vmchannels' print in vdsm log.
Check PASS
Comment 5 errata-xmlrpc 2016-02-29 14:49:55 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0317.html
Note You need to log in before you can comment on or make changes to this bug.