Subcategories

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

    362 Topics
    3k Posts
    A
    @TITUS-MAXIMUS --get-dom0 being empty means no PCI devices were hidden from dom0 either, did you follow this step of the guide? https://docs.xcp-ng.org/compute/#2-tell-xcp-ng-not-to-use-this-device-id-for-dom0
  • ACLs, Self-service, Cloud-init, Load balancing...

    89 Topics
    763 Posts
    R
    I see your point. Thank you!
  • All XO backup features: full and incremental, replication, mirrors...

    364 Topics
    4k Posts
    R
    @florent Great work, thanks for the fixes
  • Everything related to Xen Orchestra's REST API

    64 Topics
    492 Posts
    MathieuRAM
    This is normal, as the tasks endpoints are in the old REST API (undocumented by Swagger). We are gradually migrating to the new REST API to document all endpoints.
  • Terraform, Packer or any tool to do IaC

    33 Topics
    309 Posts
    I
    @olivierlambert @nathanael-h @Team-DevOps Please let me know if you have answers for any of the flollowing questions: Why JSON-RPC over websocket regularly returns not expected result for calls and what could be done with it? examples: method xo.getAllObjects sometimes returns empty result, but following: jsonrpc method params ------- ------ ------ 2.0 all @{type=enter; items=} On retry - everything is fine and we have all data jsonrpc result ------- ------ 2.0 @{bbdb1ed0-4c86-24ec-...=;..... method vm.copy sometimes returns only task with name_label host.get_server_certificate and no task async.vm.copy. Meanwhile copy operation is started in XEN Orchestra, so we have to separately search for the task currently running in all objects and if it is not there anymore suggest that it completed successfully. Afterwards we need to check if vm was copied and appeared in all objects. That is really frustrating as we have no info about successfully completed tasks in XEN - records just removed as nothing happen. most likely this happens due to other tasks being popped up in tasks at the same time and websocket call recives not its own responce, is it possible to workaround? What is correct syntax for JSON to run job.create method? Are there any article with supported methods for JSON-RPC calls and examples to use them? Calling for "system.getMethodsInfo" I can see "job.create": { "description": "Creates a new job from description object", "params": { "job": { "type": "object", "properties": { "userId": { "type": "string", "optional": true }, "name": { "type": "string", "optional": true }, "timeout": { "type": "number", "optional": true }, "type": { "type": "string" }, "key": { "type": "string" }, "method": { "type": "string" }, "paramsVector": { "type": "object", "properties": { "type": { "type": "string" }, "items": { "type": "array", "items": { "type": "object" } } }, "optional": true } } } }, "permission": "admin" }, But it is unclear what values should I provide to paramsVector and looking into the job created manually (in web interface) with method job.getall I can see 2 jobs [ { "type": "call", "name": "copyvm", "key": "generictask", "method": "vm.copy", "paramsvector": { "type": "crossproduct", "items": [ { "type": "set", "values": [ { "name": "nevm", "vm": "GUID", "sr": "GUID" } ] } ] }, "userid": "GUID", "id": "GUID" }, { "method": "vm.copy", "key": "vm.copy", "name": "copyvmjob", "type": "call", "userid": "GUID", "id": "GUID" } ] How can I create similar job myself if it is not possible to find out why vm.copy does not return async.vm.copy task info?
  • Xen Orchestra Backups

    Solved
    5
    0 Votes
    5 Posts
    382 Views
    jbamfordJ
    @danp Okay that's great. I was just making sure. Thanks for your reply. Jack
  • SR_BACKEND_FAILURE_109

    36
    0 Votes
    36 Posts
    3k Views
    N
    We did recently have a failed drive that finished rebuilding a few days ago.
  • Issue creating Ubuntu 18.04 desktop VM

    Solved
    25
    0 Votes
    25 Posts
    8k Views
    Dr4s1l 0D
    @olivierlambert i'm using a ova import with UEFI comming from virtualbox, folowed all previous option and ddocumentation and still can't get my VM to boot. It's stuck with black screen and no network or whatever informations. Using this packer template to build the VM : { "variables": { "vm_name": "mjolmir-base", "cpu": "2", "ram_size": "2048", "disk_size": "5000", "iso_url": "ubuntu-18.04.5-server-amd64.iso", "iso_checksum_type": "sha1", "iso_checksum": "c5dc820b3b46ccdd94bb1568715852ea3bf772a4", "username" : "vagrant", "password" : "vagrant" }, "builders": [ { "vm_name":"{{user `vm_name`}}", "type": "virtualbox-iso", "format": "ova", "output_directory": "./data", "boot_wait": "5s", "disk_size": "{{user `disk_size`}}", "headless": true, "guest_additions_mode":"disable", "http_directory": "./http/", "iso_url": "{{user `iso_url`}}", "iso_checksum": "{{user `iso_checksum`}}", "communicator":"ssh", "ssh_username": "{{user `username`}}", "ssh_password": "{{user `password`}}", "ssh_timeout": "4h", "shutdown_command": "echo 'vagrant' | sudo -S -E shutdown -P now", "boot_command": [ "e<down><down><down><down><down><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", "linux /install/vmlinuz<wait>", " auto<wait>", " console-setup/ask_detect=false<wait>", " console-setup/layoutcode=us<wait>", " console-setup/modelcode=pc105<wait>", " root=/dev/sda", " debconf/frontend=noninteractive<wait>", " debian-installer=fr_FR<wait>", " vga=normal fb=false<wait>", " kbd-chooser/method=fr<wait>", " keyboard-configuration/layout=FR<wait>", " keyboard-configuration/variant=FR<wait>", " locale=fr_FR<wait>", " netcfg/get_domain=localdomain<wait>", " netcfg/get_hostname=mjolmir<wait>", " grub-installer/bootdev=/dev/sda<wait>", " noapic<wait>", " preseed/url=http://{{ .HTTPIP }}:{{ .HTTPPort }}/http/18.04/preseed-cloud-init.cfg", " -- <wait><enter>", " initrd /install/initrd.gz<wait>", "<f10>" ], "guest_os_type": "Ubuntu_64", "firmware":"efi", "iso_interface": "sata", "vboxmanage": [ [ "modifyvm","{{.Name}}","--memory","{{user `ram_size`}}" ], [ "modifyvm","{{.Name}}","--cpus","{{user `cpu`}}" ], [ "modifyvm","{{.Name}}","--firmware","EFI" ] ] }], "provisioners": [{ "type": "shell", "execute_command": "echo 'vagrant' | sudo -S -E sh {{.Path}}", "scripts": [ "./script/update.sh", "./script/cloud-init.sh", "./script/cleanup.sh" ] }], "post-processors": [ { "keep_input_artifact": true, "output": "../../{{.Provider}}/mjolmir.box", "type": "vagrant" } ] } with provisioning script : #!/bin/sh #Disable conflict service systemctl stop apt-daily.service systemctl kill --kill-who=all apt-daily.service wait until `apt-get updated` has been killed while ! (systemctl list-units --all apt-daily.service | egrep -q '(dead|failed)') do sleep 1; done #Disable service at startup systemctl mask apt-daily.service apt-daily-upgrade.service systemctl disable apt-daily.service apt-daily-upgrade.service systemctl disable apt-daily.timer apt-daily-upgrade.timer # install cloud-init apt-get update && apt-get upgrade apt-get install linux-image-generic xserver-xorg apt-get remove linux-image-generic-hwe-18.04 apt-get install --install-recommends -y cloud-init xe-guest-utilities cloud-initramfs-growroot xserver-xorg-video-all #hostname will be managed by cloud-init, but the current value will not be removed HOSTNAME=`hostname` sed -i "/${HOSTNAME}/d" /etc/hosts sed -i s/enp0s3/eth0/g /etc/network/interfaces sed -i "s/GRUB_CMDLINE_LINUX_DEFAULT=\"quiet\"/GRUB_CMDLINE_LINUX_DEFAULT=\"quiet vga=normal fb=false dsmode\=nocloud\\;s\=\/ratatosk\"/g" /etc/default/grub #sed -i "s/Before\=sysinit\.target/After\=sysinit\.target/g" /etc/systemd/system/cloud-init.target.wants/cloud-init.service #sed -i "s/\[Service\]/\[Service\]\r\nAfter\=\cloud-init.service/g" /lib/systemd/system/xe-daemon.service #sed -i "s/\[Service\]/\[Service\]\r\nExecStartPre\=\/bin\/sleep 30/g" /etc/systemd/system/cloud-init.target.wants/cloud-init.service #sed -i "s/\[Service\]/\[Service\]\r\nExecStartPre\=\/bin\/sleep 30/g" /etc/systemd/system/cloud-init.target.wants/cloud-init-local.service sed -i "s/datasource_list: \[ NoCloud, ConfigDrive, OpenNebula, DigitalOcean, Azure, AltCloud, OVF, MAAS, GCE, OpenStack, CloudSigma, SmartOS, Bigstep, Scaleway, AliYun, Ec2, CloudStack, Exoscale, RbxCloud, UpCloud, None \]//g" /etc/cloud/cloud.cfg.d/90_dpkg.cfg cp /tmp/cloud.cfg /etc/cloud/cloud.cfg && rm /tmp/cloud.cfg cat <<EOF >> /etc/cloud/cloud.cfg.d/90_dpkg.cfg datasource_list: [ NoCloud, None ] datasource: NoCloud: seedfrom: /ratatosk/ EOF update-grub mkdir /ratatosk echo "/dev/xvdb /ratatosk vfat defaults 0 2" >> /etc/fstab DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force dpkg-reconfigure -f noninteractive cloud-init stuck on : [image: 1629388720596-034b3235-383a-4aec-8a72-52bc9fb8c9ea-image.png] Any suggestion or whatever i'm missing ? Ubuntu 16.04 OVA created the same way can be imported and booted flawlessly.
  • Need help getting backups configured

    7
    0 Votes
    7 Posts
    807 Views
    olivierlambertO
    On a thin volume, it will only use the "real" space in the VM, so if you are using 40 or 50GiB, yes it will fit on the 78GiB storage
  • Can a VM be replicated to different locations?

    Solved
    4
    0 Votes
    4 Posts
    529 Views
    mauzillaM
    @olivierlambert thank you Olivier!
  • Netdata collectors from XCP repo

    1
    0 Votes
    1 Posts
    233 Views
    No one has replied
  • XCP-Ng Secure Boot

    community
    5
    0 Votes
    5 Posts
    3k Views
    stormiS
    Both secure boot support and the fix for this KB installation are now available for testing: https://xcp-ng.org/forum/post/41541
  • Sources upgrade - can't restore backups ('invalid parameters')

    14
    0 Votes
    14 Posts
    903 Views
    olivierlambertO
    FYI, you can always ask for another XOA trial when you need it
  • Is there a way to schedule an XVA export?

    6
    0 Votes
    6 Posts
    776 Views
    olivierlambertO
    It's not that complicated: it's in a folder with the UUID of the backup job, then the VM is within it's UUID folder. That's it.
  • Metadata backup doesn't include backup jobs?

    5
    0 Votes
    5 Posts
    597 Views
    DarkbeldinD
    @zevgeny Hi, You can export the config for your XOA in Settings > Config > Export and import it on your new XOA
  • backup fail after last update

    14
    0 Votes
    14 Posts
    1k Views
    T
    @joearnon Can you post logs of both backup instances (of the same job) that ran, see if they are different and in which way? You can also try to reconfigure the back up job to only a single tag parameter to see if that is the issue.
  • Orchestra / xsconsole mismatch

    1
    0 Votes
    1 Posts
    214 Views
    No one has replied
  • This topic is deleted!

    1
    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • Invalid bin field for "url-loader" when building

    2
    0 Votes
    2 Posts
    5k Views
    L
    Hi Pechkin000, Try this : npm install url-loader yarn install v1.22.11 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... info fsevents@2.3.2: The platform "linux" is incompatible with this module. info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation. info fsevents@1.2.13: The platform "linux" is incompatible with this module. info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation. [4/5] Linking dependencies... [5/5] Building fresh packages... Done in 22.66s.
  • How to change the Ip access to a web address?

    Solved
    8
    0 Votes
    8 Posts
    2k Views
    V
    @olivierlambert ah ok ok, sorry..
  • xo-server start on Ubuntu 20.04.2 LTS

    bugs in backlog
    9
    0 Votes
    9 Posts
    2k Views
    K
    @julien-f Apologies, I'm not sure how to do that, but it seems easier to run the server as root instead of these workarounds.
  • XOCE - not working on 10Gb speed

    16
    1
    0 Votes
    16 Posts
    2k Views
    olivierlambertO
    Just change HTTP in the Settings/server to connect to your pools with http://<IP> that's it
  • I have a xen orchestra that won't respond on the xcp center console.

    10
    0 Votes
    10 Posts
    991 Views
    olivierlambertO
    Just a quick FYI, XOA means "Xen Orchestra virtual Appliance" and it's only available via https://xen-orchestra.com or auto deploy. That's the only one with pro support
  • rolling snapshot no appears more on Xen Orchestra

    Solved
    12
    0 Votes
    12 Posts
    1k Views
    olivierlambertO
    Thin will have an active disk only the size used. So instead of using 100GiB, you are using 10GiB, and with a snap, only 10GiB and few KiB.
  • xo-cli can not register

    10
    0 Votes
    10 Posts
    1k Views
    olivierlambertO
    Okay so it's indeed a certificate issue on your side. Double check your certs. Sometimes, you need to have a cert file with the intermediate authority.