Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    TeddyAstieT
    @leroyj We already know that our k10temp module doesn't have support beyond Zen 2, and needs to be updated. That's not incredibly complex, but still needs to be done. I was wondering if the amd cpu temp be probed the way you did for the intel cpu. No, AMD temperature infos are not exposed through MSR but through PCIe/MMIO (through various subsystems, like "SMU" and other ones). Like what does https://github.com/torvalds/linux/blob/master/drivers/hwmon/k10temp.c or https://github.com/ocerman/zenpower. (regarding the AI draft, there is no documented MSR 0xc0010292 in neither APM nor public Zen3 PPM) That doesn't require any specific Xen support aside the right Linux drivers in Dom0.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    poddingueP
    Your thread looks a lot like https://xcp-ng.org/forum/topic/12321. Same error, same call, HA enabled there too. Olivier's answer on that one was that VMs whose HA restart priority isn't Restart aren't protected, so they never get a real evacuation plan. His two workarounds were setting those VMs to Restart, or turning HA off for the maintenance window. It doesn't land for everyone, though. On https://xcp-ng.org/forum/topic/12348 @MajorP93 fixed his by moving every VM from best-effort to restart, and @acebmxer tried the same thing and got HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN instead. Same change, opposite outcome. So, what are your VMs set to, restart or best-effort? That would tell us whether you're looking at the same thing or something else entirely. Upstream there are two PRs off the back of that discussion. 7145 merged on 8 July and only makes the error message clearer. 7146 is the one that changes the evacuation behaviour itself, and it's still open. So if it is the same problem, I don't think there's anything you can pull down yet.

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    P
    @henri9813 Hi, There should be a new "reclaimSpace" in next release which help you to clean repositories. Just to let you know, we prefer to not remove orphan backups in case a VM removal is accidental and you want to bring back it from a backup repository

  • Our hyperconverged storage solution

    54 Topics
    824 Posts
    J
    @poddingue Turns out it is all secondary-to-secondary out of sync. So that makes it less intense, though if primary dies I wonder how it will resolve this, or if it will become split brained. Still unsure of how it happened, but the ones I manually cleaned up have not come back. Going to continue to manually clear them up. If it happens again I will have an alert setup to notify me, and I have all the xcp-ng logs and everything to be able to see what happened. If that happens I will post here with details and logs for the resource so we can see how it occurs. [image: image.jpeg]

  • Non-English speakers

    37 Topics
    136 Posts
    J
    @AtaxyaNetwork Merci pour tes recherches ! Oui "cd_label" serait cool comme ajout au plugin ce qui permet sur les distro type Fedora/Redhat de ne pas avoir de boot_command à gérer