From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 86FE91FF179 for ; Wed, 12 Nov 2025 10:58:21 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0C49D1CF30; Wed, 12 Nov 2025 10:59:02 +0100 (CET) Message-ID: Date: Wed, 12 Nov 2025 10:58:58 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Kaonashi , Proxmox VE user list References: <19590067-d4c0-4cb2-b7a3-31eeab66d412@bakemono.nl> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <19590067-d4c0-4cb2-b7a3-31eeab66d412@bakemono.nl> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1762941513517 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.024 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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] container live migration (like OpenVZ) 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: , Reply-To: Proxmox VE user list Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" Hi, Am 07.11.25 um 19:02 schrieb Kaonashi: > OpenVZ, the successor of lxc, had container live migration. Which only worked for limited setups and use cases. > CloudLinux with an OpenVZ kernel, still has it I believe. OpenVZ is EOL since a long time, and it's approach heavily modified the upstream kernel and made following upstream hard. We most certainly do not want to add that big known tech debt again after being able to provide a modern CT stack using native Linux technology. I could not find anything to CloudLinux and CT live-migration, albeit the might use Virtuozo kernel (successor of openVZ), but nowadays that also uses LXC IIRC. > When will live migration on ProxMox for lxc containers re-appear? Not anytime soon, and it's not unlikely that this will never come for LXC. Use VMs when you need live-migration anytime soon. Background: Containers are to intertwined with the kernel, and while CRIU tries to provide a solution for serializing a set of processes (like those of the CT) to a file and be able to load it again, it's quite limited and that's not to say the CRIU devs don't try, it's an extremely hard problem. And that gets even harder due to the kernel continuously changing, gaining new features and changing how the internal state looks like for existing ones; i.e., even if one would have answers for every CRIU problem, it still would need a ton of maintenance work to tag along. Virtual machines OTOH have a clear state and memory boundary designed with these requirement in mind, thus it's relatively (!) easy to do there regards, Thomas _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user