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

Bug 1618755

Summary: VMs not responding
Product: [oVirt] vdsm Reporter: oliver.albl
Component: GeneralAssignee: Roy Golan <rgolan>
Status: CLOSED INSUFFICIENT_DATA QA Contact: mlehrer
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.20.31CC: bugs, christian.grundmann, dfediuck, lsvaty, rgolan, tcarlin
Target Milestone: ---   
Target Release: ---   
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-04-23 10:17:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Scale RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Logfiles (vdsm) none

Description oliver.albl 2018-08-17 13:42:46 UTC 
Created attachment 1476631 [details]
Logfiles (vdsm)

Description of problem:
I run a cluster with 10 hosts for automated testing purposes. I have VMs switching to "Not Responding" when under load.

Version-Release number of selected component (if applicable):
oVirt 4.2.4.5-1.el7
vdsm-4.20.32-1.el7.x86_64

How reproducible:
Generate load on hosts by automatically creating vms, running vm workloads, deleting vms

Steps to Reproduce:
1.
2.
3.

Actual results:
Host reports "VM xxx is not responding" for some VMs
VMs stay in this state.

Expected results:
Automatic tasks (startup, shutdown, ...) should be possible.

Additional info:
Already removed /usr/libexec/vdsm/hooks/after_vm_destroy/50_vhostmd and set [rpc] worker_threads to 16 (see https://bugzilla.redhat.com/show_bug.cgi?id=1600507)
Comment 2 Doron Fediuck 2019-04-23 10:17:40 UTC 
Closing since we just tested this with at least 500 hosts.
If you have more details please share and re-open.