Subcategories

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

    427 Topics
    3k Posts
    P
    In case anyone wonders how this played out. At the end of the day, I shutdown the host with the running workloads on it, kept it at BIOS boot so the 8.3 installer would upgrade it cleanly, and then booted it back up. For reasons related to my particular setup, the down time was more than 60 minutes. But that's not related to XCP-ng. The XCP-ng installer was maybe 10 of that. 20 of that was 3 reboots on a server that takes ages to boot. One thing that is a bit difficult is that the 8.3 installer doesn't notice ZFS volumes or help with ZFS. So after the upgrade, I have to follow a modified set of these instructions (modified because the package names have changed over time) to install ZFS and its components into the system. So the sequence is: Shutdown Install via ISO Reboot to single user mode Run yum update to pull in all the updates Run the ZFS commands to install ZFS on the host Reboot again Run normally Of course, I ended up rebooting more than just those 2 times, because I forgot that I would need to install ZFS (even though I did it on 2 different hosts already ) So now the pool is fully upgraded, everybody is happy. I'm now working on creating shared storage across the nodes. It's amateur hour over here. I appreciate all the help.
  • ACLs, Self-service, Cloud-init, Load balancing...

    97 Topics
    818 Posts
    olivierlambertO
    October release fixed it
  • All XO backup features: full and incremental, replication, mirrors...

    439 Topics
    4k Posts
    P
    source host : xe host-param-list uuid=161be695-e1f9-4271-b581-27b716fde9a5 |grep xapi software-version (MRO): product_version: 8.3.0; product_version_text: 8.3; product_version_text_short: 8.3; platform_name: XCP; platform_version: 3.4.0; product_brand: XCP-ng; build_number: cloud; git_id: 0; hostname: localhost; date: 20250909T12:59:54Z; dbv: 0.0.1; xapi: 25.6; xapi_build: 25.6.0; xen: 4.17.5-15; linux: 4.19.0+1; xencenter_min: 2.21; xencenter_max: 2.21; network_backend: openvswitch; db_schema: 5.786 DR target host : xe host-param-list uuid=e604c3bf-373c-489b-b191-edecbabec43f |grep xapi software-version (MRO): product_version: 8.3.0; product_version_text: 8.3; product_version_text_short: 8.3; platform_name: XCP; platform_version: 3.4.0; product_brand: XCP-ng; build_number: cloud; git_id: 0; hostname: localhost; date: 20250909T12:59:54Z; dbv: 0.0.1; xapi: 25.6; xapi_build: 25.6.0; xen: 4.17.5-15; linux: 4.19.0+1; xencenter_min: 2.21; xencenter_max: 2.21; network_backend: openvswitch; db_schema: 5.786
  • Everything related to Xen Orchestra's REST API

    75 Topics
    571 Posts
    F
    @MathieuRA Thank you, perfect Br,
  • Terraform, Packer or any tool to do IaC

    45 Topics
    427 Posts
    CyrilleC
    Terraform provider release v0.37.0 Enables the secure boot parameter for the VM resource Terraform provider release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.0
  • Scaling Xen Orchestra Host

    2
    0 Votes
    2 Posts
    423 Views
    olivierlambertO
    Hi, "It depends" is the answer here Depends on: the number of concurrent users on your XO instance the size/frequency/number of backup jobs you have the number of hosts and VMs managed by XO Frankly, for a small setup (less than 4/5 hosts) with one users and few backup jobs, the default 2vCPU/2GiB RAM is enough. Especially since we improved various process to happen in a dedicated worker
  • Delta Backup Fails for a Single VM - ENOTDIR (.vhd/chunk-filters.json)

    4
    0 Votes
    4 Posts
    485 Views
    olivierlambertO
    That's why a XOA will be helpful, so a simple support tunnel will do the trick
  • Restoring Full Backup Error: Stream_vdi.Invalid_checksum

    10
    0 Votes
    10 Posts
    1k Views
    florentF
    @lawrencesystems We added the healthcheck for full backup (here : https://github.com/vatesfr/xen-orchestra/pull/6401 ) Also we removed our js smb implementation ( https://github.com/vatesfr/xen-orchestra/commit/b50e95802c6a876d4e6ffd0c62c209a187b1bfb2 ) to try to circumvent the strange samba comportment fbeauchamp opened this pull request in vatesfr/xen-orchestra closed fix(backups): add healthcheck to full backup #6401 0 julien-f committed to vatesfr/xen-orchestra feat(fs): remove JS based SMB handler It's not well tested nor maintained.
  • Why does df -h produce a different disk size than in XO / XOA?

    4
    0 Votes
    4 Posts
    860 Views
    olivierlambertO
    There's no black magic As @ronivay said, you need to tell the filesystem inside your VM that the disk grew. On Cloudinit-enabled VM, there's an auto-grow parameter that is checking at each boot if the disk was extended, and will automatically do it for you. But again, that's inside the VM. Keep in mind: it's not the job of the virtualization system to deal with what's inside the VM
  • how to see which user created a vm snapshot?

    2
    0 Votes
    2 Posts
    387 Views
    ronivayR
    Settings -> audit. Assuming you have it enabled. If not, nowhere afaik.
  • 0 Votes
    3 Posts
    2k Views
    A
    @Darkbeldin I totally missed that.... I know I have used it before. It must be a long week already. Thanks.
  • Netdata plugin

    12
    0 Votes
    12 Posts
    2k Views
    olivierlambertO
    That would be nice if you open a support ticket with a support tunnel so we can take a look remotely
  • No Hosts Available When Creating New VM

    5
    0 Votes
    5 Posts
    6k Views
    K
    @olivierlambert Thanks for that information, will use it next time I run into the issue. Before I read your above reply, I was poking around and noticed that the only SR I had added was disconnected, somehow. So I researched into it and discovered that this was my own doing. Without going into too much detail, I had converted my Active Directory environment from a Zentyal server to a Windows Server and I was hosting the SMB share on the old domain controller. So I had made a DNS error which was causing the SR to not be reachable from the XCP-ng host. So I deleted the SR and recreated it and viola I was able to create the VM. Honestly, I'm not sure how the two are connected since I'm not storing any disks on this SR; I only use it for ISOs which I mount into the newly created VM to install an OS and then I eject it. Long story short, my problem is solved but I'm still confused as to how it happened.
  • Pool Metadata Backup in XO throwing a Redis Configuration Error

    Solved
    5
    0 Votes
    5 Posts
    1k Views
    olivierlambertO
    As stated in the big warning yellow box here in the official doc: https://xen-orchestra.com/docs/community.html#report-a-bug Closing then
  • Rolling Snapshot not work on xo-server 5.103 and xo-web 5.104

    Solved
    3
    3
    0 Votes
    3 Posts
    351 Views
    L
    @olivierlambert I'm rebuild to xo-server 5.103.1, It's working now ,thanks [image: 1665913661236-9e807578-8296-4fc9-aa81-8afaf1e4f52b-image-resized.png]
  • Editing a Remote always fails

    7
    0 Votes
    7 Posts
    1k Views
    florentF
    @mjtbrady compression is used ( brotli, fastest mode by default) There is a problem on the size reported especially with encryption. I will add a task to the backlog to fix it (there is padding with encryption, that complexify the maths)
  • Storage not connecting, VMs stuck in state and unable to get back.

    14
    2
    0 Votes
    14 Posts
    5k Views
    olivierlambertO
    Indeed, if your other hosts are somehow dead/unresponsive from XAPI perspective, ejecting them from the pool is an option to get your master booting those VMs
  • Restore File - Long filenames not displayed correctly

    8
    1
    0 Votes
    8 Posts
    1k Views
    M
    @pdonias I am puzzled. What do you see? To be clear there are two problems. The selected directory truncates the directory name at around 46 characters ("/var/lib/docker/containers" in my original screen shot isn't truncated because it isn't that long). "Long" file/directory names in the "Select a file" drop down do not display correctly. Once a file has been selected, the "Selected files/folders" does show it in a scrollable "widget" that can then be used to see the full file name. My screen shots are from Chrome on Fedora. I normally use Fedora/Firefox which has the same issues. I set up the following as a test. Filename lengths are 10-80 characters long. root@debian42:~/testdir# pwd /root/testdir root@debian42:~/testdir# ls -l total 0 -rw-r--r-- 1 root root 0 Oct 7 09:50 1234567890 -rw-r--r-- 1 root root 0 Oct 7 09:50 12345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:50 123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:50 1234567890123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:50 12345678901234567890123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:51 123456789012345678901234567890123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:51 1234567890123456789012345678901234567890123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:51 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Filename lengths 10-50 display. Filename lengths 60-80 do not. [image: 1665091374720-screenshot-from-2022-10-07-10-22-26.png]
  • Exports OVA Timeout...

    37
    0 Votes
    37 Posts
    13k Views
    S
    @olivierlambert i did update xoa again but no dice, i was wanting to export a couple VM's and do a head to head iscsi I/O test between vmware and xcp on identical hardware but not having much luck trying to get my VM's out of xcp. Guess I'll have to wait for this to work possibly.
  • Email Notification Alerts

    8
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    You can open an issue on XCP-ng repo here: https://github.com/xcp-ng/xcp/issues Just check before if you can already have the temps from the dom0
  • Error: couldn't instantiate any remote

    33
    0 Votes
    33 Posts
    10k Views
    olivierlambertO
    Oh wow, you were lucky indeed! Happy to know you are safe
  • Restore fails with import_error

    9
    0 Votes
    9 Posts
    1k Views
    H
    @olivierlambert Thank you Olivier, posting it here can maybe help somebody else who does the same mistake
  • XO Backup Failing - Possibly to due Local Disks and loopback issues?

    7
    0 Votes
    7 Posts
    1k Views
    DanpD
    @MichaelCropper said in XO Backup Failing - Possibly to due Local Disks and loopback issues?: Job canceled to protect the VDI chain This usually indicates that there are VDIs that haven't coalesced. Check the "unhealthy VDIs" section of Dashboard > Health.
  • XO Remote mount.nfs: access denied by server while mounting

    26
    0 Votes
    26 Posts
    10k Views
    P
    @daninmanchester Thanks so much - this is the exact same problem I had, which was further complicated by running XO in Docker running on the OMV host exporting the NFS shares. So basically you just built a small XO VM instead of running it in Docker? I had originally been thinking of making a small VM to run XO in a container there - just because Docker containers are super easy to keep updated and I could run some other orchestration-y stuff there too, like Rancher - but if you're saying that's a non-starter I'll just bite the bullet and build a tiny VM dedicated to XO and be very grateful to you for having saved me a lot of frustration.
  • Wrong paths at pool's storage

    1
    1
    0 Votes
    1 Posts
    121 Views
    No one has replied