Subcategories

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

    446 Topics
    3k Posts
    gskgerG
    I am running NVIDIA P40s on a DELL R720/R730 and a NVIDIA A2000 12GB on a DELL Optiplex 9010 in my playlab. Getting the GPUs to be accessible for VMs was quite easy: shutdown the XCP-ng host, install the GPUs, start the host again, activate the GPU in the advanced settings of the host in the PCI Devices section (“Passthrough enabled”). The host will restart at this point after displaying a warning. That's it – the GPU can now be assigned to a VM in the VMs advanced settings. I do use the GPUs for AI workloads under Debian though, so your use case might vary.
  • ACLs, Self-service, Cloud-init, Load balancing...

    98 Topics
    825 Posts
    D
    @bleader Hopefully the palm print on my forehead isn't visible from where you are sitting. Of course the interface needs an IP address. In my defense, normally for something like this, I wouldn't put it on the bonded interface with all the trunked VLAN's for guest traffic (we don't give that one an IP) and it would go on the other bonded interface that isn't trunked and does get an IP, but these are test hosts and I didn't set up the other bond, so it is pulling double duty. I was able to set the IP's and get SDN working. Thanks!
  • All XO backup features: full and incremental, replication, mirrors...

    459 Topics
    5k Posts
    P
    so, I stopped rebooting my XOA everyday [image: 1770450390599-6c5ad7ea-5c6a-4fe9-88bf-58c69406edd4-2542a03d-3948-429f-8089-7eab68cf592e.png] just patched 6.1.1, it restarted xo-server [image: 1770450434127-b7adabb8-4d4f-4805-8b25-ddbedffe5cc0-cc0c1cce-6950-4f3c-b328-2e6d9d4889c7.png] guess I'll have to let it disabled for 48h to see if with new patch, RAM is still ramping up. will report back.
  • Everything related to Xen Orchestra's REST API

    76 Topics
    578 Posts
    R
    @Pilow tags can work and the path to them is much more succinct. Thanks!
  • Terraform, Packer or any tool to do IaC

    49 Topics
    445 Posts
    T
    Offering feedback that my implementation of the XO CCM (v1.0.0-rc.1) into my K8s cluster was successful; I validated that the nodes were labeled as expected. I attached screenshots from Rancher and the CLI. In my lab, I use OCNE 1.9 (Oracle Cloud Native Environment) on Oracle Linux 9.7. In my setup, I edited the kubeadm-config ConfigMap and on all nodes added the Kubelet argument for the cloud provider. I restarted the Kubelet on all nodes and then deployed the CCM via Method 1 per the documentation From my setup to set the cloud-provider: kubectl edit cm kubeadm-config -n kube-system apiServer: extraArgs: cloud-provider: external controllerManager: extraArgs: cloud-provider: external sudo vim /etc/sysconfig/kubelet KUBELET_EXTRA_ARGS="--fail-swap-on=false --cloud-provider=external" sudo systemctl daemon-reload && sudo systemctl restart kubelet [image: 1770418969929-rancher_xo_ccm_labels-resized.png] [image: 1770419178223-ocne_xo-ccm_pod.png]
  • Backup timeout with compresion

    6
    0 Votes
    6 Posts
    518 Views
    GheppyG
    Is there any option to set for timeout value? I say this because, monitoring the process, everything seems to be going well until the moment when it starts to check the free space. XCP-NG is 8.2 up to date, the disk on which the VM is it is formated as local ext. The connection to the backup server is on NFS on the LAN at a speed of 1Gb. On the iotop it seems that the space check goes with speed 650Gbits +.
  • Migrating VM fails with DUPLICATE_VM error part2

    47
    0 Votes
    47 Posts
    20k Views
    A
    @darkbeldin For the record, both vm's were running on the same esxi host when exported. This may or may not be a factor (I suspect it is).
  • Slow XOA VM download (~250KBps)

    7
    0 Votes
    7 Posts
    2k Views
    B
    @olivierlambert I've dug into the issue a bit more, and it just gets stranger. Downloading to my Macbook on the same network gets ~4MB/s. This means there is something strange going on with the control domain around remote downloads. When I test the disk speed (which is an Samsung NVMe), the speed is 1.7GB/s: [14:31 xcp-host ~]# dd if=/dev/zero of=testfile oflag=direct bs=1M count=5000 status=progress 4998561792 bytes (5.0 GB) copied, 3.000607 s, 1.7 GB/s 5000+0 records in 5000+0 records out 5242880000 bytes (5.2 GB) copied, 3.15049 s, 1.7 GB/s When I test the network speed with Ookla's speedtest-cli it confirms a 1G connection, and a 1G transit to Europe (checked this twice because 1G Atlantic transits are rare): [14:44 xcp-host ~]# speedtest -s 2023 Speedtest by Ookla Server: LaFibre.info - Lyon (id = 2023) ISP: Bell Canada Latency: 108.05 ms (0.49 ms jitter) Download: 960.47 Mbps (data used: 1.5 GB ) Upload: 172.11 Mbps (data used: 293.4 MB ) Packet Loss: 0.0% Result URL: https://www.speedtest.net/result/c/b8f1da9f-5c57-4ad8-ad3b-729e1625affe On my Macbook (on 802.11ac) I can download an Ubuntu image at ~14MB/s ➜ wget http://ubuntu.mirrors.ovh.net/ubuntu-releases/21.10/ubuntu-21.10-desktop-amd64.iso --2021-11-16 14:49:41-- http://ubuntu.mirrors.ovh.net/ubuntu-releases/21.10/ubuntu-21.10-desktop-amd64.iso Resolving ubuntu.mirrors.ovh.net (ubuntu.mirrors.ovh.net)... 213.32.5.7 Connecting to ubuntu.mirrors.ovh.net (ubuntu.mirrors.ovh.net)|213.32.5.7|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3116482560 (2.9G) [application/octet-stream] Saving to: ‘ubuntu-21.10-desktop-amd64.iso’ ubuntu-21.10-desktop-amd64.iso 3%[=> ] 107.27M 14.4MB/s eta 4m 14s However on the control domain the download speed is considerably lower: [14:52 xcp-host ~]# wget http://ubuntu.mirrors.ovh.net/ubuntu-releases/21.10/ubuntu-21.10-desktop-amd64.iso --2021-11-16 14:53:03-- http://ubuntu.mirrors.ovh.net/ubuntu-releases/21.10/ubuntu-21.10-desktop-amd64.iso Resolving ubuntu.mirrors.ovh.net (ubuntu.mirrors.ovh.net)... 213.32.5.7 Connecting to ubuntu.mirrors.ovh.net (ubuntu.mirrors.ovh.net)|213.32.5.7|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3116482560 (2.9G) [application/octet-stream] Saving to: ‘ubuntu-21.10-desktop-amd64.iso.1’ 3% [==> ] 106,910,815 3.20MB/s eta 16m 47s Have you ever see something like this before? I saw you had some discussion on another thread regarding slow writes in a VM, but this looks like it affects the control domain as well: https://xcp-ng.org/forum/topic/4865/slow-disk-writes-inside-vm-on-8-2
  • Host Time with wront time, but timezone is OK

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    Well, it's a bit hard to tell you directly what to do vs XOA, because on XOA you are already on a validated OS (Debian) with some packages installed. On which OS did you install Xen Orchestra in the first place?
  • Interrupted backups left on destination

    Solved
    3
    0 Votes
    3 Posts
    541 Views
    julien-fJ
    Sorry for the huge delay, I just stumbled on this thread It's indeed the case now, XO automatically check the integrity and clean any unused files in VM directory on a remote when that VM is backed up.
  • After reboot all vms hanged.

    2
    0 Votes
    2 Posts
    441 Views
    olivierlambertO
    Hi, Try to disable/enable back the auto power on for one VM, and try again.
  • Commands in Xen Orchestra Jobs no longer working

    5
    0 Votes
    5 Posts
    1k Views
    T
    @olivierlambert said in Commands in Xen Orchestra Jobs no longer working: The best solution is to rely on XOA, you know I agree with @olivierlambert! Personally, I'm using XO from sources in my home lab environment -- nothing is "production" and I'm mostly having fun trying to give back to the open source community.
  • always getting "unhealthy VDI chain"

    3
    0 Votes
    3 Posts
    1k Views
    I
    @Danp - thank you. Yes, I did, but that was not helping in this case. Found the solution: Both machines are on a hostserver, which has NOT all networks. So the real reason must be a network problem, therefore a quite missleading error message After moving both VMs to the master of this pool (which is connected to the same network where the xoa resides), everything went fine. Same storage, same vhds.
  • Backing up to NFS share on ZFS

    9
    0 Votes
    9 Posts
    2k Views
    IndyJI
    @indyj The file restore issue was due to installing XO on FreeBSD (fine for VM restores, not file extraction). I then installed XO on Ubuntu 20, and this worked for restoring files from Linux VMs but not Windows VMs. Then I installed on CentOS 8 and had the same problem as Ubuntu. I then installed on Fedora 34 and everthing works fine.
  • Backblaze B2 as a backup remote

    7
    0 Votes
    7 Posts
    2k Views
    olivierlambertO
    Just hold on for this month release
  • Automatic backup verification

    feature in backlog
    11
    1 Votes
    11 Posts
    3k Views
    julien-fJ
    Yes, it should be safe enough to try importing the backup, then starting the VM without network (ie VIFs) and see if it stays up for a few minutes. I think we could start by adding a manual feature and then see in a second step how we could automate it.
  • XOCE Integration with OpenLDAP

    41
    0 Votes
    41 Posts
    15k Views
    olivierlambertO
    Also, the user will be created only on first connection. Maybe you are thinking about the plugin in a way that's not how it behave.
  • Restored Backups Do Not Boot

    backup
    8
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    Sure, please keep us posted on your experiments If it's a bug, we'll have more info to be able to work on it!
  • XOA Report

    3
    0 Votes
    3 Posts
    673 Views
    A
    @olivierlambert many thanks for the very quick response, it is indeed XO from sources. I think the burst explanation makes sense. Also, thanks for you and your teams continued development and support with both XCP-NG and XO.
  • Backups failed after changing masters?

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Source: https://github.com/vatesfr/xen-orchestra/issues/5969 olivierlambert created this issue in vatesfr/xen-orchestra closed Save all associated host IPs to a pool and use them as fallback for XAPI connection #5969
  • Lots of Tasks: Xapi#getResource /rrd_updates (on **masterhost**) 0%

    19
    0 Votes
    19 Posts
    3k Views
    stormiS
    And the IRC channel is #xcp-ng on oftc.net if you prefer IRC.
  • Usage of job.run.Sequence

    6
    0 Votes
    6 Posts
    823 Views
    F
    Hi, thank you for your support. I was out of Office for two weeks and will test this soon. I will give you feedback. Regards, Torsten
  • Jobs

    Solved
    5
    0 Votes
    5 Posts
    989 Views
    D
    Thank you for your help this is the solution i was searching for, I appriciate this much.
  • Missing information in XOA 5.64 blog post

    4
    0 Votes
    4 Posts
    748 Views
    olivierlambertO
    What do you mean "how it works"? It's the same thing than before, just "isolated" from the rest, working in a... worker. And yes, the long run objective is the ability to run it as a service on the remote directly, reducing a lot the merge time (because latency is the worst enemy of merging).
  • Backup does not work if one host in the pool is offline

    12
    0 Votes
    12 Posts
    2k Views
    ForzaF
    @olivierlambert said in Backup does not work if one host in the pool is offline: When you connect to a working, machine, yes it does But XAPI connection isn't persistent: it means, when the pool is disconnected, XO has no recollection whatsoever on who was the "real" master the last time it was connected. The only info we store is the IP address you entered in Settings/server. I agree, functionally speaking, it can be limiting in your case. A viable option would be to save all existing hosts IPs in the XO database, as fallback if we can't connect to the IP you entered. This is not a very common case, that's why it wasn't done before Looks like a good suggestion. Thanks. In my case I migrated everything from the poolmaster to the second host, then changed the second host to pool master, waited an hour and then shut down the old pool master (now just a pool member). XOA was online during the entire process and I had forgotten to check the server list.