From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 8F78E60E14 for ; Wed, 2 Dec 2020 19:34:43 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7FBB71F809 for ; Wed, 2 Dec 2020 19:34:13 +0100 (CET) Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 40F1C1F7F9 for ; Wed, 2 Dec 2020 19:34:09 +0100 (CET) Received: by mail-wr1-x436.google.com with SMTP id z7so5150059wrn.3 for ; Wed, 02 Dec 2020 10:34:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=odiso-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=8IlXt1kqxxtIo3iCi4WDlxFtiriZwEHUhLIK9XqvF+E=; b=ICk2Hg0zd+pLGsxDzUVItvVYtZ5/Uar0Ude7elbs5dTRBvA0+6eBpKRqllnyChmcOa BK05qR2rt3uaNgYukL+69RP9C7SYHjqaiDbwohlH6HN+sUp1CCiOS2+WGzO2qIIgydCJ ZRDIMemi0OOUDxqwU+66TpwIW/x+xMSJIVu6vDxPEqrgDCwT/iDBlXNVeiw/BdL6A3JA pADTNJ2fb8b4uFGuoIjxIwulWChqQyIyA2wI6iKkKcIPKO+u5mKqXnuq/uFYywYP0Uua DddA44ik4qYvrD9izkKWoFOvEJmZNpxezX6dO7ShHeoVH3kgf5i7FQRu952Yyr3xhFDJ mk3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=8IlXt1kqxxtIo3iCi4WDlxFtiriZwEHUhLIK9XqvF+E=; b=iqvTF3oS1qcMEhYpBfJDOaa09vpEF/0XGGdhw3KZpH2asyysc2SqVYF/qSn+PBKej+ z0zvFnYUlhi4YEx9zwwCuYRyGSaVVK8xeR08730/sMO3LzlqThSlUmzAvaPVQKKmcfiR y4hWEjF7w/5ah5jneVqNZgFm862mqfiJANmx7GWsgboriIhu0WuH/EqJi0j/M0Xw+hFT 9Tm7T78+//ypXmpc3tItweYuaTPiouA0x/R0DD4HPuablJDetBVjyoTNYi3HYgGYh1FQ 1ZZ5SwFRSRPw++POcuwEGZALN0C/3L8sTTm8e2fE0SFU/UgBWDcQc7pNN2cgVCxEChvE Zk7A== X-Gm-Message-State: AOAM532v/lasEJDMj67dw3E1lYWnAo4WFGbiGDGoQXF/usK5EHwq9o/0 LLuTknIsNCp0G+uRL4IvQnhx1v7aZGEIF9rDIgI= X-Google-Smtp-Source: ABdhPJz//m2mNaAPZeiE2jPU3SxLT03W/XUQo9uu02rl2XeA5X6v2w2UI1r5+sZiXSwscC4r95r63Q== X-Received: by 2002:adf:fe82:: with SMTP id l2mr4955084wrr.232.1606934042573; Wed, 02 Dec 2020 10:34:02 -0800 (PST) Received: from ?IPv6:2a0a:1580:0:1::100c? (ovpn1.odiso.net. [2a0a:1580:2000::3f]) by smtp.gmail.com with ESMTPSA id b3sm3006878wrp.57.2020.12.02.10.34.00 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 02 Dec 2020 10:34:01 -0800 (PST) To: pve-user@lists.proxmox.com References: <20201202171102.03c7f2e2@batzmaru.gol.ad.jp> From: alexandre derumier Message-ID: <92cc18a9-7e17-0f4d-d63c-438962810f9b@odiso.com> Date: Wed, 2 Dec 2020 19:33:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 In-Reply-To: <20201202171102.03c7f2e2@batzmaru.gol.ad.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature NICE_REPLY_A -0.001 Looks like a legit reply (A) RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Live VM migration 6.3 to 6.2 fails X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2020 18:34:43 -0000 On 02/12/2020 09:11, Christian Balzer wrote: > Hello, > > yes I know that migrating back to an older version is not guaranteed but > I'm rather confused as to why this happens. > > Firstly this, more details below: > --- > 2020-12-02 16:34:08 start migrate command to tcp:10.0.0.11:60000 > 2020-12-02 16:34:09 migration status error: failed > 2020-12-02 16:34:09 ERROR: online migrate failure - aborting > 2020-12-02 16:34:09 aborting phase 2 - cleanup resources > 2020-12-02 16:34:09 migrate_cancel > 2020-12-02 16:34:11 ERROR: migration finished with problems (duration 00:00:08) > TASK ERROR: migration problems > --- > > That's all I get, where would one find the exact issue? > > Now for the details, in the previous minor upgrade we saw a similar issue, > but that only affected VMs which had been created on an upgraded node, old > ones were fine to move in both ways. > OK, that was because of new features int he VM definition not present on > the old version, understandable. > > With this one on a (more frequently updated) test cluster 6.3 to 6.2 > migrations also works, the test cluster old nodes are at > pve-manager (6.2-12), the one with issues are pve-manager (6.2-6). > I however see nothing in the changelogs which would explain this difference. > > In general being able to live migrate back to a node with the previous > version is a very desirable situation, since if there are issues/bugs (on > the VM level) with the new version there no longer is an impact free way > of reverting if this functionality is not present. > > Regards, > > Christian you can't migrate from a newer qemu version to an older qemu version, if the vm start has been started first on the newer qemu version. if the vm was started first on an older qemu version, you can live migrate it to a newer qemu version and migrate it again to older qemu version. (until you stop/start it again on a newer qemu version). This is because, when the vm is started, it's keeping internally the qemu machine version of the current qemu process version. The only thing to keep in mind, try to keep all yours nodes at same version. Proxmox is a rolling release, you can have qemu upgrade between 2 releases.