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
      32
      0 Votes
      32 Posts
      902 Views
      tjkreidlT
      @john.c Indeed, John, and I almost forgot that the backup network on each host was actually on a separate, isolated NIC, and not at all on the VLAN.
    • olivierlambertO

      🛰️ XO 6: dedicated thread for all your feedback!

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      279
      7 Votes
      279 Posts
      137k Views
      julienXOvatesJ
      @jacob.becker said: Hi! In XO-5 you can see clearly if a host is in maintenace mode" or not. I'm missing a similar thing to the little green/gray dot from XO-5 in the XO6 treeview. You can see it in the System- Tab under General Information, but only if the host is already selected. I personally find it difficult to distinct between hosts and VMs in the treeview if a large amount entries are shown. Especially while scrolling. Hi @jacob.becker, this is going to be fixed in XO 6.9 (ie. the Disable state for a host). I share your point of view about hosts & VM icons, we should also change them. Thanks !
    • P

      Why are transfer sizes different between XO5 & XO6?

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      17
      2
      0 Votes
      17 Posts
      628 Views
      JorisKJ
      Wonderful !
    • F

      XOA 6.8 causes backup / replication failure

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      18
      1
      0 Votes
      18 Posts
      938 Views
      florentF
      @acebmxer we are far more explicit on the real usage of NBD, paing the way to mark a failed NBD connexion as an error in a few month also working on a diagnostic tool to be more efficient on the checks thank you all for your time
    • A

      VDI export to VMDK results in a corrupted disk

      Watching Ignoring Scheduled Pinned Locked Moved Solved Xen Orchestra
      15
      0 Votes
      15 Posts
      639 Views
      A
      @Emmanuel-V In my opinion, it would make more sense if a standalone disk exported in VMDK format were exported directly as monolithicSparse, so that it would not need to be converted. This makes more sense to me because when only the disk is exported, rather than the entire VM (OVA), it can be assumed that the disk will be attached directly to some VM.
    • J

      Troubleshooting "TCP: out of memory" - Possible memory leak?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Xen Orchestra
      14
      1
      0 Votes
      14 Posts
      864 Views
      poddingueP
      Forwarded to the right team, thanks!
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      691
      1 Votes
      691 Posts
      697k Views
      olivierlambertO
      That's a pretty beefy update! It's great to see the live storage migration performance improving by a very nice margin
    • acebmxerA

      Install XO from sources.

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      44
      3 Votes
      44 Posts
      10k Views
      acebmxerA
      @lem2405 No problem. Let me know if you still encounter any issues.
    • J

      PCIe Pass-through lanes and lane performance

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Compute
      56
      0 Votes
      56 Posts
      9k Views
      stormiS
      @JamesG Thanks. I'll let @teddyastie see. I think he would be more confortable with having the card in our lab, which should be imminent now, but I won't speak for him.
    • A

      Error: Can't init vhd directory without using alias

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      12
      1 Votes
      12 Posts
      708 Views
      A
      @pierrebrunet Tested and working again, thanks
    • J

      Not sure if its XOStor but ... VDIs disappearing

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XOSTOR
      12
      0 Votes
      12 Posts
      571 Views
      J
      @poddingue Okay, we're back here. I was told I have a hung CIFS mount that no longer exists, so a host needs to reboot to clear it, and faulty XOSTOR resources. But I can't reboot the host until I can move VMs off. Is there any indication of how to repair the faulty XOSTOR resources so I can move the VMs and reboot the host? Thanks for taking a look.
    • johnnezeroJ

      Tag-Based Automation Plugin: Tag-Based VM Performance & Permission Management via assigned tag(s)

      Watching Ignoring Scheduled Pinned Locked Moved Management
      19
      1
      0 Votes
      19 Posts
      2k Views
      johnnezeroJ
      @fohdeesha Hi all, I apologize that it's taken a while to get all the issues sorted, fixed and properly verified. I have pushed the corrected version up to my GitHub, and everything seems to be working much better (thanks to the efforts of everyone here)! A big shout out to all of you, as this is exactly how open source is supposed to work! Let me know if there are any other issues that arrise - and Happy Day to one and All!
    • G

      GPU Passthrough

      Watching Ignoring Scheduled Pinned Locked Moved Management
      29
      3
      0 Votes
      29 Posts
      9k Views
      tjkreidlT
      @coolsport00 Sorry about the VMW need for the Cisco product. Sounds like you have a number of constraints, finances being I'm sure one of them! At least you have time on your hands and the means to experiment. You may, als, end up with a number of different platforms to meet your needs. We ran both Sun Microsystems and Red Hat Linux and Microsoft Windows servers, each taking on specific duties. It's far from ideal and probably not very cost-effective, but you do what you have to to get stuff to work.
    • acebmxerA

      XOA 6.9 Update

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      9
      1 Votes
      9 Posts
      232 Views
      S
      @MathieuRA We reverted back to 6.8.2 for now. We can wait for patch, otherwise, I have opened a tunnel #38081.
    • A

      Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      114
      0 Votes
      114 Posts
      20k Views
      poddingueP
      Thanks a lot for your feeback, folks!
    • henri9813H

      Cleanup orphans backups

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      8
      0 Votes
      8 Posts
      302 Views
      P
      @johnnezero Hi, Sorry, it seems it is only in Rest API for now: You can check it here: <xoa-url>/rest/v0/docs/#/backup-repositories/ReclaimSpaceBackupRepository
    • J

      DRBD reactor metrics in k8s

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      7
      3
      0 Votes
      7 Posts
      360 Views
      J
      @poddingue Turns out it is all secondary-to-secondary out of sync. So that makes it less intense, though if primary dies I wonder how it will resolve this, or if it will become split brained. Still unsure of how it happened, but the ones I manually cleaned up have not come back. Going to continue to manually clear them up. If it happens again I will have an alert setup to notify me, and I have all the xcp-ng logs and everything to be able to see what happened. If that happens I will post here with details and logs for the resource so we can see how it occurs. [image: image.jpeg]
    • F

      XOA 6.8 Pool Metadata backup

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      7
      0 Votes
      7 Posts
      479 Views
      F
      @poddingue This was fixed a number of weeks ago via a ticket. I believe @florent may know the exact fix.
    • D

      XCP-ng Windows PV tools announcements

      Watching Ignoring Scheduled Pinned Locked Moved News
      116
      0 Votes
      116 Posts
      43k Views
      olivierlambertO
      Great, thanks for the feedback @yomeyo !
    • F

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

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved 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