Every time I try to create a Data / iSCSI Storage Domain, I receive an "Error
while executing action New SAN Storage Domain: Cannot zero out volume" error.
iscsid does login to the node, and the volumes appear to have been created.
However, I cannot use it to create or import a Data / iSCSI sto
On Fri, Oct 23, 2015 at 6:10 PM, Simone Tiraboschi
wrote:
>
>
>>
>> Probably inside the [unit] section I should add
>> After=nfs-server.service
>>
>>
> Ok, I understood.
> You are right: the broker was failing cause the NFS storage was not ready
> cause it was served in loopback and there isn't a
On Fri, Oct 23, 2015 at 5:55 PM, Gianluca Cecchi
wrote:
> On Fri, Oct 23, 2015 at 5:05 PM, Simone Tiraboschi
> wrote:
>
>>
>>>
>> OK, can you please try again the whole reboot procedure just to ensure
>> that it was just a temporary NFS glitch?
>>
>
>
> It seems reproducible.
>
> This time I was
On Fri, Oct 23, 2015 at 5:05 PM, Simone Tiraboschi
wrote:
>
>>
> OK, can you please try again the whole reboot procedure just to ensure
> that it was just a temporary NFS glitch?
>
It seems reproducible.
This time I was able to shutdown the hypervisor without manual power off.
Only strange thi
On Fri, Oct 23, 2015 at 4:56 PM, Gianluca Cecchi
wrote:
> On Fri, Oct 23, 2015 at 4:42 PM, Simone Tiraboschi
> wrote:
>
>>
>>
>>
>> Are ovirt-ha-agent and ovirt-ha-broker up and running?
>> Can you please try to restart them via systemd?
>>
>>
>> In the mean time I found inside the logs they fai
On Fri, Oct 23, 2015 at 4:42 PM, Simone Tiraboschi
wrote:
>
>
>
> Are ovirt-ha-agent and ovirt-ha-broker up and running?
> Can you please try to restart them via systemd?
>
>
> In the mean time I found inside the logs they failed to start.
I found in broker log the message
Thread-1730::ERROR::20
Not an option unfortunately. The system is a production one and we don't
have spare equipment to test that on.
On Fri, Oct 23, 2015, 12:47 AM Giorgio Bersano
wrote:
> Hi Michael,
> if you have the possibility to test with
> kernel-2.6.32-504.16.2.el6.x86_64 and
> kernel-2.6.32-504.23.4.el6.x86_6
Using ovirt-node EL7 we’ve been able to live merge since 3.5.3 without any
issues.
-Patrick
> On Oct 23, 2015, at 12:24 AM, Christopher Cox wrote:
>
> On 10/22/2015 10:46 PM, Indunil Jayasooriya wrote:
> ...
>>
>> Hmm,
>>
>> *How to list the sanphot?
>> *
>> *how to backup the VM with snaps
On Fri, Oct 23, 2015 at 3:57 PM, Gianluca Cecchi
wrote:
> On Thu, Oct 22, 2015 at 5:38 PM, Simone Tiraboschi
> wrote:
>
>>
>>
>>> In case I want to setup a single host with self hosted engine, could I
>>> configure on hypervisor
>>> a) one NFS share for sh engine
>>> b) one NFS share for ISO DOM
On Thu, Oct 22, 2015 at 5:38 PM, Simone Tiraboschi
wrote:
>
>
>> In case I want to setup a single host with self hosted engine, could I
>> configure on hypervisor
>> a) one NFS share for sh engine
>> b) one NFS share for ISO DOMAIN
>> c) a local filesystem to be used to create then a local POSIX
Hi Dan,
I want to monitor my oVirt infrastructure with Zabbix. I found a zabbix
template , but it needs to modifiy libirtd.conf to enable libvirt-snmp to
access VM informations (https://github.com/jensdepuydt/zabbix-ovirt).
Kevin
- Mail original -
> De
Hi Michael,
if you have the possibility to test with
kernel-2.6.32-504.16.2.el6.x86_64 and
kernel-2.6.32-504.23.4.el6.x86_64 please do it.
I'm expecting that 2.6.32-504.16.2.el6 is the latest correctly working
kernel. Please tell us if this is your case.
There are clear signs of misbehaviours due
12 matches
Mail list logo
