1. Home
  2. Popular
Log in to post
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    477
    1 Votes
    477 Posts
    195k Views
    F
    Updates deployed, no issues so far.
  • H

    89 vulnerabilities in XAPI / Citrix XenServer

    Solved Development
    7
    0 Votes
    7 Posts
    782 Views
    TeddyAstieT
    Xen Project covered this as XSA-489.
  • C

    Error while scanning disk

    Backup
    12
    0 Votes
    12 Posts
    256 Views
    poddingueP
    Thanks for following up and opening the issue; that's exactly the kind of report the team needs. I've subscribed to it, so I'll see when it moves. The second-run failure pattern is a useful clue; hopefully they can reproduce it from there.
  • olivierlambertO

    🛰️ XO 6: dedicated thread for all your feedback!

    Pinned Xen Orchestra
    184
    7 Votes
    184 Posts
    24k Views
    G
    @MajorP93 Before the LTS release UEFI worked extremely well, something kind of went sideways when it hit release. I only have a single UEFI VM, it was created under version 8.2 and does not give me trouble. I guess I need to get my lab back up, had a UPS fail and shut everything off a few days ago. Then I need to test UEFI VMs and see what I can see. But back when it went LTS I reinstalled from scratch and tried to do everything through XO-lite to get the first VM running and found that Debian 13 or Windows Server 2022 would not boot if I created them with UEFI. Since then I haven't tested this again. I'm also tempted to just move my whole lab to version 9, waiting for the next ISO to land and I may do this. I can run real testing workloads on Harvester for the time being and maybe play around migrating back and forth between both systems.
  • R

    VTPM_MAX_AMOUNT_REACHED

    Management
    3
    1
    1 Votes
    3 Posts
    141 Views
    olivierlambertO
    Interesting Maybe a way to create the vTPM in XO? Adding @julienxovates in the loop
  • JamfoFLJ

    Xen Orchestra has stopped updating commits

    Xen Orchestra
    27
    0 Votes
    27 Posts
    9k Views
    D
    I ran into this issue today after doing the following I was still seeing the old version in the settings -> about sudo systemctl stop xo-server git pull --ff-only yarn yarn build --force sudo systemctl start xo-server I then did a full OS reboot now the commit shows up to date rather than 23 commits behind, why was a reboot needed? Shouldn't restarting the service be enough?
  • M

    CR backup with retention > 4

    Backup
    4
    0 Votes
    4 Posts
    186 Views
    M
    @florent So for CR backups it is safe to have a retention value of 13 and just ignore the warnings?
  • B

    The Lowest Priority Bug Ever? (/etc/udev/rules.d/z10-xen-vcpu-hotplug.rules)

    XCP-ng
    4
    0 Votes
    4 Posts
    369 Views
    B
    @Team-OS-Platform-Release , lowest priority ever, but any thoughts on the topic at hand?