On 07-07-2015 8:36, Francesco Romani wrote:
- Original Message -
From: "Christopher Pereira"
To: "Francesco Romani"
Cc: "Doron Fediuck" , devel@ovirt.org, "Roy Golan"
Sent: Tuesday, July 7, 2015 1:32:40 PM
Subject: Re: [ovirt-devel] VM won't start because of -incoming flag after
upg
- Original Message -
> From: "Christopher Pereira"
> To: "Francesco Romani"
> Cc: "Doron Fediuck" , devel@ovirt.org, "Roy Golan"
>
> 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-0
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 service
- Original Message -
> From: "Christopher Pereira"
> To: "Doron Fediuck" , "Francesco Romani"
>
> Cc: devel@ovirt.org, "Roy Golan"
> Sent: Tuesday, July 7, 2015 12:07:20 PM
> Subject: Re: [ovirt-devel] VM won't start because of -incoming flag after
> upgrading to alpha-2
>
>
> On 07-
On 07-07-2015 6:59, Doron Fediuck wrote:
On 07/07/15 12:50, Christopher Pereira wrote:
Well, something is triggered it.
I will send you the logs right now.
According to libvirt docs, this is an internal flag, which is not
exposed to the user-
http://wiki.libvirt.org/page/QEMUSwitchToLibvirt
On 07/07/15 12:50, Christopher Pereira wrote:
>
> On 07-07-2015 6:04, Francesco Romani wrote:
>> It should not, it should be added by VDSM only when it creates a
>> migration destination VM/
> Well, something is triggered it.
> I will send you the logs right now.
>
According to libvirt docs, th
On 07-07-2015 6:04, Francesco Romani wrote:
It should not, it should be added by VDSM only when it creates a
migration destination VM/
Well, something is triggered it.
I will send you the logs right now.
___
Devel mailing list
Devel@ovirt.org
http://
- Original Message -
> From: "Christopher Pereira"
> To: devel@ovirt.org
> Sent: Tuesday, July 7, 2015 10:22:20 AM
> Subject: [ovirt-devel] VM won't start because of -incoming flag after
> upgrading to alpha-2
>
> Hi,
>
> After upgrading from alpha-1 to alpha-2 and restarting services,
Hi,
After upgrading from alpha-1 to alpha-2 and restarting services, a VM
won't start because of the following qemu error:
Domain id=5 is tainted: hook-script
2015-07-07T07:39:27.215579Z qemu-kvm: Unknown migration flags: 0
qemu: warning: error while loading state section id 2
2015
