[ovirt-devel] VM won't start because of -incoming flag after upgrading to alpha-2
This is a multi-part message in MIME format.
--------------040500060504070207030504
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
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-07-07T07:39:27.215681Z qemu-kvm: load of migration failed:
Invalid argument
The reason is that Engine was starting the VM with the -incoming flag
(for "incoming migrations").
1) Why did engine enable the -incoming flag?
VM was configured with "Allow manual migration only".
Maybe this ocurred because I set the host in maintenance mode before
upgrading.
2) How can I clean the -incoming flag in oVirt?
3) Note that the "domain is tainted" error was also freezing the monitor
socket between libvirt and vdsm, requiring a libvirtd + vdsmd restart.
--------------040500060504070207030504
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
After upgrading from alpha-1 to alpha-2 and restarting services, a
VM won't start because of the following qemu error:<br>
<blockquote>Domain id=5 is tainted: hook-script<br>
2015-07-07T07:39:27.215579Z qemu-kvm: Unknown migration flags: 0<br>
qemu: warning: error while loading state section id 2<br>
2015-07-07T07:39:27.215681Z qemu-kvm: load of migration failed:
Invalid argument<br>
</blockquote>
The reason is that Engine was starting the VM with the -incoming
flag (for "incoming migrations").<br>
<br>
1) Why did engine enable the -incoming flag?<br>
VM was configured with "Allow manual migration only".<br>
Maybe this ocurred because I set the host in maintenance mode before
upgrading.<br>
<br>
2) How can I clean the -incoming flag in oVirt?<br>
<br>
3) Note that the "domain is tainted" error was also freezing the
monitor socket between libvirt and vdsm, requiring a libvirtd +
vdsmd restart.<br>
<br>
</body>
</html>
--------------040500060504070207030504--
Attachments:
- attachment.bin (multipart/alternative — 2.3 KB)