Bug 825972 - VM status turned into "Not Responding" after a while
VM status turned into "Not Responding" after a while
Status: CLOSED DUPLICATE of bug 821468
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm (Show other bugs)
6.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Dan Kenigsberg
Pavel Stehlik
virt
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-29 04:34 EDT by Chao Yang
Modified: 2012-05-29 13:43 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-29 13:43:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
vdsm log in this problematic host (373.17 KB, application/x-bzip2)
2012-05-29 04:34 EDT, Chao Yang
no flags Details

  None (edit)
Description Chao Yang 2012-05-29 04:34:36 EDT
Created attachment 587347 [details]
vdsm log in this problematic host

Description of problem:
I launched some VMs on AMD host using local nfs storage, but after a while, they are all not responding. vdsm log will be attached.

Version-Release number of selected component (if applicable):
vdsm-4.9.6-13.el6.x86_64
libvirt-0.9.10-20.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.294.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Haim 2012-05-29 13:43:04 EDT
I really think its the same issue (just checked attached vdsm.log and monitor response is '-1')

*** This bug has been marked as a duplicate of bug 821468 ***

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