is there a reverse proxy before the xoa ?

@DevFlint the https://XOA_URL/rest/v0/tasks endpoint exists, but it's not yet documented through swagger

you should be able to add ?sync=true to the url to get the immediate result, but it can fail with a timeout if the creation takes too much time ( for example : migrating a big template )

found it , there was not one, but 2 bugs
albeit small they were putting the xo backup in a incorrect state
the fix is here, and will be merged as soon as possible and then released as a patch for xoa users
https://github.com/vatesfr/xen-orchestra/pull/8780

really thank you everyone for the information

fbeauchamp opened this pull request in vatesfr/xen-orchestra

closed fix(xapi): respect the config file setting for preferNbd #8780

@RobWhalley saved the day
We are still working on it to better understand why it fixes and improve the situation

@frank-s yes please
the more detailed the bug report is, the easier it is to fix

@Gheppy and nothing in the journalctl log ?

you're right, preferNbd default value is not the same on the front and the back, we'll fix it

Most of the backup issue are solved by either removing the snapshot, or having it fa enough so thaht the next backup will be a base one, with all the data

I am still not reproducing the nackup stuck issue after this commit https://github.com/vatesfr/xen-orchestra/commit/3c8efb4dc3e1cb3955521063047227849cfb6ed3

0 fbeauchamp committed to vatesfr/xen-orchestra

fix(backups): non NBD backups stalls (#8766)

@Gheppy if this is what I think it should have been fixed by https://github.com/vatesfr/xen-orchestra/commit/3c8efb4dc3e1cb3955521063047227849cfb6ed3

0 fbeauchamp committed to vatesfr/xen-orchestra

fix(backups): non NBD backups stalls (#8766)

@frank-s it looks like you need to select a base SR , even if you choose to assign different SR for each vdi ( or do not restore some vdi)

this looks like a UI bug

@robyt 2 is generally a sweet spot

@Gheppy is there anything in the xo ? like an error on "readblock" ?

@RobWhalley nice work, I am testing it right now

@OhSoNoob @manoli
do you have anything in the Xo logs ?

@bogikornel this look like the most recent backup job did not use CBT , but the previous was using it
is it intendend ?

@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

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

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

@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 ?

@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

@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 )