Re: [ovirt-users] Live migration fails

2016-04-14 Thread Charles Tassell
users can better diagnose the problem. On 16-04-14 01:00 PM, users-requ...@ovirt.org wrote: Date: Thu, 14 Apr 2016 16:35:34 +0200 From: Sandro Bonazzola <sbona...@redhat.com> To: Nick Vercampt <nick.verca...@gmail.com> Cc: users <users@ovirt.org> Subject: Re: [ovirt-users] Li

Re: [ovirt-users] Live migration fails

2016-04-14 Thread Sandro Bonazzola
On Thu, Apr 14, 2016 at 2:14 PM, Nick Vercampt wrote: > Dear Sirs > > I'm writing to ask a question about the live migration on my oVirt setup. > > I'm currently running oVirt 3.6 on a virtual test enviroment with 1 > default cluster (2 hosts, CentOS 7) and 1 Gluster

[ovirt-users] Live migration fails

2016-04-14 Thread Nick Vercampt
Dear Sirs I'm writing to ask a question about the live migration on my oVirt setup. I'm currently running oVirt 3.6 on a virtual test enviroment with 1 default cluster (2 hosts, CentOS 7) and 1 Gluster enabled cluster (with 2 virtual storage nodes, also CentOS7). My datacenter has a shared

[ovirt-users] Live migration fails - domain not found -

2015-03-18 Thread Markus Stockhausen
Hi, although we already upgraded several hypervisor nodes to Ovirt 3.5.1 the newest upgrade has left the host in a very strang state. We did: - Host was removed from cluster - Ovirt 3.5 repo was activated on host - Host was reinstalled from enging And we got: - A host that is active and looks

Re: [ovirt-users] Live migration fails - domain not found -

2015-03-18 Thread Markus Stockhausen
Von: Paul Heinlein [heinl...@madboa.com] Gesendet: Mittwoch, 18. März 2015 18:43 An: Markus Stockhausen Cc: Users@ovirt.org Betreff: Re: [ovirt-users] Live migration fails - domain not found - On Wed, 18 Mar 2015, Markus Stockhausen wrote: although we already upgraded several

Re: [ovirt-users] Live migration fails - domain not found -

2015-03-18 Thread Paul Heinlein
On Wed, 18 Mar 2015, Markus Stockhausen wrote: although we already upgraded several hypervisor nodes to Ovirt 3.5.1 the newest upgrade has left the host in a very strang state. We did: - Host was removed from cluster - Ovirt 3.5 repo was activated on host - Host was reinstalled from enging