Bug 1389090 - VM's transition to not-responding state then back to UP state.
Summary: VM's transition to not-responding state then back to UP state.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.6.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan Kenigsberg
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 20:25 UTC by Bimal Chollera
Modified: 2019-12-16 07:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-02 08:28:24 UTC
oVirt Team: Virt
Target Upstream Version:


Attachments (Terms of Use)

Description Bimal Chollera 2016-10-26 20:25:25 UTC
Description of problem:

VM's transition to not-responding state then back to UP state.
This problem is seen on end-user system when taking VM snapshots.
The VM's it-self doesn't have any problems and continue to operate.

The VDSM logs contains "monitor become unresponsive (command timeout, age=89.0200000005)" messages for the VM's.

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

rhevm-3.6.9.2-0.1.el6.noarch 
vdsm-4.17.35-1.el7ev.noarch
libvirt-daemon-1.2.17-13.el7_2.5.x86_64 

How reproducible:
1.  100% reproducible on end-user system.  

Steps to Reproduce:

1.  Take and snapshot of the VM and observe the VM's momentarily transition to not responding state then back to Up state.

2.
3.

Actual results:

VM's momentarily transition to not responding state then back to Up state.

Expected results:

VM's shouldn't transition to not responding state.  

Additional info:

Comment 4 Michal Skrivanek 2016-10-27 05:58:34 UTC
Francesco, os it the same as the race on shutdown?

Comment 5 Yaniv Kaul 2016-10-27 07:16:33 UTC
(In reply to Michal Skrivanek from comment #4)
> Francesco, os it the same as the race on shutdown?

I doubt that - just by looking at the logs - if it takes you >1m to take a snapshot, something's wrong (storage-side performance?). I'd look at VDSM log for storage issues.


Note You need to log in before you can comment on or make changes to this bug.