Subcategories

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

    458 Topics
    4k Posts
    C
    I have two PE R630 and one PE R730xd. The two R630s show the IPMI data in XO but the R730xd does not. If I run ipmitool sensor from an ssh session, I get very similar data back on the 730 and 630. This isn't critical to me, just letting you know that there are cases that functioning ipmitool on a Dell does not seem to be enough to show it. There are some differences in the labels. The R730 has "Fan1 RPM", "Fan2 RPM" while the R630 has "Fan1A", "Fan2A", "Fan1B". Most of the other interesting fields seem to have the same names but the order is a bit different and I didn't do an exhaustive comparison. It's very cool that you are surfacing this data now.
  • ACLs, Self-service, Cloud-init, Load balancing...

    102 Topics
    844 Posts
    C
    We are running Xen Orchestra with commit c3dcb and the auth-oidc (v0.4.2) plugin. The users that login are unique and not yet present as local users. The OICD provider is SURF with SRAM: https://www.surf.nl/en/services/identity-access-management/surf-research-access-management They support the following attributes/scopes: https://servicedesk.surf.nl/wiki/spaces/IAM/pages/74226142/Attributes+in+SRAM There are some IPs that need to be accessable: https://servicedesk.surf.nl/wiki/spaces/IAM/pages/74226067/IP+addresses#IPaddresses-OIDC . Outgoing traffic from the server to port 443 is open and works. We did try several settings for the Username field and scopes. For example the following: [image: 1774600482742-plugin-resized.png] This should create a user R123456789 The logging shows the following: mrt 27 09:29:48 vm-xoa xo-server[2641104]: Expected values to be strictly equal: mrt 27 09:29:48 vm-xoa xo-server[2641104]: + actual - expected mrt 27 09:29:48 vm-xoa xo-server[2641104]: + 'undefined' mrt 27 09:29:48 vm-xoa xo-server[2641104]: - 'string' If we change it to: [image: 1774600514661-plugin-2-resized.png] The following shows up: mrt 27 09:32:21 vm-xoa xo-server[2641104]: Cannot read properties of undefined (reading '0') I hope this helps to understand the problem. Thanks.
  • All XO backup features: full and incremental, replication, mirrors...

    481 Topics
    5k Posts
    JSylvia007J
    @pilow - I know this has gotten a bit off topic, but in the interests of keeping folks informed... I've managed to migrate ALL VDIs over to remote NFS Storage, except this problem VM. To solve that problem, I: Added a second disk on the remote storage, attached it, and booted into clonezilla. Cloned the disk from INSIDE the VM. Detatched and removed the old disk. The local SR is now void of disks. I decided that instead of rebuild the RAID with a new disk, I'm just going to completely pull the disks and replace with shiny new disks. It's just not worth the uncertainty of what MIGHT happen. All the disks in that array are the same age. EDIT: Backup Succeeded on the new disk, so I think you hit the nail on the head @pilow ... Failing SR.
  • Everything related to Xen Orchestra's REST API

    84 Topics
    628 Posts
    olivierlambertO
    Thanks for the quick answer @mathieura
  • Terraform, Packer or any tool to do IaC

    49 Topics
    463 Posts
    dalemD
    Version 1.4.0 is released: https://codeberg.org/NiXOA/system/releases/tag/v1.4.0 It includes significant changes and improvements, including: dedicated getting started section, migration to valkey, only needing to clone system, and helper scripts. the xen-orchestra-ce nixpkg now references the libvhdi nixpkg, and the core flake now references and pulls from the xen-orchestra-ce repo as an overlay. System (the user input flake) now uses the Core repo as an overlay, reducing the need to clone both locally AND allowing system to pull new updates and releases from core. XO, and libvhdi as needed. The next goal is: Make an xsconsole-like TUI Automate package updates for libvhdi and xen-orchestra-ce using CI/CD pipelines Submit libvhdi and xen-orchestra-ce as official nixpkgs
  • Restoring a downed host ISNT easy

    5
    8 Votes
    5 Posts
    5k Views
    ForzaF
    @xcprocks said in Restoring a downed host ISNT easy: So, we had a host go down (OS drive failure). No big deal right? According to instructions, just reinstall XCP on a new drive, jump over into XOA and do a metadata restore. Well, not quite. First during installation, you really really must not select any of the disks to create an SR as you could potentially wipe out an SR. Second, you have to do the sr-probe and sr-introduce and pbd-create and pbd-plug to get the SRs back. Third, you then have to use XOA to restore the metadata which according to the directions is pretty simple looking. According to: https://xen-orchestra.com/docs/metadata_backup.html#performing-a-restore "To restore one, simply click the blue restore arrow, choose a backup date to restore, and click OK:" But this isn't quite true. When we did it, the restore threw an error: "message": "no such object d7b6f090-cd68-9dec-2e00-803fc90c3593", "name": "XoError", Panic mode sets in... It can't find the metadata? We try an earlier backup. Same error. We check the backup NFS share--no its there alright. After a couple of hours scouring the internet and not finding anything, it dawns on us... The object XOA is looking for is the OLD server not a backup directory. It is looking for the server that died and no longer exists. The problem is, when you install the new server, it gets a new ID. But the restore program is looking for the ID of the dead server. But how do you tell XOA, to copy the metadata over to the new server? It assumes that you want to restore it over an existing server. It does not provide a drop down list to pick where to deploy it. In an act of desperation, we copied the backup directory to a new location and named it with the ID number of the newly recreated server. Now XOA could restore the metadata and we were able to recover the VMs in the SRs without issue. This long story is really just a way to highlight the need for better host backup in three ways: A) The first idea would be to create better instructions. It ain't nowhere as easy as the documentation says it is and it's easy to mess up the first step so bad that you can wipe out the contents of an SR. The documentation should spell this out. B) The second idea is to add to the metadata backup something that reads the states of SR to PBD mappings and provides/saves a script to restore them. This would ease a lot of the difficulty in the actual restoring of a failed OS after a new OS can be installed. C) The third idea is provide a dropdown during the restoration of the metadata that allows the user to target a particular machine for the restore operation instead of blindly assuming you want to restore it over a machine that is dead and gone. I hope this helps out the next person trying to bring a host back from the dead, and I hope it also helps make XOA a better product. Thanks for a good description of the restore process. I was wary of the metadata-backup option. It sounds simple and good to have, but as you said it is in no way a comprehensive restore of a pool. I'd like to add my own oppinion here. A full pool restore, including network, re-attaching SRs and everything else that is needed to quickly get back up and running. Also a restore pool backup should be available on the boot media. It could look for a NFS/CIFS mount or a USB disk with the backup files on. This would avoid things like issues with bonded networks not working.
  • Xen Orchestra Backups

    Solved
    5
    0 Votes
    5 Posts
    806 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
    5k 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
    11k 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
    2k 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
    693 Views
    mauzillaM
    @olivierlambert thank you Olivier!
  • Netdata collectors from XCP repo

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

    community
    5
    0 Votes
    5 Posts
    4k 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
    2k 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
    1k 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
    1k 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
    3k 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
    341 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
    3k 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
    3k 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
    2k 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
    2k 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.