all lists on lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH manager] pve7to8: detect kernel 6.8.x as a valid running kernel
@ 2024-05-17  8:31 Fiona Ebner
  2024-05-17 12:22 ` Dominik Csapak
  0 siblings, 1 reply; 3+ messages in thread
From: Fiona Ebner @ 2024-05-17  8:31 UTC (permalink / raw)
  To: pve-devel

Reported in the community forum:
https://forum.proxmox.com/threads/145723/post-664612

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
 PVE/CLI/pve7to8.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/PVE/CLI/pve7to8.pm b/PVE/CLI/pve7to8.pm
index b34c8362..8443f1fb 100644
--- a/PVE/CLI/pve7to8.pm
+++ b/PVE/CLI/pve7to8.pm
@@ -204,7 +204,7 @@ sub check_pve_packages {
 	}
 
 	# FIXME: better differentiate between 6.2 from bullseye or bookworm
-	my ($krunning, $kinstalled) = (qr/6\.(?:2\.(?:[2-9]\d+|1[6-8]|1\d\d+)|5)[^~]*$/, 'proxmox-kernel-6.2');
+	my ($krunning, $kinstalled) = (qr/6\.(?:2\.(?:[2-9]\d+|1[6-8]|1\d\d+)|5|8)[^~]*$/, 'proxmox-kernel-6.2');
 	if (!$upgraded) {
 	    # we got a few that avoided 5.15 in cluster with mixed CPUs, so allow older too
 	    ($krunning, $kinstalled) = (qr/(?:5\.(?:13|15)|6\.2)/, 'pve-kernel-5.15');
-- 
2.39.2



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [pve-devel] [PATCH manager] pve7to8: detect kernel 6.8.x as a valid running kernel
  2024-05-17  8:31 [pve-devel] [PATCH manager] pve7to8: detect kernel 6.8.x as a valid running kernel Fiona Ebner
@ 2024-05-17 12:22 ` Dominik Csapak
  2024-05-28 11:00   ` Fiona Ebner
  0 siblings, 1 reply; 3+ messages in thread
From: Dominik Csapak @ 2024-05-17 12:22 UTC (permalink / raw)
  To: Proxmox VE development discussion, Fiona Ebner

On 5/17/24 10:31, Fiona Ebner wrote:
> Reported in the community forum:
> https://forum.proxmox.com/threads/145723/post-664612
> 
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>   PVE/CLI/pve7to8.pm | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/PVE/CLI/pve7to8.pm b/PVE/CLI/pve7to8.pm
> index b34c8362..8443f1fb 100644
> --- a/PVE/CLI/pve7to8.pm
> +++ b/PVE/CLI/pve7to8.pm
> @@ -204,7 +204,7 @@ sub check_pve_packages {
>   	}
>   
>   	# FIXME: better differentiate between 6.2 from bullseye or bookworm
> -	my ($krunning, $kinstalled) = (qr/6\.(?:2\.(?:[2-9]\d+|1[6-8]|1\d\d+)|5)[^~]*$/, 'proxmox-kernel-6.2');
> +	my ($krunning, $kinstalled) = (qr/6\.(?:2\.(?:[2-9]\d+|1[6-8]|1\d\d+)|5|8)[^~]*$/, 'proxmox-kernel-6.2');
>   	if (!$upgraded) {
>   	    # we got a few that avoided 5.15 in cluster with mixed CPUs, so allow older too
>   	    ($krunning, $kinstalled) = (qr/(?:5\.(?:13|15)|6\.2)/, 'pve-kernel-5.15');

wouldn't it be more future proof to just check if the kernel is a -pve one and the version is higher 
(or equal) than what was shipped in pve7 ?

i guess the same thing will happen for pve8to9 sooner or later...


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [pve-devel] [PATCH manager] pve7to8: detect kernel 6.8.x as a valid running kernel
  2024-05-17 12:22 ` Dominik Csapak
@ 2024-05-28 11:00   ` Fiona Ebner
  0 siblings, 0 replies; 3+ messages in thread
From: Fiona Ebner @ 2024-05-28 11:00 UTC (permalink / raw)
  To: Dominik Csapak, Proxmox VE development discussion

Am 17.05.24 um 14:22 schrieb Dominik Csapak:
> On 5/17/24 10:31, Fiona Ebner wrote:
>> Reported in the community forum:
>> https://forum.proxmox.com/threads/145723/post-664612
>>
>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>> ---
>>   PVE/CLI/pve7to8.pm | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/PVE/CLI/pve7to8.pm b/PVE/CLI/pve7to8.pm
>> index b34c8362..8443f1fb 100644
>> --- a/PVE/CLI/pve7to8.pm
>> +++ b/PVE/CLI/pve7to8.pm
>> @@ -204,7 +204,7 @@ sub check_pve_packages {
>>       }
>>         # FIXME: better differentiate between 6.2 from bullseye or
>> bookworm
>> -    my ($krunning, $kinstalled) =
>> (qr/6\.(?:2\.(?:[2-9]\d+|1[6-8]|1\d\d+)|5)[^~]*$/, 'proxmox-kernel-6.2');
>> +    my ($krunning, $kinstalled) =
>> (qr/6\.(?:2\.(?:[2-9]\d+|1[6-8]|1\d\d+)|5|8)[^~]*$/,
>> 'proxmox-kernel-6.2');
>>       if (!$upgraded) {
>>           # we got a few that avoided 5.15 in cluster with mixed CPUs,
>> so allow older too
>>           ($krunning, $kinstalled) = (qr/(?:5\.(?:13|15)|6\.2)/,
>> 'pve-kernel-5.15');
> 
> wouldn't it be more future proof to just check if the kernel is a -pve
> one and the version is higher (or equal) than what was shipped in pve7 ?
> 
> i guess the same thing will happen for pve8to9 sooner or later...
> 

Sent a v2 with that approach:
https://lists.proxmox.com/pipermail/pve-devel/2024-May/064005.html


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-05-28 11:00 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-17  8:31 [pve-devel] [PATCH manager] pve7to8: detect kernel 6.8.x as a valid running kernel Fiona Ebner
2024-05-17 12:22 ` Dominik Csapak
2024-05-28 11:00   ` Fiona Ebner

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal