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
    • A

      XO Community edition backups dont work as of build 6b263

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      64
      0 Votes
      64 Posts
      2k Views
      R
      @florent Great work, thanks for the fixes
    • R

      Internal error: Not_found after Vinchin backup

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      56
      0 Votes
      56 Posts
      666 Views
      olivierlambertO
      So you have to dig in the SMlog to check what's going on
    • B

      XO and XCP-ng pricing

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      34
      0 Votes
      34 Posts
      838 Views
      B
      @DustinB Been using it since 2012, non-profits fell under the academic tier and it was originally by number of cpu which was 2 cpu per host, under 192G ram but again didnt include vmotion etc, just plain ole esxi why I used Veeam since it brought replication into the mix again still using them at a very low cost. They had essentials and essentials plus and the academic pricing was very low, my understanding is they would rather you use VMware vs something else. Again I have receipts going back to 2012, pretty much same price for all these years until Broadcom entered the picture. There was nothing sus about it, you had to verify your non-profit category and fit within the limts, it was pretty standard pricing for a low number of cores, I could go to CDW or any reseller and get the same pricing. Why you have so many small companies jumping ship many were using vmware essentials which was WAY cheaper then what they are doing now which the only option is Standard and it now requires min of 16 cores per host @$50/core. That is the new and wonderful world of Broadcom... Anyway, this was pretty common stuff under VMware, why so many folks were using it, even the small shops.
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      211
      1 Votes
      211 Posts
      22k Views
      gduperreyG
      @manilx We recently upgraded our Koji build system. This may have caused disruptions in this recent update release yesterday, where an XML file was generated multiple times. This has now been fixed and should not happen again. This may explain the issue encountered this time, particularly with the notification of updates via XO. Note that normally yum metadata expires after a few hours and so it should normally return to normal on its own.
    • P

      Error: invalid HTTP header in response body

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      49
      0 Votes
      49 Posts
      2k Views
      F
      Mine was working on the latest commit however tonight due to a power failure my XO VM rebooted and now i too am experiencing the same errors. My hosts also rebooted as a result. Rolled back to a build from earlier this month and all is well again.
    • D

      [HELP] XCP-ng 4.17.5 dom0 kernel panic — page fault in TCP stack, crashdump attached

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      23
      0 Votes
      23 Posts
      371 Views
      A
      @dnikola The AQC113 10G card (from your vendor) also support 2.5G with the driver loaded.
    • A

      Backups not working

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      21
      2
      1 Votes
      21 Posts
      949 Views
      olivierlambertO
      Excellent news, thanks for the feedback!
    • JamfoFLJ

      Xen Orchestra from Sources unreachable after applying XCPng Patch updates

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      19
      0 Votes
      19 Posts
      298 Views
      K
      Hello. @JamfoFL said in Xen Orchestra from Sources unreachable after applying XCPng Patch updates: This is very odd. When I check to see if the Orchestra status is running, everything looks OK: [image: 1752072112055-5c529c8c-8f2b-4c79-806c-daa2b8398847-image.png] This doesn't look ok. The process behind this service has actually exited. Suggest you start/restart this service and check if XO is reachable. If it's not, dive into the logs and look for clues why the process is exiting. You may want to also try manually running /etc/init.d/orchestra and see if that produces any helpful output. But when I try to run the command you sent over, I get an error message stating "Unit xo-server.service" could not be found". However, when I check in the very same folder from which I am running the command, I can see xo-server.service right there. Not taking away from the points others have made about .service files needing to be in the correct location, but in your case, worrying about the xo-server.service file is probably a dead end. It appears whoever installed XO created the systemd service as orchestra. You needn't try and "fix" the fact you don't have an xo-server.service. .joel
    • B

      Migrating from XCP-ng Windows guest tools to Citrix

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      20
      0 Votes
      20 Posts
      686 Views
      B
      I did it that way so as to get the old Citrix driver first, and then let it update and watch it reboot. That was my logic anyway. @dinhngtu said in Migrating from XCP-ng Windows guest tools to Citrix: @bberndt Okay, I managed to reproduce your situation. I think it's because the "driver via Windows Update" option was enabled after installing the XS drivers, which caused the drivers to lock onto the non-C000 device and prevent updates from coming in. Normally, XenClean should be able to fix the situation. But if you want to fix things manually, or if things still don't work (C000 is still not active), here's a procedure that should fix the problem: Take a snapshot/backup/etc. Keep a note of static IP addresses (if you have any; there's a chance those will be lost). You can also use our script here: https://github.com/xcp-ng/win-pv-drivers/blob/xcp-ng-9.1/XenDriverUtils/Copy-XenVifSettings.ps1 Reboot in safe mode and disable the non-C000 device. Reboot back to normal mode; it'll ask you to reboot a few more times. The C000 device should now be active and you should be able to get driver updates again. (Optional) You can now enable and manually update the non-C000 device (Browse my computer - Let me pick).
    • R

      VM failed and won't start. Displaying "An emulator required to run this VM failed to start"

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      35
      0 Votes
      35 Posts
      897 Views
      olivierlambertO
      Then try to find anything happening around that time on other hosts, equipment, storage and so on.
    • G

      GPU Passthrough

      Watching Ignoring Scheduled Pinned Locked Moved Management
      16
      3
      0 Votes
      16 Posts
      261 Views
      tjkreidlT
      @gb.123 Interesting -- alert the XCP-ng team to take a closer look, if they haven't seen this already.
    • F

      Failed vm restore

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      16
      0 Votes
      16 Posts
      267 Views
      florentF
      @frank-s yes please the more detailed the bug report is, the easier it is to fix
    • robytR

      mirror backup to S3

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      15
      0 Votes
      15 Posts
      354 Views
      robytR
      any ideas?
    • M

      Windows11 VMs failing to boot

      Watching Ignoring Scheduled Pinned Locked Moved Solved Management
      15
      0 Votes
      15 Posts
      104 Views
      M
      @dinhngtu Thank you so much. If you want me I'll be at the pub.
    • M

      gui issue in latest builds in backup setting

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      14
      2
      0 Votes
      14 Posts
      352 Views
      olivierlambertO
      Excellent!
    • T

      PCI Passthorugh INTERNAL_ERROR

      Watching Ignoring Scheduled Pinned Locked Moved Management
      13
      1
      0 Votes
      13 Posts
      248 Views
      T
      @andriy.sultanov After running that command I didn't have anything returned.
    • planedropP

      XOA 5.107.2 Backup Failure via SMB and S3 (Backblaze)

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      19
      1 Votes
      19 Posts
      526 Views
      olivierlambertO
      Thanks for keeping us posted, really appreciated here by all the team
    • A

      Backup Network - Unable to add new network

      Watching Ignoring Scheduled Pinned Locked Moved Management
      12
      0 Votes
      12 Posts
      256 Views
      olivierlambertO
      @AtaxyaNetwork It will/it does
    • Tristis OrisT

      What metadata restore really do?

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      11
      0 Votes
      11 Posts
      135 Views
      K
      @olivierlambert You got it, I'll do that. Thank you.
    • olivierlambertO

      XOSTOR hyperconvergence preview

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      457
      1
      5 Votes
      457 Posts
      538k Views
      henri9813H
      Hello, I plan to install my XOSTOR cluster on a pool of 7 nodes with 3 replicas, but not all nodes at once because disks are in use. consider: node1 node2 node ... node 5 node 6 node 7. with 2 disks on each sda: 128GB for the OS sdb: 1TB for local sr ( for now ) I emptied node 6 & 7. so, here is what i plan to do: On ALL NODES: setup linstor packages Run the install script on node 6 & 7 to add their disks so: node6# install.sh --disks /dev/sdb node7# install.sh --disks /dev/sdb Then, configure the SR and the linstor plugin manager as the following xe sr-create \ type=linstor name-label=pool-01 \ host-uuid=XXXX \ device-config:group-name=linstor_group/thin_device device-config:redundancy=3 shared=true device-config:provisioning=thin Normally, i should have a linstor cluster running of 2 nodes ( 2 satellite and one controller randomly placed ) with only 2 disks and then, only 2/3 working replicas. The cluster SHOULD be usable ( i'm right on this point ? ) The next step, would be to move VM from node 5 on it to evacuate node 5. and then add it to the cluster by the following node5# install.sh --disks /dev/sdb node5# xe host-call-plugin \ host-uuid=node5-uuid \ plugin=linstor-manager \ fn=addHost args:groupName=linstor_group/thin_device That should deploy satelite on node 5 and add the disk. I normally should have 3/3 working replicas and can start to deploy others nodes progressively. I'm right on the process ? aS mentionned in the discord, i will post my feedbacks and results from my setup once i finalized it. ( maybe thought a blog post somewhere ). Thanks to provide xostor in opensource, it's clearly the missing piece for this virtualization stack in opensource ( vs proxmox )