=== arif-ali_ is now known as arif-ali === MJCDcook is now known as MJCD [12:18] Hi all, anybody around who knows what is or will be the standard compression method of the ubuntu kernels? I have 5.4.0-96 (LZ4 compressed), 5.11.0-46 (GZIP compressed) and 5.13.0-27 (ZSTD compressed). Since I'm running Xen and pygrub isn't capable of decompressing neither LZ4 nor ZSTD I'm trying to figure out whether I need to find a permanent solution. [12:22] 2nd question would be if the upcoming LTS release will stuck with Xen 4.11.4 as it seems to be once looking on the current 22.04 package list or if Canonical is planning to include a more recent version as Debian already did. [12:39] i can't comment on the xen version. but the choice of initrd compression is up to you, it's configurable. [12:40] generally, there's #ubuntu-next for 22.04 topics [12:40] yosamite9999: ^ [12:42] What I have read is that the kernel compression method is set as a kernel parameter before compilation. So my understanding is that I cannot change that except compiling the kernel by myself. [12:43] and in regards to my second question I will move that one to #ubuntu-next [12:45] oh you're referring to the kernel itself, sorry. i was thinking of the COMPRESS= option in /etc/initramfs-tools/initramfs.conf [12:50] @tomreyn Yes, that's exactly the issue, initrd decompression isn't the problem. I'm wondering anyway why I have 3 relatively recent 20.04 kernels having 3 different kernel compression methods applied. Not really sustainable! [12:51] i think there was recently some discussion on what should be used, but i don'T remember where exactly. probably the -devel mailing list [12:51] or a related bug report [12:55] if it's of any use to you: the 22.04 new desktop installer canary i installed with less than a week ago is: https://termbin.com/ny89 [12:57] (and server uses the same kernel as desktop by default, with the exception that it may onboard HWE with a different strategy) [14:04] @tomreyn Thank you for the hint, will check the current 22.04 kernel on the compression method being used but already thinking of to move from ubuntu to Debian as my default Xen host OS [14:09] yosamite9999: you could file a bug against xen in ubuntu, requesting for it to be synched from debian before release. it may be too late for this, not sure. [14:10] debian import freeze is on february 19th, so it can still work https://discourse.ubuntu.com/t/jammy-jellyfish-release-schedule/23906 [14:11] !bug [14:11] If you find a bug in Ubuntu or any of its official !flavors, please report it using the command « ubuntu-bug » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs. [14:51] @tomreyn well, it's not really a bug, decompression is working with any method on plain machines but not with ZSTD and pygrub. Knowing this, is a bug report still the right way to go? [15:31] @tomreyn: Anyway, many thanks for you suggetions, subscribed to the ubuntu-devel-discuss mailing list and raised both topics there incl your idea to sync with Debian before freeze. [20:32] yosamite9999: i meant to suggest a bug report to get a newer xen version into 22.04 before release [20:32] that would be a feature / debian sync request [22:35] anyone know a good lightweight server monitoring tool that's foss? [22:38] sar [22:42] oh that looks perfect I'll try it [22:42] I was actually just about to look at netdata before you said that [22:46] that's an option if you don't take "lightweight" as seriously [22:47] yeah. I am trying to find one I can just run over ssh, but it's hard to dig through those http-hosted options to get to things like sar... i guess they're really popular. [22:50] netdata is still not very demanding, but it certainly involves more services, more indirection, more cpu + ram. if you actually have multiple systems to monitor, you may want an agent-based solution which reports to a central monitoring (only9 instance. [22:51] naw, It's just a single raspberry pi nextcloud server. [22:51] but out of curiousity, is there anything foss that's easier to get working than zabbix [22:51] ? [22:52] the current vmlinuz-5.13.0-27-generic jammy kernel is zstd compressed [22:53] that conversation was a while ago but just saw it now :) [22:56] I know and that's the issue, pygrub can decompress, resulting in a non ELF, causing kernel panic [22:56] on Dom0 as well as on pvh DomUs