I was more interested in how the score process would be calculated, the vm-status option considered the VM in a bad state.
I left it for a few minutes and nothing seemed to have changed, I think it relates to hosted engine as virsh requires authentication. Should I still open a bz?
Cheers,
Andrew.On Jan 20, 2014 7:48 PM, "Dafna Ron" <dron@redhat.com> wrote:I am not sure this is a hosted engine question as much as a qemu question.
qemu-kvm will not support auto start of vm's after EIO because of remote possibility of corruption.
On 01/20/2014 05:46 AM, Andrew Lau wrote:
Hi,
Quick question, in the scenario eg. the NFS server becomes unreachable and the hosted-engine goes into a paused state. Will other hosts attempt to bring it back up? Should there be a command eg. hosted-engine --vm-resume ?
When this happened, I manually forced it to resume using virsh
On Sun, Jan 19, 2014 at 7:21 PM, Yedidyah Bar David <didi@redhat.com <mailto:didi@redhat.com>> wrote:
Thanks a lot for your efforts and the report!
-- Didi
------------------------------------------------------------------------
*From: *"Andrew Lau" <andrew@andrewklau.com
<mailto:andrew@andrewklau.com>>
*To: *"users" <users@ovirt.org <mailto:users@ovirt.org>>
*Sent: *Saturday, January 18, 2014 3:20:22 PM
*Subject: *Re: [Users] Issues starting hosted engine VM
I believe I found the issue and have reported it here
https://bugzilla.redhat.com/show_bug.cgi?id=1055059
On Sat, Jan 18, 2014 at 11:33 PM, Andrew Lau
<andrew@andrewklau.com <mailto:andrew@andrewklau.com>> wrote:
The interesting thing - trying it with the paused option
vdsm seems to create the VM
hosted-engine --vm-start-paused
vdsm.log http://www.fpaste.org/69604/13900482/
But I'm not sure how to then proceed to "resume" it.
On Sat, Jan 18, 2014 at 10:23 PM, Andrew Lau
<andrew@andrewklau.com <mailto:andrew@andrewklau.com>> wrote:
Hi,
With the great help from sbonazzo, I managed to step
past the initial bug with the hosted-engine-setup but
appear to have run into another show stopper.
I ran through the install process successfully up to
the stage where it completed and the engine VM was to
be shutdown. (The engine has already been installed on
the VM and the host has been connected to the engine).
The issue starts here that the host finds itself not
able to start the VM up again.
VDSM Logs: http://www.fpaste.org/69592/00427141/
ovirt-hosted-engine-ha agent.log
http://www.fpaste.org/69595/43609139/
It seems to keep failing to start the VM.. when I
restart the agent I can see the score drop to 0 after
3 boot attempts. The interesting thing seems to be in
the VDSM Logs "'Virtual machine does not exist',
'code': 1}}"
I'm not sure where else to look. Suggestions?
Cheers,
Andrew
_______________________________________________
Users mailing list
Users@ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
-- Didi
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Dafna Ron