XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      814
      1 Votes
      814 Posts
      1m Views
      A
      @vxgmichel @lmolina Pools updated, working so far. Rolling reboot failed because of backup (CR) conflicts. CR backups cause RPU to fail. RPU causes CR backups to fail.
    • okynnorO

      iscsi shows "No Storage Repositories Detected"

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Compute
      5
      0 Votes
      5 Posts
      86 Views
      okynnorO
      @DustinB Wowsers! Thank you ...I got my metadata back! I got a new problem...when I try to turn on my VMs, they are reporting NO_HOSTS_AVAILABLE() Also, while iSCSI is listed under Storage, and reports usage and free space, it's showing as disconnected. I suspect that the fact that iSCSI is disconnected leads me to believe that the VMs are not starting. When I look into the iScsi repository under XSCONSOLE, it's saying This Storage Repository is unplugged and not usable by this host. When I look at the iSCSI setup under TrueNAS Scale, it's showing as running. I'm on a roll thanks you guys...just need one more push! [image: Screenshot 2026-11-20 at 1.30.32 PM.png]
    • acebmxerA

      Backups in OX v6

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      8
      3
      0 Votes
      8 Posts
      233 Views
      poddingueP
      @flakpyro from your screenshot and a look at the code, I think the VM name is already stored on each of those "backup VM" tasks, but the XO 6 task list just shows the generic label instead, so it might be a small change rather than a big missing piece (I haven't checked whether the side panel shows it). It could be worth its own post on feedback.vates.tech so it gets votes. The closest one I found is about the job's detail panel rather than the task list: https://feedback.vates.tech/posts/60/xo6-backup-summary-is-a-stacked-jumbled-and-cryptic
    • J

      [XO6] Bug: Working in multiple XO6 in tabs, breaks the "eye"-sidebar

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      2
      0 Votes
      2 Posts
      55 Views
      poddingueP
      I tried your steps on a lab XOA running 6.10, and I could reproduce it, but only once I had unpinned the side panel. With the panel pinned (the pin button at the top of the panel), switching tabs left it alone in my test, so that might do as a workaround for now. Did you unpin it at some point, or is your browser window on the narrow side? From a quick look at the code, I think the open or closed state of that panel is kept in the browser's local storage, which all tabs of the same site share, so one tab closing it closes it for the others, though I may be misreading it. You have the steps written down already, so I'd pass them to @Team-XO-Frontend; whether it's meant to work that way is their call, not mine.
    • P

      backup mail report says INTERRUPTED but it's not ?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      125
      5
      0 Votes
      125 Posts
      50k Views
      T
      @Pilow, I saw your update that the affected backups show SUCCESS in XOA, are present on the remote, and have been restored successfully. Given that, your suggestion about the report being generated before the final status is available seems reasonable. Bastien’s delay test looks like a useful way to check that. You mentioned the first day after applying it was clear, although with the issue appearing intermittently, it would probably take several days of reports to know whether it helped. I also saw your later test: one- and two-second delays still produced interrupted reports, while three seconds appeared to work over two days. The team has since merged a five-second delay. If you’re still seeing the original mismatch, can you confirm whether your current XO build includes that change? That would help establish whether there’s another timing issue, or whether the fix simply hasn’t reached the installation yet. For the next occurrence, it may help to keep the email timestamp and the run log for that same job, particularly if only one VM in a larger job is marked interrupted in the report. Posting those alongside the XO version would give the team something specific to compare. On a related note, Mail Backup X could be useful as a separate routine if you also want backups of your email accounts. It’s a convenient tool that works across the spectrum and is compatible with IMAP-based email accounts, offers incremental backups and encryption support.
    • B

      Missing vdi which is a base for a delta

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      18
      0 Votes
      18 Posts
      988 Views
      poddingueP
      @blueh2o I think the two things you saw fit together, at least going by what I see in the mirror code. The 1 differencing tag only says that this one backup's disk is a delta, which is normal for an incremental; the key sits further back in the chain, which I think is why the health check could still rebuild the whole ~280 GiB disk. And as I wrote a few posts up, the mirror reads the parent of each delta on Ark and then asks each target whether it already has it, so last night's error would mean the Synology is missing d08f1acc for that one VM (fb7fca7d), not that Ark is broken. That brings us back to Florent's suggestion from the older thread, deleting that VM's most recent backups on the Synology so they get sent again, though I can't tell you why the Synology lost that base in the first place. At least it's down to one VM out of 56 last night, against 16 in October.
    • samuelolavoS

      Large QCOW2 VDI on LVM SR fails to activate with make_chain_rw / Input/output error

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XCP-ng
      5
      1 Votes
      5 Posts
      527 Views
      lmolinaL
      Hello, the current update candidate includes fixes related to this issue. Note that it is still under testing.
    • enkaskalE

      packer plugin signing key

      Watching Ignoring Scheduled Pinned Locked Moved Infrastructure as Code
      4
      0 Votes
      4 Posts
      456 Views
      poddingueP
      @enkaskal I need to correct my reply above, I got two things wrong. The plugin is ours after all: ddelnano/packer-plugin-xenserver is the repo's old address, it moved to vatesfr/packer-plugin-xenserver (where you filed #212), and GitHub just redirects the old link, which I read on our IaC docs page and jumped to the wrong conclusion. The key isn't missing either, I just didn't look in the right place: it's the signing key the Terraform Registry lists for vatesfr/xenorchestra, so you can fetch it from there. curl -s https://registry.terraform.io/v1/providers/vatesfr/xenorchestra/0.41.2/download/linux/amd64 \ | jq -r '.signing_keys.gpg_public_keys[0].ascii_armor' > xenorchestra-signing.asc gpg --import xenorchestra-signing.asc gpg --verify packer-plugin-xenserver_v0.12.0_SHA256SUMS.sig packer-plugin-xenserver_v0.12.0_SHA256SUMS On my machine the last command reports a good signature from 0DD2E92A7A0F682BC29F87073084D82948625D89, still a key in Dom Delnano's name from before the move. I'm honestly not sure how much trust that gives you beyond "the registry vouches for the same key", so I'd leave that part to the folks on #212 who know the release side better than me. Sorry for the detour.
    • C

      XOSTOR getting an SR_BACKEND_FAILURE because it is trying to connect to a random IP

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XOSTOR
      6
      0 Votes
      6 Posts
      138 Views
      C
      @poddingue said: Do your hosts have public IP addresses on their management interface? I'm asking because the XOSTOR docs carry a warning about that setup (here) : according to them, the LINSTOR satellites listen on port 3366 without authentication, and an outside party can connect to them and get in the way of the real controller. If yours are reachable from outside, I think a different address each time would fit that, but I haven't checked it against a setup like yours. Thanks for offering to keep the cluster in that state for a bit. I'd point @Team-Storage at it before you reboot anything, since they're much better placed than me to say what's worth collecting. Does it look like you need to examine anything? I'm okay keeping it as-is for another day or two, but it would be good to know.
    • B

      New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      Watching Ignoring Scheduled Pinned Locked Moved News
      67
      1
      9 Votes
      67 Posts
      19k Views
      C
      @benapetr That's great - thank you for clarifying - really looking forward to the next release!