• 0 Votes
    1 Posts
    3 Views
    No one has replied
  • 🛰️ XO 6: dedicated thread for all your feedback!

    Pinned Xen Orchestra
    334
    7 Votes
    334 Posts
    227k Views
    C
    @julienXOvates Superb Julien. I figured it was in your really long list that you all are working on. Appreciate the response!
  • 9 Votes
    61 Posts
    18k Views
    bvitnikB
    @benapetr Here are some more bugs: Templates are still not sorted correctly in the tree view. User templates (blue) should go first then built in ones (yellow). Each group should be sorted alpabetically (see the screenshot). Icons are back for categories (under the tree view) but elements should be left aligned. They look ugly when centered (screenshot). Categories are still not collapsable to a single icon like shown in previous screenshots. With the addition of horizontal scrollbar, there seems to be an ugly regression in tree view itself. The tree view is refreshed each 30 sec but while doing so, the tree is collapsed and then expanded. It's a little bit hard to explain but the tree just "jumps" in front of the eyes. This is particularly annoying while doing something in the tree view. The New VM dialog, template selection section, now seems to be functionally identical, not visually though. [image: image.jpeg]
  • Missing vdi which is a base for a delta

    Unsolved Backup
    14
    0 Votes
    14 Posts
    854 Views
    B
    @poddingue They were all on Ark. VMs: 7da38127-0ff5-1f76-d8b6-a5159a37d658 7eb23022-4f0b-f73e-b544-c4d860e54453 865f4634-76f6-48a3-938e-3adff4fb9e3f 9a64cc4e-0b46-d01e-bfcf-3fbedbd7e334 a1f1bee1-4076-b37f-006c-630d5c3a9f39 a86bb37b-a0ec-3d94-b52d-196da40b317d a925c4c2-b3f3-6cc3-3c40-a836e3a24914 b27a40e4-ea4f-7706-fb4e-98551fa85d0d b92636e5-c9f1-47d6-644f-70158dc39f0e bbe64766-97f3-de14-43aa-77867b7f1fb0 d1a39422-78d6-56d1-28c3-65299cdc1a5e d77691ef-a507-e120-e2b8-2c1807f0ef99 edc46393-eee4-6a39-89c0-0b4486df8879 f8ed66aa-e753-1271-84c6-a73819ff25f7 fb7fca7d-7355-4a48-f35c-d32c8dfa71ee
  • xoa kernel update crash the VM ! linux-image-6.1.0-55

    Unsolved Management
    4
    2 Votes
    4 Posts
    85 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.
  • Backups in OX v6

    Backup
    2
    3
    0 Votes
    2 Posts
    79 Views
    poddingueP
    I don't think the manual run part is a bug. XO 6 has its own message for it ("This backup job has multiple schedules"), so it looks like a deliberate limit for now, though I don't know the reasoning behind it. On the chains, if I'm reading the backup code right, an incremental job only looks for its parent disks in a folder named after the job's ID. If that's right, splitting into two jobs would give you two separate chains on the remote, each starting with its own full. If the Full Backups schedule is there to restart the chain every so often, the docs describe the full backup interval setting on the delta job as the way to do that within one job: https://docs.xen-orchestra.com/backups-and-dr/backup-types/incremental_backups#key-backup-interval I haven't tried switching a running job over to it myself. @Team-XO-Frontend can probably say what the split advice has in mind.
  • 0 Votes
    14 Posts
    196 Views
    J
    Small thing I noticed: I have set the job to import 4 VMs. (2 concurrent) The Global counter is listing 3, as it has completed 1 and therefore gone up from 2->3.. However, the global counter-circle is listing 3. But the tracking percentage is counting the overall job. So in this case, the percentage tracker, is the correct one. Whereas the acctual counter is not showing the acctual amount of VMs that are in the job. [image: image.jpeg]
  • Full backup failure when upgrading XOce

    Unsolved Backup
    13
    0 Votes
    13 Posts
    259 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
    169 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.
  • 0 Votes
    18 Posts
    855 Views
    acebmxerA
    @poddingue added my info as well.
  • MFA for console access

    Unsolved XCP-ng
    2
    0 Votes
    2 Posts
    158 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
    306 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
    465 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
    236 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
  • New 9.2.445 XCP Windows tools Roll Back

    Management
    3
    0 Votes
    3 Posts
    220 Views
    B
    Looks like the tools installation had an issue with Windows Update packages, the windows event log started throwing error relating to the cryptsvc service and C:\Windows\System32\catroot2 at the time I ran XenClean before trying to install 9.2445. Rebuilding Catroot resolved the issue and tools installed fine. net stop cryptsvc ren C:\Windows\System32\catroot2 catroot2.old net start cryptsvc Reboot Appears to be isolated to this single VM
  • 0 Votes
    12 Posts
    6k Views
    olivierlambertO
    Hi @odmsys It's on the roadmap and it won't wait for SMAPIv3. I truly hope we can bring something in a matter of few months, at least to have it to test
  • Native Ceph RBD SM driver for XCP-ng

    Development
    43
    3 Votes
    43 Posts
    12k Views
    A
    @dicode-nl Thank you for the code. I'm in testing now with ceph 20.2.5 and so far I haven't had any issues.
  • XCP-ng 8.3 updates announcements and testing

    Pinned News
    802
    1 Votes
    802 Posts
    1m Views
    R
    Thank you, @stormi , I'm happy to know that xcp-ng.repo is not touched. These three hosts haven't been rebuilt or restored recently, no hosts have been added, and I did have to make the above modification on each one of them to get them to work. I suppose it's possible I missed the step to remove "mirrors.xcp-ng.org" from xcp-ng.repo during the initial pool build about a year ago and it's just somehow been working with our outbound Internet proxy. In any event, having "mirrors.xcp-ng.org" in our xcp-ng.repo file has definitely caused us problems in the past with our proxy setup. TGIF/DMCV!
  • Disk import not happens

    Unsolved Management
    5
    0 Votes
    5 Posts
    254 Views
    Tristis OrisT
    error via reverse proxy. Uncaught Error: Body is not a JSON, original message is : <html> <title>500 Internal Server Error</title> <style>html{color-scheme:light dark;}</style> </head> <body> <center><h1>500 Internal Server Error</h1></center> <hr><center>Angie</center> </body> </html> pr index.js:2564 me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 be index.js:4029 be index.js:4029 dr index.js:2531 importDisks index.js:2575 Lodash 2 importDisks index.js:2574 e index.js:113 P index.js:22 i index.js:22 R index.js:22 R index.js:22 import index.js:121 t factory.js:307 o factory.js:331 e action-button.js:93 m action-button.js:10 i action-button.js:10 _execute action-button.js:10 _execute action-button.js:10 _execute action-button.js:10 v action-button.js:140 componentDidMount action-button.js:147 React 14 componentWillUnmount factory.js:125 f factory.js:31 _dispatch factory.js:158 t factory.js:322 promise callback*t factory.js:313 o factory.js:331 value index.js:206 promise callback*value index.js:174 React 5