Sorry, I must've overlooked this email - I'll try reproduce and open a new bz. On Fri, Jan 24, 2014 at 4:13 AM, Doron Fediuck <dfediuck@redhat.com> wrote:
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Andrew Lau" <andrew@andrewklau.com> Cc: "users" <users@ovirt.org> Sent: Monday, January 20, 2014 2:33:08 PM Subject: Re: [Users] Issues starting hosted engine VM
On 01/20/2014 02:27 PM, Andrew Lau wrote:
On Mon, Jan 20, 2014 at 11:19 PM, Itamar Heim <iheim@redhat.com <mailto:iheim@redhat.com>>wrote:
On 01/20/2014 01:19 PM, Andrew Lau wrote:
Hi,
That bug seems to be private :(
I'm interested also to hear about this feature, as with 3.3.2 I had my gluster vms go into paused state quite a few times and they actually couldn't be resumed at all, they needed to be forced off and back on.
did the storage domain go back to up and they remained down?
Yup, the storage domain went down and when it came back up the VMs remained paused.
please open a bug with repro steps in that case and attach logs. thanks
On Mon, Jan 20, 2014 at 10:13 PM, Dafna Ron <dron@redhat.com <mailto:dron@redhat.com> <mailto:dron@redhat.com <mailto:dron@redhat.com>>> wrote:
interesting... :) so this is now configurable... what happens if qemu fails to start the vm (this happens sometimes - mostly on file type storage). do we have a re-try or a specific error telling the use that the activation failed and
manual
intervention is required?
Andrew, did you manage to open a bug for the resume issue?