• XCP-ng 8.3 updates announcements and testing

    Pinned News
    810
    1 Votes
    810 Posts
    1m Views
    B
    @vxgmichel Installed on my usual test pool. Set disks of a FreeBSD VM to CBT. Migrated the VM from NFS to iSCSI storage. Started Delta Backup Job. No issues except the backup was a full backup for this VM instead of a delta. Followed up with a second backup which then was a delta backup again. No issues with either backup.
  • 0 Votes
    1 Posts
    15 Views
    No one has replied
  • Backups in OX v6

    Backup
    6
    3
    0 Votes
    6 Posts
    184 Views
    J
    @flakpyro I agree with you on the UI part IMHO, XO6 is far from being a clean and clear UI. My impression is that it works well(ish) in screenshots. But acctually using it, and it becomes evident that it is hard to discern and read information that should be clean and clear at a glance. It's going to sound exagerated, but XO6 acctually gives me a little bit of a headache each time I try to use it. XO5 is far from a pretty UI. But OMG is it clear and clean, and present the information structured and clearly. Making many glances full of usefull information. PS: I have several feedback posts over at feedback.vates.tech, regarding the UI part. Where I think there could be improvement. Hoping that XO6 (or maybe XO7) one day can become as good as I would wish it to be.
  • backup mail report says INTERRUPTED but it's not ?

    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.
  • 9 Votes
    67 Posts
    19k Views
    C
    @benapetr That's great - thank you for clarifying - really looking forward to the next release!
  • iscsi shows "No Storage Repositories Detected"

    Unsolved Compute
    1
    0 Votes
    1 Posts
    36 Views
    No one has replied
  • Missing vdi which is a base for a delta

    Unsolved Backup
    17
    0 Votes
    17 Posts
    946 Views
    B
    And the health check passes. How can that be possible? { "id": "0mwnnmk6y-jd7jumsiui", "start": 1795099050682, "status": "success", "updatedAt": 1795103578854, "tasks": [ { "id": "0mwnnmmmn-jvm3zflms38", "start": 1795099053839, "status": "success", "end": 1795103578854, "result": { "size": 302621130752, "id": "b656b0d4-b575-c805-5738-6fd50d150951", "liveMounts": [] }, "message": "transfer" } ], "end": 1795103578854, "result": { "size": 302621130752, "id": "b656b0d4-b575-c805-5738-6fd50d150951", "liveMounts": [] }, "message": "restore", "data": { "backupId": "dc0a417c-e1cb-4b4b-8fd9-d59e2564999f//xo-vm-backups/fb7fca7d-7355-4a48-f35c-d32c8dfa71ee/20261119T051216Z.json", "jobId": "73d695c7-901b-45bd-94ba-f38682705d35", "srId": "caba922c-ac32-67e8-f83b-a5907d880179", "time": 1795065136373 } }
  • 0 Votes
    5 Posts
    107 Views
    C
    @ronan-a said: @ccooke As said by @poddingue , your network is not isolated. You must change that to protect your pool. We are aware of this issue and we will change this behavior in a future release to block LINSTOR controller and satellite access from the outside (probably in December). Also we will use TLS to add another security layer. Right. I missed that warning - I was going from https://xcp-ng.org/forum/topic/5361/xostor-hyperconvergence-preview which doesn't look to link to the XOSTOR documentation with the warning. Does this need a full reinstall effectively, or can I recover it? I see the warning is you can't have hypervisors with any public IPs - that will need a little re-engineering for my small test cluster. I know you can change the IP addresses for linstor after installing xostor - does that resolve the issue, or is there no way to secure it when the hypervisor is on a public IP? Could I not just add some firewall rules for now? Thanks for the reply.
  • 0 Votes
    19 Posts
    980 Views
    poddingueP
    Thanks, both of you, for putting the tests on the GitHub issue (https://github.com/vatesfr/xen-orchestra/issues/10741). Florent and the devs have everything in one place now. @frb94, sorry the NFS side pushed you back to Veeam for the VM backups. I can't promise anything on timing, but I'll keep an eye on the issue and post here if it moves.
  • 0 Votes
    15 Posts
    375 Views
    O
    @jr-m4 hello, thanks for your feedback, I've gathered your feedback and will work with our designer to improve the UX/UI. Thanks again for testing
  • Slow SR Creation

    Unsolved Management
    15
    1
    0 Votes
    15 Posts
    1k Views
    I
    @tjkreidl everything looks normal. I also shared SOS report with @goulven I hope I'll get a feedback on slowness.
  • 🛰️ XO 6: dedicated thread for all your feedback!

    Pinned Xen Orchestra
    334
    7 Votes
    334 Posts
    229k Views
    coolsport00C
    @julienXOvates Superb Julien. I figured it was in your really long list that you all are working on. Appreciate the response!
  • xoa kernel update crash the VM ! linux-image-6.1.0-55

    Unsolved Management
    4
    2 Votes
    4 Posts
    147 Views
    poddingueP
    Thanks for the heads-up, @Pilow. In case someone finds this later, Debian tracks it as bug #1154101, an ext4 regression in kernel 6.1.192-1, which installs as -55. They marked it fixed in 6.1.192-2 on 16 November. That one installs as linux-image-6.1.0-56-amd64, so it's the -56 in your proxy screenshot. The XOA in my test lab never picked up -55, and apt-cache policy there already offers 6.1.192-2 as the next kernel. I think unattended-upgrades will jump straight to the fixed one, but I haven't watched it do that. If you put the hold in place, you'll want sudo apt-mark unhold linux-image-amd64 once you're on -56. Otherwise, if I understand holds correctly, the box stops getting kernel updates, including the security ones. It might be worth a mention to @Team-XO-Backend too, since XOA installs these kernels on its own.
  • Full backup failure when upgrading XOce

    Unsolved Backup
    13
    0 Votes
    13 Posts
    351 Views
    P
    @acebmxer said: So when you used my script it worked aside from the backup hiccup? Yes, so far what I have tested. Seems like You put some effort int this one, keeping my fingers crossed It' using node v24.22.3
  • New Tools 9.2.445 update failure

    Unsolved Management
    5
    1
    0 Votes
    5 Posts
    254 Views
    F
    @dinhngtu I will mention that the package was deployed via windows SCCM deployment tools so that may have also played a part in leaving the old product code behind. After running the above script we were able to deploy 9.2.445 via SCCM without issue and no old product codes were left behind.
  • MFA for console access

    Unsolved XCP-ng
    2
    0 Votes
    2 Posts
    179 Views
    poddingueP
    I haven't tried Duo on a host myself, so this comes from reading an 8.3 dom0 rather than from experience. The first thing I'd watch is that XAPI checks the root password through PAM as well. /etc/pam.d/xapi just includes system-auth, so my guess is that a Duo module placed in system-auth would make every password login to XAPI (XO's connection to the pool, xe -pw, XO Lite) ask for a factor it can't give. The physical console is less simple than it looks too: tty1 runs xsconsole, and on my 8.3 host it checks root against the password-auth PAM service by handing over just the password, so I'd expect a module that asks a second question to make that login fail rather than prompt. Also worth knowing before an audit: software from outside the XCP-ng repos isn't supported in dom0 (https://docs.xcp-ng.org/installation/requirements), and as far as I can tell from rpm, /etc/pam.d/xapi isn't marked as a config file, so an update would put it back. Anyone who has been through this for real will know more than me.
  • 0 Votes
    5 Posts
    334 Views
    poddingueP
    If I follow your excerpts, there are two different problems stacked here. One is the LinstorSR attach giving up on what looks like a one-second controller hiccup, which is the @Team-Storage side. The other is xenopsd leaving state behind on both hosts after the failed sync point 4, so that every later run trips over it. I think that half belongs to the toolstack people rather than storage, so I'm adding @Team-XAPI-Network too. I can't judge either part myself, so I'll leave it with them.
  • Backup failures after VHD to QCOW2 conversion

    Unsolved Backup
    8
    0 Votes
    8 Posts
    509 Views
    poddingueP
    Thanks for sharing those. I can't read SMlogs well enough to add anything useful myself, so this is really one for @Team-Storage. One thing though: if I read the link right, it expires on 23 November, so it would be good if someone grabbed the files before then.
  • XCP-ng Windows PV tools announcements

    Moved News
    120
    0 Votes
    120 Posts
    66k Views
    F
    Running into an installation issue with this new version. I created a separate thread here about the issue: https://xcp-ng.org/forum/topic/12580/new-tools-9.2.445-update-failure
  • 1 Votes
    4 Posts
    282 Views
    Bastien NolletB
    Here's the fix, which should be merged in the following days/weeks, and should be in the next XO release: https://github.com/vatesfr/xen-orchestra/pull/10809