, January 8, 2015 7:03:55 PM
Subject: RE: [ovirt-users] VM failover with ovirt3.5
Thanks for the advice.
For
2) If something happen with host where HA vm run(network problem, power
outage), vm dropped to unknown state, and if you want from engine to start
this vm on another host, you need click
Subject: Re: [ovirt-users] VM failover with ovirt3.5
On 01/06/2015 09:34 AM, Artyom Lukianov wrote:
Case 1:
In vdsm.log I can see this one:
Thread-674407::ERROR::2015-01-05 12:09:43,264::migration::259::vm.Vm::(run)
vmId=`0d3adb5c-0960-483c-9d73-5e256a519f2f`::Failed to migrate
Traceback (most
Moskovcak; Yedidyah
Bar David; Sandro Bonazzola
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Case 1:
In vdsm.log I can see this one:
Thread-674407::ERROR::2015-01-05 12:09:43,264::migration::259::vm.Vm::(run)
vmId=`0d3adb5c-0960-483c-9d73-5e256a519f2f`::Failed to migrate
Traceback (most recent
8:46 AM
To: Yue, Cong
Cc: cong yue; stira...@redhat.com; users@ovirt.org; Jiri Moskovcak; Yedidyah
Bar David; Sandro Bonazzola
Subject: Re: [ovirt-users] VM failover with ovirt3.5
So, behavior for not HE HA vm is:
1) If vm crash(from some reason) it restarted automatically on another host
:38:08 PM
Subject: RE: [ovirt-users] VM failover with ovirt3.5
I collected the agent.log and vdsm.log in 2 cases.
Case1 HE VM failover trail
What I did
1, make all host be engine up
2, set host1 be with local maintenance mode. In host1, there is HE VM.
3, Then HE VM is trying to migrate, but finally
cong_...@alliedtelesis.com
To: Artyom Lukianov aluki...@redhat.com
Cc: cong yue yuecong1...@gmail.com, stira...@redhat.com, users@ovirt.org
Sent: Monday, January 5, 2015 7:38:08 PM
Subject: RE: [ovirt-users] VM failover with ovirt3.5
I collected the agent.log and vdsm.log in 2 cases.
Case1 HE VM
, January 1, 2015 2:32:18 AM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Thanks for the advice. I applied the patch for clientIF.py as
- port = config.getint('addresses', 'management_port')
+ port = config.get('addresses', 'management_port')
Now there is no fatal error in beam.log, also
AM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Thanks for the advice. I applied the patch for clientIF.py as
- port = config.getint('addresses', 'management_port')
+ port = config.get('addresses', 'management_port')
Now there is no fatal error in beam.log, also migration can start
and restart vdsm.
- Original Message -
From: cong yue yuecong1...@gmail.com
To: aluki...@redhat.com, stira...@redhat.com, users@ovirt.org
Cc: Cong Yue cong_...@alliedtelesis.com
Sent: Tuesday, December 30, 2014 8:22:47 PM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
The vdsm.log just after
...@redhat.com, stira...@redhat.com, users@ovirt.org
Cc: Cong Yue cong_...@alliedtelesis.com
Sent: Tuesday, December 30, 2014 8:22:47 PM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
The vdsm.log just after I turned the host where HE VM is to local.
In the log, there is some part like
, users@ovirt.org
Sent: Monday, December 29, 2014 7:15:24 AM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Also I change the maintenance mode to local in another host. But also the VM in
this host can not be migrated. The logs are as follows.
[root@compute2-2 ~]# hosted-engine --set
Lukianov aluki...@redhat.commailto:aluki...@redhat.com
Cc: Simone Tiraboschi stira...@redhat.commailto:stira...@redhat.com,
users@ovirt.orgmailto:users@ovirt.org
Sent: Monday, December 29, 2014 7:15:24 AM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Also I change the maintenance mode to local
, users@ovirt.org
Sent: Monday, December 29, 2014 6:30:42 PM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Thanks and the --vm-status log is as follows:
[root@compute2-2 ~]# hosted-engine --vm-status
--== Host 1 status ==--
Status up-to-date : True
Hostname
...@alliedtelesis.com
To: Artyom Lukianov aluki...@redhat.com
Cc: Simone Tiraboschi stira...@redhat.com, users@ovirt.org
Sent: Monday, December 29, 2014 6:30:42 PM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Thanks and the --vm-status log is as follows:
[root@compute2-2 ~]# hosted-engine --vm-status
From: Yue, Cong cong_...@alliedtelesis.com
To: Artyom Lukianov aluki...@redhat.com
Cc: users@ovirt.org users@ovirt.org
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Message-ID: 11a51118-8b03-41fe-8fd0-c81ac8897...@alliedtelesis.com
Content-Type: text/plain; charset=us-ascii
Thanks
, users@ovirt.org
Sent: Monday, December 29, 2014 8:29:04 PM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
I disabled local maintenance mode for all hosts, and then only set the host
where HE VM is there to local maintenance mode. The logs are as follows. During
the migration of HE VM
: Simone Tiraboschi stira...@redhat.com, users@ovirt.org
Sent: Monday, December 29, 2014 7:49:58 PM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Thanks for detailed explanation. Do you mean only HE VM can be failover? I want
to have a try with the VM on any host to check whether VM can
To: Simone Tiraboschi stira...@redhat.com
Cc: users@ovirt.org
Sent: Saturday, December 27, 2014 6:58:32 PM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Hi
I had a try with hosted-engine --set-maintence --mode=local on
compute2-1, which is host 3 in my cluster. From the log, it shows
maintence
...@redhat.com
Cc: users@ovirt.orgmailto:users@ovirt.org
Sent: Saturday, December 27, 2014 6:58:32 PM
Subject: Re: [ovirt-users] VM failover with ovirt3.5
Hi
I had a try with hosted-engine --set-maintence --mode=local on
compute2-1, which is host 3 in my cluster. From the log, it shows
maintence mode
: RE: [ovirt-users] VM failover with ovirt3.5
Thanks for the information. This is the log for my three ovirt nodes.
From the output of hosted-engine --vm-status, it shows the engine state for
my 2nd and 3rd ovirt node is DOWN.
Is this the reason why VM failover not work in my environment
- Original Message -
From: Cong Yue cong_...@alliedtelesis.com
To: Simone Tiraboschi stira...@redhat.com
Cc: users@ovirt.org
Sent: Friday, December 19, 2014 7:22:10 PM
Subject: RE: [ovirt-users] VM failover with ovirt3.5
Thanks for the information. This is the log for my three
- Original Message -
From: Cong Yue cong_...@alliedtelesis.com
To: Simone Tiraboschi stira...@redhat.com
Cc: users@ovirt.org
Sent: Friday, December 19, 2014 9:25:32 PM
Subject: RE: [ovirt-users] VM failover with ovirt3.5
In the documentation of
http://www.ovirt.org
- Original Message -
From: Cong Yue cong_...@alliedtelesis.com
To: users@ovirt.org
Sent: Friday, December 19, 2014 2:14:33 AM
Subject: [ovirt-users] VM failover with ovirt3.5
Hi
In my environment, I have 3 ovirt nodes as one cluster. And on top of host-1,
there is one
@ovirt.org
Subject: Re: [ovirt-users] VM failover with ovirt3.5
- Original Message -
From: Cong Yue cong_...@alliedtelesis.com
To: users@ovirt.org
Sent: Friday, December 19, 2014 2:14:33 AM
Subject: [ovirt-users] VM failover with ovirt3.5
Hi
In my environment, I have 3 ovirt
machines.
Does this mean I need to confirgure all poer management for all ovirt nodes?
Thanks,
Cong
-Original Message-
From: Yue, Cong
Sent: Friday, December 19, 2014 10:22 AM
To: 'Simone Tiraboschi'
Cc: users@ovirt.org
Subject: RE: [ovirt-users] VM failover with ovirt3.5
Thanks
Hi
In my environment, I have 3 ovirt nodes as one cluster. And on top of host-1,
there is one vm to host ovirt engine.
Also I have one external storage for the cluster to use as data domain of
engine and data.
I confirmed live migration works well in my environment.
But it seems very buggy for
26 matches
Mail list logo
