I see that the bug is actually already fixed on the latest version (5.98.1).

I believe Proxmox Backup Server kernel Linux pbs 6.8.4-2-pve has also the same issue. updating to Linux pbs 6.8.12-1-pve solves.

@darkbounce Short answer: it seems that Intel hybrid architecture is finding a way to make something that would result of Xen running the VM with the less "featured" CPU, meaning your VM will never use all P core instructions that aren't on E core, meaning... it will work without disabling one or another. Hard to tell how much is lost in terms of perfs vs the best Intel hybrid scheduler (which is on... Windows) but probably not that much on a machine with a reduced number of P cores like this one.

@yammy I hope you are not talking of installing Docker in the Dom0, because this is really a bad idea.

@Pix [image: 1724423840376-capture-d-e-cran-2024-08-23-a-16.36.56.png] Looks like the different HW or Pool is an issue, i'll make more tests and report here if it's ok

@PontusB i don't even know if disabling option 66 solves the issue but as soon as we add option 66 in our DHCP server it boots fine from XenServer (but without HA between the many PVS servers).

@stormi Thanks, looking forward.

@olivierlambert There you go hehe

@bloodyskullz If you still see the old ISO SR, the easiest way to migrate is simply by creating a new one and migrate the ISOs through XO to the new one. In regards to deletion of the old SR you need to check if it really is mapped to another drive or if the mapping was not working and it filled / if so, you might not be able to delete it

@bleader said in update via yum or via xoa?: yes you're basically doing an RPU manually. But it is indeed odd that the process is stuck at 0%, it should be fairly fast to do the install patches, no errors in the logs? i've another install all patches and install all. Now i'll use rpm update and see if speed is the same or not

@Danp Yes to both. I've probably restarted the toolstack at least a dozen times, mostly to clear hung tasks. I did notice some weird issues with a secondary SR being disconnected on xcp02, (one of 10 hosts, 9 after I ejected and forgot xcp01), but there's no disks on it. It wasn't being used for anything at all (yet), and it's fine on all the rest. That does lead me to think maybe it was a power bump that rebooted a switch or something though. Maybe it caused some kind of hangup with xcp01 and xcp02, and since xcp01 was the pool master, it cascaded to the other issues I've seen? Could that cause the VM's that were originally running on xcp02 to die and not be able to be recovered easily?

I just tried to install Ubuntu 24.04 to test it out, and I experienced the same problem with it not recognizing the IP address. I was first using the Ubuntu-provided package (xe-guest-utilities=7.20.2-0ubuntu1), which was failing. I then tried the package I had been using with my Ubuntu 22.04 servers that used to be part of the XCP-ng guest-tools.iso (xe-guest-utilities_7.20.0-9_amd64.deb) and had the same results. I mounted my current guest-tools.iso, which now has xe-guest-utilities_7.30.0-11_amd64.deb, and installed it. Now it was retrieving the IP address correctly. I'm not sure why the OP was still having trouble with that version (I'm using UEFI instead of BIOS, but I wouldn't think that would matter). I went ahead and tried out the Rust-based tools mentioned (xen-guest-agent_0.4.0_amd64.deb), and it was properly getting the IP address as well. I'm guessing there's some incompatibility (probably with the 6.x kernel) that was fixed between 7.20 and 7.30 (intentionally or accidentally). Given how much the Linux tools have changed over the years and the fact that they're not used for PV drivers anymore, is there a particular reason to use one over the other (legacy vs Rust)? What features do they really provide now? Is it just CPU/memory/disk/network status?

In any case, you can ignore it.

@Danp Okay, you're a genius, I upgrade this morning after my backup. So that could explain my issue. the mentioned thread is exactly my issue, but I didn't find it when I was searching about my issue. Thanks for all !

No, from the XCP-ng point of view, the VM is still running without any interruption.

@olivierlambert @Marc-pezin Thank you very much for sorting this out!

@nick-lloyd I like your interpretation.

@aghering You could try compiling it yourself on 8.1... I don't have an 8.1 test/build system.

@NerdsOrder66 Ah, good question... My most recent environment included a Windows Server with 100+ RDP users. There wasn't anything special for optimization there aside from giving it a bunch of RAM/CPU resources, but YMMV.