From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH stable-7 container 0/2] setup: cherry-pick ubuntu 24.04 support
Date: Tue, 4 Jun 2024 12:48:14 +0200 [thread overview]
Message-ID: <25a277ea-2929-492c-b293-448db4f29d13@proxmox.com> (raw)
In-Reply-To: <20240604083523.357515-1-c.heiss@proxmox.com>
Am 04/06/2024 um 10:34 schrieb Christoph Heiss:
> This backports the series to support Ubuntu 24.04 "Noble" CTs [0].
>
> They could be cherry-picked cleanly. Tested on a up-to-date PVE 7.4
> system (running on `pvetest`), template for Ubuntu 24.04
> (`ubuntu-24.04-standard_24.04-2_amd64.tar.zst`) was copied from a 8.2
> host for testing.
>
> Tested creating new CT from that template, using either a static IP or
> DHCP. Then working around with the system a bit, everything seems to
> work just fine.
>
> [0] https://lists.proxmox.com/pipermail/pve-devel/2024-April/063766.html
>
> Fiona Ebner (2):
> setup: support Ubuntu 24.04 Noble
> setup: unlink default netplan configuration even with Ubuntu >= 23.04
>
> src/PVE/LXC/Setup/Ubuntu.pm | 3 +++
> 1 file changed, 3 insertions(+)
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-06-04 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 8:34 [pve-devel] " Christoph Heiss
2024-06-04 8:34 ` [pve-devel] [PATCH stable-7 container 1/2] setup: support Ubuntu 24.04 Noble Christoph Heiss
2024-06-04 8:34 ` [pve-devel] [PATCH stable-7 container 2/2] setup: unlink default netplan configuration even with Ubuntu >= 23.04 Christoph Heiss
2024-06-04 10:48 ` 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=25a277ea-2929-492c-b293-448db4f29d13@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@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