On 07-07-2015 8:36, Francesco Romani wrote:
----- Original Message -----
> From: "Christopher Pereira" <kripper(a)imatronix.cl>
> To: "Francesco Romani" <fromani(a)redhat.com>
> Cc: "Doron Fediuck" <dfediuck(a)redhat.com>, devel(a)ovirt.org, "Roy
Golan" <rgolan(a)redhat.com>
> Sent: Tuesday, July 7, 2015 1:32:40 PM
> Subject: Re: [ovirt-devel] VM won't start because of -incoming flag after
upgrading to alpha-2
>
>
> On 07-07-2015 8:16, Francesco Romani wrote:
>> This means the VM is "migrating from file", aka resuming after a
>> suspension.
>> Any chance the VM was suspended while running some QEMU version and resumed
>> using a different QEMU version?
> Yes, the VM was suspended before updating and restarting services.
> It probably failed the first time I tried to resume and by some reason,
> the memory snapshot is not available any more.
OK, then the scenarios are the following:
If you suspended on qemu-kvm-ev version X and resumed on qemu-kvm-ev version Y (Y >
X),
then it should be supported, so please file a bug against qemu-kvm-ev
Same goes for plain qemu.
but if you suspended on qemu and resumed on qemu-kvm-ev, or vice versa, then I'm not
sure
this flow is supported (AFAIR, it isn't).
'qemu-kvm-ev-2.1.2-23.el7_1.3.1.x86_64' was being used for both
suspending and resuming.
BZ created here:
https://bugzilla.redhat.com/show_bug.cgi?id=1240649