[ovirt-users] Re: VM --- is not responding.

2019-08-26 Thread Edoardo Mazza
...I saw the logs, the storage of domain is glusterfs but I didn't find any error in gluster's log when the vm became unresponsive, it would be very strange if the problem was in the storage controller, may be that the vm is too used? thanks Edoardo Il giorno mer 14 ago 2019 alle ore 18:47

[ovirt-users] Re: VM --- is not responding.

2019-08-14 Thread Strahil
Hm... It was supposes to show controller status. Maybe the hpssacli you have is not supporting your raid cards.Check for newer version on HPE's support page. Best Regards, Strahil Nikolov Best Regards, Strahil NikolovOn Aug 14, 2019 11:40, Edoardo Mazza wrote: > > I installed

[ovirt-users] Re: VM --- is not responding.

2019-08-14 Thread Edoardo Mazza
I installed hpssacli-2.40-13.0.x86_64.rpm and the result of "hpssacli ctrl all show status" is: Error: No controllers detected. Possible causes:. The s.o. run on sd cards and the vm runs on array on traditional disk thanks Edoardo Il giorno lun 12 ago 2019 alle ore 05:59 Strahil ha scritto:

[ovirt-users] Re: VM --- is not responding.

2019-08-11 Thread Strahil
Would you check the health status of the controllers : hpssacli ctrl all show status Best Regards, Strahil NikolovOn Aug 11, 2019 09:55, Edoardo Mazza wrote: > > The hosts are 3 ProLiant DL380 Gen10, 2 hosts with HPE Smart Array P816i-a SR > Gen10 like controller and the other host with > HPE

[ovirt-users] Re: VM --- is not responding.

2019-08-11 Thread Edoardo Mazza
The hosts are 3 ProLiant DL380 Gen10, 2 hosts with HPE Smart Array P816i-a SR Gen10 like controller and the other host with HPE Smart Array P408i-a SR Gen10. The storage for ovirt enviroment is gluster and the last host is the arbiter in the gluster enviroment. The S.M.A.R.T. healt status is ok

[ovirt-users] Re: VM --- is not responding.

2019-08-08 Thread Sandro Bonazzola
Il giorno gio 8 ago 2019 alle ore 11:19 Edoardo Mazza ha scritto: > Hi all, > It is more days that for same vm I received this error, but I don't > underdand why. > The traffic of the virtual machine is not excessive, cpu and ram to, but > for few minutes the vm is not responding. and in the