From: Kaonashi via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Kaonashi <kaonashi@bakemono.nl>
Subject: [PVE-User] container live migration (like OpenVZ)
Date: Fri, 7 Nov 2025 19:02:20 +0100 [thread overview]
Message-ID: <mailman.797.1762538582.362.pve-user@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 2147 bytes --]
From: Kaonashi <kaonashi@bakemono.nl>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: container live migration (like OpenVZ)
Date: Fri, 7 Nov 2025 19:02:20 +0100
Message-ID: <19590067-d4c0-4cb2-b7a3-31eeab66d412@bakemono.nl>
Hi all,
OpenVZ, the successor of lxc, had container live migration.
CloudLinux with an OpenVZ kernel, still has it I believe.
When will live migration on ProxMox for lxc containers re-appear?
--
Best regards,
Kaonashi
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next reply other threads:[~2025-11-07 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 18:02 Kaonashi via pve-user [this message]
[not found] <19590067-d4c0-4cb2-b7a3-31eeab66d412@bakemono.nl>
2025-11-12 9:58 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.797.1762538582.362.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=kaonashi@bakemono.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox