Subcategories

  • VMs, hosts, pools, networks and all other usual management tasks.

    490 Topics
    4k Posts
    Z
    @poddingue said: Thanks for posting the fix. The same thing came up in an older thread, https://xcp-ng.org/forum/topic/9957, where disabling IPv6 also made xoa check go green. @HamiltonWDS explained a likely reason in https://xcp-ng.org/forum/post/87831: Node tries the addresses with a short timeout and can end up on the IPv6 one. Your curl -6 test helps a lot here, because it shows IPv6 doesn't connect at all on that network, so it's more than a slow path. Turning it off in XOA seems reasonable if you don't use IPv6 there; if you do, I'd guess the router side is where it really needs fixing, though I could be wrong (still haven't migrated to IPv6 myself ). Curious whether it sorts out the Cloud Backup too. XOA is using our management network where ipv6 is not needed and not enabled. Looks like our cloud backup finally ran for the first time in while too.[image: cloudbackup.jpg]
  • ACLs, Self-service, Cloud-init, Load balancing...

    106 Topics
    870 Posts
    D
    I ran into the same problem with DR replicas. Ignoring VMs by tag would solve the problem, but so would excluding the ip address information.
  • All XO backup features: full and incremental, replication, mirrors...

    538 Topics
    6k Posts
    johnnezeroJ
    @pierrebrunet Thanks for the update. So is there any way to run the reclaimSpace function (i.e from the XO CLI or something, without having to build a whole REST API application or whatever that involves)?
  • Everything related to Xen Orchestra's REST API

    88 Topics
    654 Posts
    poddingueP
    Pretty cool, @samuelolavo, thanks for clarifying!
  • Terraform, Packer or any tool to do IaC

    52 Topics
    488 Posts
    CyrilleC
    New release ! Cloud Controller Manager v1.2.0 https://github.com/vatesfr/xenorchestra-cloud-controller-manager/releases/tag/v1.2.0 Adds a new cloud-node-out-of-service controller that applies the node.kubernetes.io/out-of-service=nodeshutdown:NoExecute taint to the nodes whose Xen Orchestra VM is halted or has been deleted. More about this feature in the documentation or #90
  • XO - change control domain memory?

    4
    0 Votes
    4 Posts
    3k Views
    olivierlambertO
    I'm not against exposing this in the UI, it might be not that difficult. However, more traction will obviously make it possible
  • XOA VM Export Fail

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    No it's even better to have XOA. So I assume you are on latest and fully up to date? Ping @julien-f
  • [solved] NFS on XO failing, on Center has no issues

    24
    0 Votes
    24 Posts
    18k Views
    olivierlambertO
    No problem, it happens.
  • XO from sources - plugins

    3
    1
    0 Votes
    3 Posts
    1k Views
    M
    @Danp super! lol that was exactly it... and funny cause its the same plugin i was looking to have working! Cheers!!!
  • 0 Votes
    8 Posts
    3k Views
    olivierlambertO
    In fact, there's 2 different things: Downloading and unpacking the updates (yum process). This won't change anything right now, because your current updated programs are likely running in memory (Xen, Linux, XAPI…) so only a reboot will make things changed: it's the current update button on the pool view. Evacuating the host, rebooting it to get all the new versions, and migrate back VMs to it (starting by the master) Right now, 1. need to be triggered manually (you must do it otherwise it won't happen: bad if you forgot) but everything else is managed at all hosts of the pool at the same time (good). And 2 is entirely manual. So that's why I wrote this, to get 1. and 2. entirely automated while being safe and giving you reports: https://github.com/vatesfr/xen-orchestra/issues/5286 I have hopes we can deliver a first version (at least from the CLI) for this month release
  • mapping NFS storage from XO fails, but works fine from terminal?

    13
    0 Votes
    13 Posts
    4k Views
    DanpD
    There was a recent commit on Github dealing with NFS mounts. Suggest that you rebuild with the latest source and then try setting up the NFS storage again.
  • Change xoa hostname

    Solved
    2
    0 Votes
    2 Posts
    3k Views
    olivierlambertO
    https://manpages.debian.org/testing/systemd/hostnamectl.1.en.html hostnamectl set-hostname mymachine
  • missing icon on the UI?

    7
    1
    1 Votes
    7 Posts
    2k Views
    olivierlambertO
    If it's not, it's a bug
  • Get VM from <ID>.vhd from Storage-Record

    7
    0 Votes
    7 Posts
    3k Views
    T
    @fluffy-bunny Use this to get your VBDs from each VM xe vm-param-get param-name=VBDs uuid=<vm-uuid> Then to get the name of each VDI file use this xe vbd-param-get param-name=vdi-uuid uuid=<vbd-uuid> But as olivier said, it is much easier to just use XO's disk view of the VM you want, then use the "copy" button to copy its VDI name.
  • 0 Votes
    3 Posts
    2k Views
    N
    Correct, I made changes to pfSense to be my DHCP and DNS Resolver, so had to make that change to the NFS Settings to reflect the Domain Name. Thanks for your help!...
  • Issue with building XO from source on FreeBSD

    8
    0 Votes
    8 Posts
    2k Views
    M
    Seen this too late today but I will give it a whirl tomorrow! Will let know how it went.
  • VM Snapshot Schedules

    Solved
    9
    2
    0 Votes
    9 Posts
    3k Views
    M
    @olivierlambert I posted my issue building on FreeBSD here: https://xcp-ng.org/forum/topic/3788/issue-with-building-xo-from-source-on-freebsd Maybe its better so this doesn't go too offtopic. regarding this question its solved!
  • How do I attach a network to a PIF

    8
    0 Votes
    8 Posts
    5k Views
    K
    @Rocky I'm a little confused I guess. I have a PIF section. There is nothing under my Private Network area. [image: Screen Shot 2020-10-30 at 6.48.50 PM.png]
  • VM Migration Failed & Now Can't Access VM

    12
    0 Votes
    12 Posts
    8k Views
    olivierlambertO
    If migration failed, there's a reason. It's usually stable. Obviously, because your hosts weren't in the pool, a different CPU model can be the problem (they are automatically adapted if they are in the same pool).
  • FreeBSD file restore

    2
    0 Votes
    2 Posts
    560 Views
    olivierlambertO
    I don't this we support UFS right now. If I remember correctly, we got: FAT NTFS ext xfs LVM based
  • Netdata is not available on this appliance, please deploy a new one

    Solved
    3
    0 Votes
    3 Posts
    1k Views
    H
    That updated my Netdata package from 1.23 to 1.26, and now the plugin is working. Thanks!
  • Xen Orchestra TLS minimum version requirement -- How to set?

    Solved
    9
    0 Votes
    9 Posts
    2k Views
    julien-fJ
    @kevdog Not at all, it made us aware that our vendor config was no longer relevant Thank your for your report!
  • Add server, Connection Failed

    Solved
    8
    0 Votes
    8 Posts
    6k Views
    olivierlambertO
    No worries, it happens
  • Cannot take snapshots with XO

    6
    0 Votes
    6 Posts
    2k Views
    G
    X-O Server is 5.51.1 and XO-Web is 5.51.0.
  • XO UI Storage Feedback

    6
    0 Votes
    6 Posts
    1k Views
    badrAZB
    Hi, Remotes and SRs aren't managed the same way by XO. XO is connected directly to the remotes to do some read/write operations, unlike SRs which is connected to them via XCP-ng. So the SRs aren't directly managed by XO, but are managed using the XCP-ngs' XAPI and we are limited to what the XAPI provides as information.