[image: 1770204922255-7ec89d01-64e4-47c6-a800-e4de50a56e38-grafik.png] This is the RAM usage of my XO CE instance (Debian 13, Node 24, XO commit fa110ed9c92acf03447f5ee3f309ef6861a4a0d4 / "feat: release 6.1.0") Metrics are exported via XO openmetrics plugin. At the spots in the graph where my XO CE instance used around 2GB of RAM it was freshly restarted. Between 31.01. and 03.02. you can see the RAM usage climbing and climbing until my backup jobs went into "interrupted" status on 03.02. due to Node JS heap issue as described in my error report in post https://xcp-ng.org/forum/post/102160.

@TeddyAstie I have to get my hands on a null modem cable first. Will try get that next week and then test. Will get back when I have some results. I have never tried that before, just to be sure: Idea is to connect serial port of the xcp-ng server < null modem cable > serial port of another PC, right? And then just i.e. putty on the other machine and the xcp-ng server should send out console text via serial.

@olivierlambert okay, understood. it is small minor cosmetic problem as of now. need to get you an access to our internal developped app, to show you the potential of sub-xoas ^^' almost out of alpha phase

Hi! See https://docs.xcp-ng.org/releases/release-8-3/#4k-native-disks and https://docs.xcp-ng.org/storage/#largeblock-sr Note that qcow2 format is supporting 4k natively, and it's in release candidate stage, maybe the right approach in a near future

Ping @gregoire

Hi, There's thousands of different S3 providers in the world, and sometimes, some of them are behaving weirdly. We do test our S3 capabilities with the most popular S3 AWS SDK (in Node), so it's very likely that the issue comes fro the provider itself. However, we have no information in your post about which provider you are using, so it's hard to tell.

@randyrue on our side, we do not use custom fields, but TAGs. working well. depends on the number of custom fields you manage, and perhaps not usable because you need field:value ? but nested tags could do the trick : field=value [image: 1770190720889-99027821-448b-415e-ba89-321260247f73-image.png]

REST API VBD order thing: quetion for @mathieuRA

What is the purpose of this discussion? You did create this thread, I think you would know what's the purpose of this discussion Have you asked VEEAM for a solution, because it seems more VEEAM-related question after all I have no idea what it means regarding "replication is not possible for this Oracle point via VEEAM". Remember we aren't from VEEAM in here, so you should explain more precisely what do you expect from us to do despite it seems to be a VEEAM limitation?

Something to document @thomas-dkmt

Hi, You mean persistence after XCP-ng updates, right?

@dinhngtu said in XCP-ng Windows PV tools announcements: Hello all, The XCP-ng Standard VGA Display Driver for Windows v0.1.29.2216 has been released https://github.com/xcp-ng/win-xstdvga This driver provides high-resolution consoles and resolution switching for Windows VMs running on the XCP-ng hypervisor. This is a beta release. This driver will eventually be integrated into the main Windows PV tools package. Driver pulled for bug fixes. Will come back soon Test on windows 11 vm no issues to report.