Xen Orchestra

• A

  Backup-NG Error "invalid header checksum" after VM-Disk-Resize and reaching retention Limit.
  • AlexD2006  

  1
  0
  Votes
  1
  Posts
  38
  Views

  No one has replied

• 

  This topic is deleted!
  • Soarin  

  1
  0
  Votes
  1
  Posts
  4
  Views

  No one has replied

• P

  "Cannot GET /" Error after update
  • Pechkin000  

  11
  0
  Votes
  11
  Posts
  137
  Views

  P

  In case someone ran into the same problem here is how I solved it. I had a feeling this was http mounts issue. I checked and looks like during update process the .xo-server.toml got deleted. I copied the sample one from the /opt/xen-orchestra/packages/xo-server/sample.config.toml , edited the http.mount and bob's your uncle. I have a feeling this has something to do with the format of that file change. When I originally built from source the file has a slightly different syntax and it was called .xo-server.yaml. At least according tot he directions I used to build. In any case its all back to normal now. Thanks you everyone for your help.
• F

  Try to import .ova
  • fraggan  

  26
  0
  Votes
  26
  Posts
  271
  Views

  

  Thanks, this way we'll have a way to understand what's wrong with this OVA, if it's something really specific or a VMWare way to make something we didn't expected
• H

  Self-Service not showing assigned IP pool
  • hitechhillbilly  

  1
  0
  Votes
  1
  Posts
  23
  Views

  No one has replied

• P

  Feature suggestion: attach an existing SR in XO
  • peder  

  4
  0
  Votes
  4
  Posts
  64
  Views

  

  Thanks for your feedback, please open an issue here to describe that so XO devs will improve it: http://github.com/vatesfr/xen-orchestra/issues/new Thanks!
• 

  xoa, xoa-updater ignore LC variables
  xoa xoa-updater utf8 • • MajorTom  

  9
  0
  Votes
  9
  Posts
  132
  Views

  

  Yes, I know this is not exclusive to C, but there are some facilities to handle this, that are, as far as I know, not available in Node.
• 

  xo-server: Warning: connect.session() MemoryStore is not designed for a production environment, as it will leak memory, and will not scale past a single process.
  xoa memory leak • • MajorTom  

  2
  0
  Votes
  2
  Posts
  71
  Views

  

  @MajorTom I saw it on my XenOrchestra's and wondered also
• H

  Self-Service moving VMs from one to the other
  • hitechhillbilly  

  2
  0
  Votes
  2
  Posts
  59
  Views

  

  @hitechhillbilly yes it does you can do it live or with a shutdown VM
• P

  free space of backup drive reported incorrect
  • payback007  

  5
  0
  Votes
  5
  Posts
  115
  Views

  P

  that's relatively easy to explain, only the naming is doubled: the backup-hdd are local disks raid1 in xcp-ng and there brought to xcp-ng as a local "vmbackup" volume, called vmbackup on xcp-ng-volume a disk is created with the name "backup_raid1_1tb" and connected as 2nd disk (xvdb) to XO to make the disk available for backup-usage the disk xvdb is mounted via "remote" as a local now usage for backup-ng is possible, but the usage is not xo_disks
• D

  Deleting old delta backups.
  • dawid-xcpng  

  2
  0
  Votes
  2
  Posts
  88
  Views

  

  Yes, you can safely remove them.
• 

  xoa - host restart, random DR vms are UP!
  • akurzawa  

  7
  0
  Votes
  7
  Posts
  90
  Views

  

  I've replied on github. For sure the VMs should not boot. Of course the source vm has autopower on parameter becouse it's needed. The problem is big: DR copy of Second Active Directory server is up.... for sure I can expect AD problems in a while... Autopower on is set up:
• A

  USB Hard drives for VM exports
  • axel  

  10
  0
  Votes
  10
  Posts
  123
  Views

  

  @axel said in USB Hard drives for VM exports: thx i will try it soon expect very. slow. data. transfer
• B

  SOLVED XOA Update patches fails
  • bazzacad  

  9
  0
  Votes
  9
  Posts
  126
  Views

  

  That's why I thought. NEVER enable base repo. If you want a package from their, just enable it during the yum install command line.
• B

  SOLVED Stuck on Importing XOA VM....
  • bazzacad  

  4
  0
  Votes
  4
  Posts
  120
  Views

  

  Okay thanks. Note that with XCP-ng 8.0, it will be even easier to deploy XOA, directly from the host HTTP URL "mini website".
• D

  XO from the sources - Something in the pages is missing
  • dcstancu  

  19
  0
  Votes
  19
  Posts
  178
  Views

  

  @pdonias Thanks for confirming that this issue wasn't caused by the use of a 3rd party script.
• N

  How to delete unmanaged disks in local storage
  • nodesocket  

  2
  0
  Votes
  2
  Posts
  73
  Views

  

  Those are likely "base copy". If it's the case, it's normal because they are "parents" of a VDI chain (snapshot, active disks etc.) What you can probably safely remove are orphaned disks.
• 

  vm start delay - does it work yet?
  • akurzawa  

  5
  0
  Votes
  5
  Posts
  181
  Views

  P

  unfortunately "start delay" is not working as expected. The function what you marked above is to change the start delay of an existing "vApp". Here is an example of my setup: The value whould change the "Delay interval" later by XOA, nothing else. Otherwise is vApp feature also not working on my XCP-ng installation, I think it was never really tested. If you want to implement start delays to your VM's you can follow this guide: define vApp for autostart in xcp-ng center including start order find out the uuid of the vApp: xe appliance-list write autostart script containing #!/bin/sh xe appliance-start uuid=uuid-autostart-vApp implement new systemd.service in /etc/systemd/system/autostart.service [Unit] Description=autostart script for boot VM After=graphical.target [Service] Type=simple ExecStart=/path/to/your/autostart-script.sh TimeoutStartSec=0 [Install] WantedBy=default.target enable the service systemctl enable autostart.service Editing of boot delay time is then possible via XOA which is already a nice feature at all for "fine tuning" or adapt if new VMs are added to the autostart vApp. @olivierlambert whould it make sense to open an additional feature request? vApp-implementation was several times discussed with no "final statement" I think.
• J

  Backup-NG daily delta issue: footer1 !== footer2
  • jcdick1  

  2
  0
  Votes
  2
  Posts
  30
  Views

  

  Hi, Before reporting on issues when you use XO from the sources, you must always fetch the latest code available on GitHub. Because it's likely some issues are fixed since then. Please upgrade, and come back if the problem persists
• 

  No manifest found for stable channel.
  • akurzawa  

  4
  0
  Votes
  4
  Posts
  42
  Views

  

  We're deploying support for the incoming release channels and there was an issue with that.