Hi,
On Fri, Sep 30, 2016 at 9:27 PM, Yaniv Kaul wrote:
>
> > btw, b
> > oth of the environments were RHEV-H based RHEV 3.5 clusters, and both
> we were busy systems, so restarting vdsm service took quite a long time.
> I'm guessing this might be a factor.
>
> That indeed
On Aug 22, 2016 10:57 PM, "Ekin Meroğlu" wrote:
>
> Hi Yaniv,
>
>> On Sun, Aug 7, 2016 at 9:37 PM, Ekin Meroğlu
wrote:
>>>
>>> Hi,
>>>
>>> Just a reminder, if you have power management configured, first turn
that off for the host - when you
Hi Yaniv,
Just a reminder, can you give us a pointer? Red Hat Support just asked us
to disable PM before restarting vdsm again.
Thanks & Best regards,
On Mon, Aug 22, 2016 at 10:57 PM, Ekin Meroğlu
wrote:
> Hi Yaniv,
>
> On Sun, Aug 7, 2016 at 9:37 PM, Ekin Meroğlu
Hi Yaniv,
On Sun, Aug 7, 2016 at 9:37 PM, Ekin Meroğlu
> wrote:
>
>> Hi,
>>
>> Just a reminder, if you have power management configured, first turn that
>> off for the host - when you restart vdsmd with the power management
>> configured, engine finds it not responding
> On 09 Aug 2016, at 19:14, Nicolás wrote:
>
> Hi,
>
> It worked (thanks Ekin, I'd probably had not turned it off and it would
> indeed been restarted), restarting libvirtd and vdsmd made all machines set
> their status to up. Seems the cuprit is libvirtd in this case, as
Hi,
It worked (thanks Ekin, I'd probably had not turned it off and it would
indeed been restarted), restarting libvirtd and vdsmd made all machines
set their status to up. Seems the cuprit is libvirtd in this case, as I
could see some errors in the log. I'm attaching the log FWIW.
Thanks.
On Thu, Aug 4, 2016 at 6:10 PM, Nicolás wrote:
>
>
> El 04/08/16 a las 15:25, Arik Hadas escribió:
>
>>
>> - Original Message -
>>
>>> El 2016-08-04 08:24, Arik Hadas escribió:
>>>
- Original Message -
>
> El 04/08/16 a las 07:18, Arik Hadas
El 04/08/16 a las 15:25, Arik Hadas escribió:
- Original Message -
El 2016-08-04 08:24, Arik Hadas escribió:
- Original Message -
El 04/08/16 a las 07:18, Arik Hadas escribió:
- Original Message -
Hi,
We're running oVirt 4.0.1 and today I found out that one of
- Original Message -
>
>
> El 04/08/16 a las 07:18, Arik Hadas escribió:
> > - Original Message -
> >> Hi,
> >>
> >> We're running oVirt 4.0.1 and today I found out that one of our hosts
> >> has all its VMs in an unknown state. I actually don't know how (and
> >> when) did
El 04/08/16 a las 07:18, Arik Hadas escribió:
- Original Message -
Hi,
We're running oVirt 4.0.1 and today I found out that one of our hosts
has all its VMs in an unknown state. I actually don't know how (and
when) did this happen, but I'd like to restore service possibly without
- Original Message -
> Hi,
>
> We're running oVirt 4.0.1 and today I found out that one of our hosts
> has all its VMs in an unknown state. I actually don't know how (and
> when) did this happen, but I'd like to restore service possibly without
> turning off these machines. The host is
Hi,
We're running oVirt 4.0.1 and today I found out that one of our hosts
has all its VMs in an unknown state. I actually don't know how (and
when) did this happen, but I'd like to restore service possibly without
turning off these machines. The host is up, the VMs are up, 'qemu'
process
12 matches
Mail list logo