Posts

• RE: backup tasks (exporting VDI) stopped showing progression, bug introduced on build master 7994f or shortly before

  @manilx
  can you retry with NBD enabled ? I have a hunch that it is related to non NBD backup, and the changes introduced to handle qcow2
  (you'll need to restart xo to stop the task )

  my bet is thaht the breaking commit are these https://github.com/vatesfr/xen-orchestra/commit/cbc07b319fea940cab77bc163dfd4c4d7f886776 and https://github.com/vatesfr/xen-orchestra/commit/bb4e14b6ddfe7d682c4bdea089c8407caebfb9a5

  0 fbeauchamp committed to vatesfr/xen-orchestra

  feat(xapi): support import and export of qcow2 disks (#8506)
  
  This PR implement a limited support of generating and reading qcow2 . The support is limited since it only handles qcow2 with 64KB cluster size, with this structure :
  
      header
      refcount table
      refcount blocks
      L1 table
      L1 tables
      data clusters
  
  generated by https://github.com/qemu/qemu/blob/a9cd5bc6399a80fcf233ed0fffe6067b731227d8/scripts/qcow2-to-stdout.py

  0 fbeauchamp committed to vatesfr/xen-orchestra

  fix(backups): use the right format (qcow2/vhd) (#8750)
  
  introduced by https://github.com/vatesfr/xen-orchestra/commit/cbc07b319fea940cab77bc163dfd4c4d7f886776

  posted in Backup

  F

  florent
  
• RE: XO Community edition backups dont work as of build 6b263

  @marcoi
  is there any error message in XO logs ? (like journalctl )

  posted in Backup

  F

  florent
  
• RE: Cloning Windows 11 with vTPM

  @jkatz hello, thanks for your report. This topic is being studied on our side, we have scheduled a ticket on it in our roadmap.
  We will keep you informed.

  Have a good day!

  posted in Management

  L

  lsouai-vates
  
• RE: Is there a way to assign OIDC user to local XOA group (which will have target permissions applied)?

  as far as I know, there is no support to extract a group from the oidc plugin

  posted in Management

  F

  florent
  
• RE: Error: invalid HTTP header in response body

  @peo said in Error: invalid HTTP header in response body:

  can't connect through NBD, fallback to stream export

  "maybe it's the can't connect through NBD"

  do you have VM with a lot of disks ? if yes, can you reduce the concurrency , or the number of nbd connection ?

  posted in Backup

  F

  florent
  
• RE: gui issue in latest builds in backup setting

  @manilx

  the PR is here : https://github.com/vatesfr/xen-orchestra/pull/8754

  fbeauchamp opened this pull request in vatesfr/xen-orchestra

  closed fix(xo-web): clarify when CBT is enabled automatically #8754

  posted in Backup

  F

  florent
  
• RE: gui issue in latest builds in backup setting

  @olivierlambert Nice catch
  CBT will only be enabled when using purge data , I will fix the first one

  (this is because CBT does not improve things without purge snaphot data , but has some edge case , so at least we won't enable it for nothing )

  posted in Backup

  F

  florent
  
• RE: mirror backup to S3

  @robyt said in mirror backup to S3:

  1 backup job with two disables schedules, one full and one delta, to a nas

  Hi robyt

  i the mirror settings : full mirror if when mirroring full backup ( called backup ) , as one file per VM
  The incremental mirror will take care on all the files created by a delta backup

  Can you show me what retention you have on both side ? you have more explanation on the syncrohnization algorithm here https://docs.xen-orchestra.com/mirror_backup , to be short a delta mirror can only be done if part of the disks chains are common to both remotes

  posted in Backup

  F

  florent
  
• RE: Error: invalid HTTP header in response body

  @peo said in Error: invalid HTTP header in response body:

  @olivierlambert Also the same in XOA, switched "latest" in the "release channel" before updating:

  this is probably a CBT issue
  you will have more infomation in the log ( journalctl as root )
  can you try running the backup without NBD/CBT enabled ?

  posted in Backup

  F

  florent