• Is v8.3 NUMA aware?

    Hardware
    7
    0 Votes
    7 Posts
    336 Views
    Y
    Hello @codemercenary In theory Xen is NUMA aware (See https://wiki.xenproject.org/wiki/Xen_on_NUMA_Machines) so you would leave memory interleaving option of the BIOS off so that Xen does what it thinks is necessary. But these kinds of settings are very very workload sensitive and in fact it's usually a good idea to just test what works best for you. Regards, Yann
  • 0 Votes
    5 Posts
    267 Views
    Y
    @dkg Please also note that you should not use @jul1an ISO installer on production environment. Only on test env where you can afford to break things and lose data.
  • CR backup with retention > 4

    Backup
    8
    0 Votes
    8 Posts
    363 Views
    P
    @McHenry I think depends if the copy is a fast clone, depending of full chain length with 13 points behind, or a full copy of its own that will be independant
  • [SOLVED] Just FYI: current update seams to break NUT dependancies

    XCP-ng
    29
    0 Votes
    29 Posts
    2k Views
    F
    Hi, I just wanted to comment that the provided packages work for all my server. Thank you!
  • Default console username and password on XOA Appliance

    Solved Xen Orchestra
    12
    0 Votes
    12 Posts
    29k Views
    olivierlambertO
    Hi, See https://docs.xen-orchestra.com/troubleshooting#recover-web-login-password
  • Mirror backup: Progress status and ETA

    Backup
    8
    1
    1 Votes
    8 Posts
    486 Views
    M
    @poddingue I see backups in the tasks view fine, just not mirror ones. I'm talking about v5, haven't converted to v6 yet because of missing features.
  • XO Console: Modifier keys stuck, unable to enter passwords

    Xen Orchestra
    12
    0 Votes
    12 Posts
    2k Views
    poddingueP
    Just to close the loop on this: XO 6.4 (released on April 29) includes a specific fix for VNC reconnection, which may have been causing keyboard focus loss and, in turn, modifier keys to get stuck (PR #9727). At least, that’s my understanding; I could be completely wrong, so please take it with a grain of salt. If you’re on XO 6 and still seeing the issue, upgrading to 6.4 may help.
  • XOA Unable to connect xo server every 30s

    Xen Orchestra
    4
    0 Votes
    4 Posts
    183 Views
    poddingueP
    Good news, or at least, that's my understanding. This was a known bug and it's fixed in XO 6.4 (released April 29, PR #9681). Upgrading should make those alerts disappear for good. Thanks for the video, it made the report unambiguous.
  • 4 Votes
    64 Posts
    17k Views
    CyrilleC
    Xen Orchestra Kubernetes Storage Driver new release v0.2.0 Introducing dynamic provisioning The latest CSI driver release introduces dynamic provisioning: by creating a Kubernetes storage class that references the XO CSI driver and sets the poolId parameter, you can then create a PVC and pod using that storage class, and Xen Orchestra will automatically provision new VDIs into the default SR of the chosen pool, to satisfy the requested volumes. Your feedback on the CSI driver is welcome! Which features would you like to see? How would you like to use the driver and storage classes? https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.2.0
  • Date format on web interface: Only US format available?

    Compute
    4
    1 Votes
    4 Posts
    84 Views
    olivierlambertO
    Note that we have 0 XO or XCP-ng dev based in the US neither
  • Install XO from sources.

    Xen Orchestra
    22
    3 Votes
    22 Posts
    2k Views
    F
    Very nice job @acebmxer Well done
  • VM Migration | PIF is not attached

    Compute
    3
    0 Votes
    3 Posts
    123 Views
    C
    I have completed the latest patches that came out and yet i still face this same issue.. anyone have a solution for this?? id "0moke6b1h-u49q39cfnql" properties method "vm.migrate" params vm "038b1fb8-e86c-9169-2ebc-c18b4e9c53f7" migrationNetwork "9a74000a-8481-1b36-2dd1-a58cd6747623" targetHost "82cf5c29-db31-4cc3-b057-db8f85324232" name "API call: vm.migrate" userId "02d261f6-840b-4148-9eb5-d181432af7d2" type "api.call" start 1777487518565 status "failure" updatedAt 1777487530207 warnings 0 data pif "c13bcf0c-ef0c-27bd-592a-58ef4eedf18d" message "PIF is not attached" end 1777487530207 result code "INTERNAL_ERROR" params 0 'xenopsd internal error: Xmlrpc.Parse_error("open_tag(html)", "open_tag(methodResponse)", _)' task uuid "bd7f8d2a-6d91-3d6a-0da2-e4c1c3758346" name_label "Async.VM.pool_migrate" name_description "" allowed_operations [] current_operations {} created "20260429T18:31:58Z" finished "20260429T18:32:09Z" status "failure" resident_on "OpaqueRef:6dadebb7-39c8-4bb7-a559-909a80824227" progress 1 type "<none/>" result "" error_info 0 "INTERNAL_ERROR" 1 'xenopsd internal error: Xmlrpc.Parse_error("open_tag(html)", "open_tag(methodResponse)", _)' other_config {} subtask_of "OpaqueRef:NULL" subtasks [] backtrace "(((process xenopsd-xc)(filename src/lib/xmlrpc.ml)(line 182))((process xenopsd-xc)(filename ocaml/xapi-idl/lib/xcp_client.ml)(line 138))((process xenopsd-xc)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xenopsd-xc)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xenopsd-xc)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xenopsd-xc)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xenopsd-xc)(filename ocaml/libs/stunnel/stunnel.ml)(line 412))((process xenopsd-xc)(filename src/lib/idl.ml)(line 550))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 2816))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_task.ml)(line 103))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_task.ml)(line 111))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 3408))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 3418))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 3439))((process xenopsd-xc)(filename ocaml/xapi-idl/lib/task_server.ml)(line 192))((process xapi)(filename ocaml/xapi/xapi_xenops.ml)(line 3479))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/xapi_xenops.ml)(line 3650))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 262))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 268))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 293))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 434))((process xapi)(filename ocaml/xapi/xapi_xenops.ml)(line 3488))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 458))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 141))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2515))((process xapi)(filename ocaml/xapi/rbac.ml)(line 228))((process xapi)(filename ocaml/xapi/rbac.ml)(line 238))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))" message 'INTERNAL_ERROR(xenopsd internal error: Xmlrpc.Parse_error("open_tag(html)", "open_tag(methodResponse)", _))' name "XapiError" stack 'XapiError: INTERNAL_ERROR(xenopsd internal error: Xmlrpc.Parse_error("open_tag(html)", "open_tag(methodResponse)", _))\n at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202604291609/packages/xen-api/_XapiError.mjs:16:12)\n at default (file:///opt/xo/xo-builds/xen-orchestra-202604291609/packages/xen-api/_getTaskResult.mjs:13:29)\n at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202604291609/packages/xen-api/index.mjs:1078:24)\n at file:///opt/xo/xo-builds/xen-orchestra-202604291609/packages/xen-api/index.mjs:1112:14\n at Array.forEach (<anonymous>)\n at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202604291609/packages/xen-api/index.mjs:1102:12)\n at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202604291609/packages/xen-api/index.mjs:1275:14)' i had to manually migrate VM's using the xe command to do the patching and even now to move hosts back. So the loadbalancing or anything is not working
  • 0 Votes
    5 Posts
    470 Views
    rzrR
    @bnerickson said: Thanks for the reminder, for some reason it was not seen before (all applogies). I'm unsure where to report this, Here or in related open projects directly (assuming you know where to look at) but let me guide you. but syslog reports the following warning when a VM starts: (UDEV-WORKER) cpu0: Process '/bin/sh -c '[ -e /dev/xen/xenbus ] && [ -e /sys/devices/system/cpu/cpu0/online ] && echo 1 > /sys/devices/system/cpu/cpu0/online'' failed with exit code 1. Good catch, it's a bad habit to use AND (&&) in conditionals. Hardcore programmers prefer to use OR (||) in scripts, this practice prevents failed exit and make debugging easier (with set -xe). (...) > ACTION=="add", SUBSYSTEM=="cpu", RUN+="/bin/sh -c 'if [ -e /dev/xen/xenbus ] && [ -e /sys$devpath/online ]; then echo 1 > /sys$devpath/online; fi'" That would work, What about this "simpler" form ? [ ! -e /dev/xen/xenbus ] || [ ! -e /sys$devpath/online ] || echo 1 > /sys$devpath/online Could be harder to read, but I get used to. If you want you can contribute the fix directly to upstream since the file is public at: https://github.com/xenserver/xe-guest-utilities/blob/master/mk/xen-vcpu-hotplug.rules About the exec bit, here is the line that should be changed: https://github.com/xcp-ng-rpms/xcp-ng-pv-tools/commit/3d134fbd0f3ac9e2f3cfa914e38b33529635d458#r183816712 @bnerickson, If you need any mentoring for OSS contributions, I would be more than a happy to help. Since it's a lowest priority you can take all the time you need, and If too busy, no problem we can do it for you and then backport the change to XCP-ng. 1 stormi committed to xcp-ng-rpms/xcp-ng-pv-tools Build the tools from the sources - Build 32 bit and 64 bit xe-guest-utilities - Build TGZ, RPM and DEB packages for xe-guest-utilities - Put the result into the ISO and the ISO into the xcp-ng-pv-tools RPM (as before). It's a bit hacky, but as the binaries are statically linked, this peculiar build process should work.
  • 0 Votes
    11 Posts
    200 Views
    J
    @MathieuRA I noticed you merged https://github.com/vatesfr/xen-orchestra/pull/9787 I just tried it. And it does seem to fix my original issue! Thank you! I am always impressed by you guys. Making testing and reporting upstream (to you guys) a good experience! Elise-FZI opened this pull request in vatesfr/xen-orchestra closed fix(xo6): remove dev routes from prod #9787
  • Error while scanning disk

    Backup
    14
    0 Votes
    14 Posts
    465 Views
    poddingueP
    Thanks, Florent, for the explanation.
  • 89 vulnerabilities in XAPI / Citrix XenServer

    Solved Development
    7
    0 Votes
    7 Posts
    1k Views
    TeddyAstieT
    Xen Project covered this as XSA-489.
  • VTPM_MAX_AMOUNT_REACHED

    Management
    3
    1
    1 Votes
    3 Posts
    200 Views
    olivierlambertO
    Interesting Maybe a way to create the vTPM in XO? Adding @julienxovates in the loop
  • Alcatel OXE on XCP-ng – anyone done this before?

    XCP-ng
    4
    0 Votes
    4 Posts
    241 Views
    olivierlambertO
    Ah very good, so it was even easier than this. You had the Xen blk driver but instead of using an UUID, the appliance was having a hardcoded sda. Keep us posted
  • 0 Votes
    4 Posts
    223 Views
    P
    @delacosta456 said: the pool host maximum limit is 3200% right right
  • VMWARE to XCP-ng migration of 2TB disk

    Migrate to XCP-ng
    3
    0 Votes
    3 Posts
    208 Views
    J
    @CyaVMware said: Have a simple question for someone. Looking at migrating a client to XCP. Currently they have a data disk that is exactly 2TB in VMware. My question is the limitation anything OVER 2TB, or is it 2TB AND above? I'd prefer not to use the VMware converter tool to shrink the disk to 1.99TB if I don't have to. VHD format has a strict limit of roughly 2TB (around 2040 GB), so if your client’s VM disks are larger than this then you’re going to have trouble with VHD format. However QCOW2 support is almost here (production ready) about to reach RC2 state, once this reaches stable you’ll be able to safely reach a max of around 16TB. That is if your using ext4 based SR, other Filesystems have different limits. If using a networked file sharing protocol service then, the limit of the host server’s filesystem applies. Though QCOW2 VDI has a limit of 16 TiB.