• XO Tasks - backups just pilling up

    Unsolved Management
    4
    1
    0 Votes
    4 Posts
    63 Views
    marcoiM
    as for how long they stay, i been clearing my old ones out manually, so not sure.
  • Cleanup orphans backups

    Unsolved Backup
    8
    0 Votes
    8 Posts
    245 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
  • XOA 6.9 Update

    Xen Orchestra
    8
    1 Votes
    8 Posts
    154 Views
    MathieuRAM
    Issue identified. @spelon If you're using XO from source, you can try this mra-fix-undici-xen-api branch, otherwise, feel free to open a tunnel so I can fix your XOA.
  • Synchronize snapshots

    Backup
    4
    2
    0 Votes
    4 Posts
    92 Views
    poddingueP
    A short label on that step would've saved you the ghost hunt, yes. Since it's a UI change more than a bug, I think https://feedback.vates.tech is where it'd get picked up, ideally with your two screenshots showing "All (8)" against seven VMs.
  • Unclear errors

    Management
    3
    1
    0 Votes
    3 Posts
    25 Views
    Tristis OrisT
    i forgot how i got VM_BAD_POWER_STATE. Probably need to choose multiple VMs from different pools and do a batch migration.
  • 1 Votes
    3 Posts
    55 Views
    D
    @trelane Hello, the bug affects Xen drivers of any 9.0 series (considering the upstream code, it goes back to circa September 2019). 9.2.385 contains the fix, which was merged upstream just this month. The bug also impacts network connections, however to a lesser extent due to its nature. I believe that the bug is also present in XenServer VM Tools 9.6.0 and by extension, older versions of it. We recommend that you switch to the XCP-ng tools whenever possible, also due to its other benefits (fully open source, validated for XCP-ng and optimized for Xen Orchestra).
  • XCP-ng Windows PV tools announcements

    Moved News
    116
    0 Votes
    116 Posts
    43k Views
    olivierlambertO
    Great, thanks for the feedback @yomeyo !
  • Install XO from sources.

    Xen Orchestra
    44
    3 Votes
    44 Posts
    9k Views
    acebmxerA
    @lem2405 No problem. Let me know if you still encounter any issues.
  • HA causes reboot of xcp-ng nodes

    Unsolved Management
    32
    0 Votes
    32 Posts
    832 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.
  • Enable Maintenance Mode = Host Not Enough Memory

    Unsolved XCP-ng
    5
    0 Votes
    5 Posts
    110 Views
    J
    @poddingue Our HA-pool is a 3 host system, yes. I'll add a note about our plans to go paid in that feedback-item. Thanks for the tip. In the meantime, I'm testing and reporting as much as I can. In order to hopefully help the product be better for all. Cheers!
  • PCIe Pass-through lanes and lane performance

    Unsolved Compute
    51
    0 Votes
    51 Posts
    9k Views
    pandusenP
    @stormi I dont doubt that the team works hard. The GPU passthrough support has been of lower priority for a long time, it has been said many times before by the team and Oliver. 99 percent of the dev team is working security and basic hypervisor, and is not prioritized for edge cases. Which i guess that PCI passthrough is for GPUs Please dont ask me to dig up the sources. It has always been the case with Xen.... Proxmox, KVM and vmware has the edge there, and that should be well known. But I would in any case where PCI passthrough for edge cases like the GPU marked kind of is, is not a requirement, Always recommend XCP-ng over the others.
  • [SOLVED] Just FYI: current update seams to break NUT dependancies

    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
  • [dedicated thread] Dell Open Manage Appliance (OME)

    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
  • DRBD reactor metrics in k8s

    XOSTOR
    7
    3
    0 Votes
    7 Posts
    336 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]
  • Slow VM migration on Linstor SR

    Unsolved XOSTOR
    4
    0 Votes
    4 Posts
    205 Views
    K
    @ronan-a For testing purposes, I did the following: I created a VM on the local SR of a host, installed Linux on it, and configured an ISCSI target. I then added that ISCSI target as an ISCSI SR within xcp-ng pool, and created a small VM on that repository, using XO. While the machine was running, I performed a migration without losing a single ping.I assume this confirms my previous assertion regarding the use of a standard storage system.
  • Piraeus operator 2.12.0 does not work on current xostor version

    Unsolved XOSTOR
    4
    3
    0 Votes
    4 Posts
    144 Views
    poddingueP
    Thanks, @Jonathon !
  • V2V migrated VMs don't autostart

    Unsolved Migrate to XCP-ng
    6
    1 Votes
    6 Posts
    201 Views
    J
    @poddingue Thanks for taking a look. Yes it is this part that tells me that it should start the VM automatically once the import has completed. "After the transfer, the VM on XCP-ng side is started:" Followed by, "This process is fully automated, without any human intervention after it starts on step 1." [image: image.jpeg] https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/ But my findings/experience is that the VM does not start once the import/transfer has completed. So either the docs are wrong. Or the function is not behaving as intended. I'm acctually fine either way. As long as I know what to expect. However, I would like to have it auto-start the VMs after transfer completion. Which would make the procedure "Fully automated". Update: Am I assuming correctly that "the XO V2V guide says to start the VM yourself once the migration is complete " you're reffering to, is part of the "test migration"-procedure? Not the acctual production mgiration? Because: "Final migration Run the production migration When you're ready for the final migration: Shut down the source VM completely. Start the V2V migration in Xen Orchestra with the Stop source option enabled. This ensures the final sync happens while the VM is powered off, and prevents any inconsistencies." In my mind doesn't state that the VM should be started manually post-transfer. Great thanks in advance for discussing! Cheers!
  • XCP-ng 8.3 updates announcements and testing

    Pinned News
    682
    1 Votes
    682 Posts
    694k Views
    TeddyAstieT
    @leroyj We already know that our k10temp module doesn't have support beyond Zen 2, and needs to be updated. That's not incredibly complex, but still needs to be done. I was wondering if the amd cpu temp be probed the way you did for the intel cpu. No, AMD temperature infos are not exposed through MSR but through PCIe/MMIO (through various subsystems, like "SMU" and other ones). Like what does https://github.com/torvalds/linux/blob/master/drivers/hwmon/k10temp.c or https://github.com/ocerman/zenpower. (regarding the AI draft, there is no documented MSR 0xc0010292 in neither APM nor public Zen3 PPM) That doesn't require any specific Xen support aside the right Linux drivers in Dom0.
  • Reducing vCPU isn't done live on Windows

    Solved XCP-ng
    4
    0 Votes
    4 Posts
    138 Views
    olivierlambertO
    I wasn't even aware about this being a Windows limitation by itself
  • Why are transfer sizes different between XO5 & XO6?

    Solved Backup
    17
    2
    0 Votes
    17 Posts
    586 Views
    JorisKJ
    Wonderful !