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

      HA causes reboot of xcp-ng nodes

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      28
      0 Votes
      28 Posts
      690 Views
      tjkreidlT
      @carloum70 One option to address the HA error messages: Delete the HA configuration and re-configure it from scratch once the bonds are all configured OK, which it appears you think they now are.
    • F

      [SOLVED] Just FYI: current update seams to break NUT dependancies

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      35
      0 Votes
      35 Posts
      8k Views
      F
      @Kajetan321 I looked into my server and I think I forget some points. First and foremost I have to say, modifying the systemd files can make you system unbootable! It should not happen, but there is chance since we are also modifying some "natively shipped files". So an update can break your working configuration again and that is not the fault of XCP-NG!!! That said I assume that after a reboot (prior to any of any input of yours) if you enter: systemctl status ups-driver.service nut-server.service nut-monitor.service you will see that "ups-driver.service" is loaded and active, but the 2 other services are not. If thats the case I think I can help you since it is related to a dependency problem during boot up. Please do the following: Remove "nut-driver.target" dependency from "nut-server.service" by calling nano /lib/systemd/system/nut-server.service and remove nut-driver.target from routine. I prefer to duplicate and comment the to be modified rows to keep the original code. It then should look like this. DO NOT COPY AND PASTE, read, compare and modify carefully! [Unit] Description=Network UPS Tools - power devices information server #After=local-fs.target network.target nut-driver.target After=local-fs.target network.target # We don't Require drivers to be successfully started! This would be # a change of behavior compared to init SysV, and could prevent from # accessing successfully started, at least to audit a system. #Wants=nut-driver.target Wants= # The `upsd` is a networked service (even if bound to a `localhost`) # so it requires that the OS has some notion of networking already. # Extending the unit does not require *this* file to be edited, you # can instead drop in an additional piece of configuration, e.g. add # a `/etc/systemd/system/nut-server.service.d/network.conf` with: # [Unit] # Requires=network-online.target # After=network-online.target Requires=network.target Before=nut-monitor.service PartOf=nut.target [Service] EnvironmentFile=-/etc/ups/nut.conf SyslogIdentifier=%N # Note: foreground mode by default skips writing a PID file (and # needs Type=simple); can use "-FF" here to create one anyway: ExecStart=/usr/sbin/upsd -F ExecReload=/usr/sbin/upsd -c reload -P $MAINPID [Install] WantedBy=nut.target Afterwards enable nut.target: systemctl enable nut.target Then call: systemctl daemon-reload systemctl start nut.target systemctl start nut-monitor.service Now it should work even after reboot
    • J

      Enable Maintenance Mode = Host Not Enough Memory

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      3
      0 Votes
      3 Posts
      48 Views
      J
      @poddingue Huh.. Good catch. I set all of the VMs to restart, and now it does make maintenance mode possible, on the host. However, when we go into licensed/paid production (soon tm). It would be an absolute nightmare to try and find one VM that might not be on the right HA-plan... And it does kind of feel that Maintenance-mode should be compatible with whatever HA-plan is chosen regardless. Perhaps there could be a way to assign a global/pool-wide HA-plan along with enabling HA alltogether? Update: Shining light on that there is already a feedback-item, wishing for this kind of mass-operation for HA. https://feedback.vates.tech/posts/45/bulk-operation-for-setting-vm-ha-option
    • J

      PCIe Pass-through lanes and lane performance

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Compute
      50
      0 Votes
      50 Posts
      8k Views
      stormiS
      @pandusen said: its scary that GPU passthrough still has a low priority for XCP-ng, during the boom of AI and local LLM Inferencing. As XCP-ng product owner, and someone who sees how much work developers put into such topics, may I ask you to elaborate on this "has low priority" statement?
    • F

      [dedicated thread] Dell Open Manage Appliance (OME)

      Watching Ignoring Scheduled Pinned Locked Moved Solved Compute
      104
      1
      0 Votes
      104 Posts
      63k Views
      S
      @ataxyanetwork hey, thanks for sharing this. I am new to the forum so maybe i am not looking in the right place. Your Blog seems to be offline, so did you link the Appliance here in the forum or is it only available on the blog thx
    • henri9813H

      Cleanup orphans backups

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      4
      0 Votes
      4 Posts
      148 Views
      P
      @henri9813 Hi, There should be a new "reclaimSpace" in next release which help you to clean repositories. Just to let you know, we prefer to not remove orphan backups in case a VM removal is accidental and you want to bring back it from a backup repository