From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server] blockdev: add NBD: fix handling of IPv6 host to unbreak TCP disk live migration
Date: Sat, 29 Nov 2025 23:49:00 +0100 [thread overview]
Message-ID: <176445653896.1120579.14851558686707660989.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251124122223.358353-1-f.ebner@proxmox.com>
On Mon, 24 Nov 2025 13:21:51 +0100, Fiona Ebner wrote:
> As reported in the community forum [0], live disk migration using
> migration type 'insecure' would fail when the target is an IPv6 host.
> When passing the IPv6 address to QMP, the surrounding square brackets
> need to be removed first.
>
> [0]: https://forum.proxmox.com/threads/176727/
>
> [...]
Applied, thanks!
[1/1] blockdev: add NBD: fix handling of IPv6 host to unbreak TCP disk live migration
commit: d8bd9aba33326812ed5a44dc18886e97744d16ae
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-29 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 12:21 [pve-devel] " Fiona Ebner
2025-11-29 22:49 ` Thomas Lamprecht [this message]
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=176445653896.1120579.14851558686707660989.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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