I have updated to last master branch bda87
issue remains
Error: invalid HTTP header in response body
Type: full
I have updated to last master branch bda87
issue remains
Error: invalid HTTP header in response body
Type: full
un 12 07:16:23 xenorchestra xo-server[1679463]: 2025-06-12T05:16:23.729Z xo:xapi:vdi WARN invalid HTTP header in response body {
Jun 12 07:16:23 xenorchestra xo-server[1679463]: body: 'HTTP/1.1 500 Internal Error\r\n' +
Jun 12 07:16:23 xenorchestra xo-server[1679463]: 'content-length: 266\r\n' +
Jun 12 07:16:23 xenorchestra xo-server[1679463]: 'content-type:text/html\r\n' +
Jun 12 07:16:23 xenorchestra xo-server[1679463]: 'connection:close\r\n' +
Jun 12 07:16:23 xenorchestra xo-server[1679463]: 'cache-control:no-cache, no-store\r\n' +
Jun 12 07:16:23 xenorchestra xo-server[1679463]: '\r\n' +
Jun 12 07:16:23 xenorchestra xo-server[1679463]: '<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a whi>Jun 12 07:16:23 xenorchestra xo-server[1679463]: }
Jun 12 07:16:28 xenorchestra xo-server[1679463]: 2025-06-12T05:16:28.522Z xo:backups:MixinBackupWriter WARN cleanVm: incorrect backup size in metadata {
Jun 12 07:16:28 xenorchestra xo-server[1679463]: path: '/xo-vm-backups/04d4ce05-81fd-e2b6-ef0d-4e9b91f3ffb1/20250610T051506Z.json',
Jun 12 07:16:28 xenorchestra xo-server[1679463]: actual: 1116023296,
Jun 12 07:16:28 xenorchestra xo-server[1679463]: expected: 1116023808
Jun 12 07:16:28 xenorchestra xo-server[1679463]: }
Jun 12 07:16:29 xenorchestra xo-server[1675344]: 2025-06-12T05:16:29.954Z xo:backups:mergeWorker INFO merge in progress {
Jun 12 07:16:29 xenorchestra xo-server[1675344]: done: 59198,
Jun 12 07:16:29 xenorchestra xo-server[1675344]: parent: '/xo-vm-backups/eda7fcd9-484f-7f19-b5ae-0cfd94ca2207/vdis/89511625-67f3-46be-98fe-8d7a7584386>Jun 12 07:16:29 xenorchestra xo-server[1675344]: progress: 83,
Jun 12 07:16:29 xenorchestra xo-server[1675344]: total: 71442
Jun 12 07:16:29 xenorchestra xo-server[1675344]: }
Jun 12 07:16:39 xenorchestra xo-server[1675344]: 2025-06-12T05:16:39.954Z xo:backups:mergeWorker INFO merge in progress {
Jun 12 07:16:39 xenorchestra xo-server[1675344]: done: 59467,
Jun 12 07:16:39 xenorchestra xo-server[1675344]: parent: '/xo-vm-backups/eda7fcd9-484f-7f19-b5ae-0cfd94ca2207/vdis/89511625-67f3-46be-98fe-8d7a7584386
un 12 07:16:39 xenorchestra xo-server[1675344]: 2025-06-12T05:16:39.954Z xo:backups:mergeWorker INFO merge in progress {
Jun 12 07:16:39 xenorchestra xo-server[1675344]: done: 59467,
Jun 12 07:16:39 xenorchestra xo-server[1675344]: parent: '/xo-vm-backups/eda7fcd9-484f-7f19-b5ae-0cfd94ca2207/vdis/89511625-67f3-46be-98fe-8d7a7584386>
Jun 12 07:16:39 xenorchestra xo-server[1675344]: progress: 83,
Jun 12 07:16:39 xenorchestra xo-server[1675344]: total: 71442
Jun 12 07:16:39 xenorchestra xo-server[1675344]: }
Jun 12 07:16:46 xenorchestra xo-server[1679463]: 2025-06-12T05:16:46.783Z @xen-orchestra/xapi/disks/Xapi WARN openNbdCBT Error: CBT is disabled
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at XapiVhdCbtSource.init (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/xapi/d>
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async #openNbdCbt (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/xapi/disks>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async XapiDiskSource.init (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/di>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/backups/_incrementalVm.>
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async Promise.all (index 1)
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async cancelableMap (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/backups/>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async exportIncrementalVm (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/ba>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async IncrementalXapiVmBackupRunner._copy (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async IncrementalXapiVmBackupRunner.run (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xe>
Jun 12 07:16:46 xenorchestra xo-server[1679463]: code: 'CBT_DISABLED'
Jun 12 07:16:46 xenorchestra xo-server[1679463]: }
Jun 12 07:16:46 xenorchestra xo-server[1679463]: 2025-06-12T05:16:46.863Z @xen-orchestra/xapi/disks/Xapi WARN openNbdCBT Error: CBT is disabled
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at XapiVhdCbtSource.init (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/xapi/d>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async #openNbdCbt (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/xapi/disks>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async XapiDiskSource.init (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/di>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/backups/_incrementalVm.>
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async Promise.all (index 2)
Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async cancelableMap (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/backups/>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async exportIncrementalVm (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xen-orchestra/ba>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async IncrementalXapiVmBackupRunner._copy (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@>Jun 12 07:16:46 xenorchestra xo-server[1679463]: at async IncrementalXapiVmBackupRunner.run (file:///opt/xo/xo-builds/xen-orchestra-202506050918/@xe>
Jun 12 07:16:46 xenorchestra xo-server[1679463]: code: 'CBT_DISABLED'
Jun 12 07:16:46 xenorchestra xo-server[1679463]: }
today same issue again
Snapshot
Start: 2025-06-12 07:16
End: 2025-06-12 07:16
50G-Backup-Delta
Start: 2025-06-12 07:16
End: 2025-06-12 07:16
Duration: a few seconds
Start: 2025-06-12 07:16
End: 2025-06-12 07:16
Duration: a few seconds
Error: invalid HTTP header in response body
Type: full
vm is a PFSense
with template Other install media
Management agent 6.2.0-76888 detected
Hardware virtualization with paravirtualization drivers enabled (PVHVM)
dear all i am facing the same issue
Error: invalid HTTP header in response body
{
"data": {
"mode": "delta",
"reportWhen": "failure"
},
"id": "1749107336350",
"jobId": "89511625-67f3-46be-98fe-8d7a7584386f",
"jobName": "All-2-50G-Delta",
"message": "backup",
"scheduleId": "405be84c-8b49-408a-871e-b21c211ee326",
"start": 1749107336350,
"status": "failure",
"infos": [
{
"data": {
"vms": [
"20e7d42f-bf69-186d-ec65-82e08230e557"
]
},
"message": "vms"
}
],
"tasks": [
{
"data": {
"type": "VM",
"id": "20e7d42f-bf69-186d-ec65-82e08230e557",
"name_label": "PfSense_Ip_92_61_60_23_EXT_172_16_16_99_INT_2022_03_03_07_24_57"
},
"id": "1749107339106",
"message": "backup VM",
"start": 1749107339106,
"status": "failure",
"tasks": [
{
"id": "1749107339113",
"message": "clean-vm",
"start": 1749107339113,
"status": "success",
"end": 1749107339118,
"result": {
"merge": false
}
},
{
"id": "1749107339665",
"message": "snapshot",
"start": 1749107339665,
"status": "success",
"end": 1749107341927,
"result": "02828209-8cc6-8694-8fdd-af5aa04d5b90"
},
{
"data": {
"id": "455eee8b-49ca-4552-9431-ebb417fbd8f8",
"isFull": true,
"type": "remote"
},
"id": "1749107341927:0",
"message": "export",
"start": 1749107341927,
"status": "success",
"tasks": [
{
"id": "1749107347491",
"message": "clean-vm",
"start": 1749107347491,
"status": "success",
"end": 1749107347494,
"result": {
"merge": false
}
}
],
"end": 1749107347496
}
],
"end": 1749107347496,
"result": {
"message": "invalid HTTP header in response body",
"name": "Error",
"stack": "Error: invalid HTTP header in response body\n at checkVdiExport (file:///opt/xo/xo-builds/xen-orchestra-202503211145/@xen-orchestra/xapi/vdi.mjs:40:19)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async Xapi.exportContent (file:///opt/xo/xo-builds/xen-orchestra-202503211145/@xen-orchestra/xapi/vdi.mjs:326:7)\n at async file:///opt/xo/xo-builds/xen-orchestra-202503211145/@xen-orchestra/backups/_incrementalVm.mjs:56:34\n at async Promise.all (index 1)\n at async cancelableMap (file:///opt/xo/xo-builds/xen-orchestra-202503211145/@xen-orchestra/backups/_cancelableMap.mjs:11:12)\n at async exportIncrementalVm (file:///opt/xo/xo-builds/xen-orchestra-202503211145/@xen-orchestra/backups/_incrementalVm.mjs:25:3)\n at async IncrementalXapiVmBackupRunner._copy (file:///opt/xo/xo-builds/xen-orchestra-202503211145/@xen-orchestra/backups/_runners/_vmRunners/IncrementalXapi.mjs:44:25)\n at async IncrementalXapiVmBackupRunner.run (file:///opt/xo/xo-builds/xen-orchestra-202503211145/@xen-orchestra/backups/_runners/_vmRunners/_AbstractXapi.mjs:396:9)\n at async file:///opt/xo/xo-builds/xen-orchestra-202503211145/@xen-orchestra/backups/_runners/VmsXapi.mjs:166:38"
}
}
],
"end": 1749107347497
}
thanks for info
i used https://github.com/ddelnano/packer-plugin-xenserver
but because of lack of ssh key support i changed the code a bit.
now i can use ssh keys. (not ready for a PR)
my problem is that inside the auto iso i use a shell script doing a reboot within the install.
the reason is that i use this iso also on bare metal installations, some software i cant install without doing a reboot.
i will now focus on the ansible integratian an fire the commands after the reboot using ansible.
this might work.
br
Mark
Hi Oliver,
I’ve been experimenting with Terraform — I can create a VM and boot it using my autoinstall ISO, but unfortunately, most other things aren’t working as expected.
So I gave Packer a try instead.
With Packer, I can successfully create a VM, mount the ISO, and perform the installation.
At the moment, I’m stuck trying to reliably detect when the VM installation is actually finished — I’m currently working on a script to solve that.
Out of curiosity: how do you handle the Xen Orchestra appliance installation?
Here’s what I’m aiming for:
We want to generate a custom VM image for our clients to import into different hypervisors (VMware, Xen, XCP-ng, Hyper-V, VirtualBox).
My current workflow and progress:
Generate autoinstall ISO with custom config — DONE
Create VM, mount ISO, perform install, and detect when installation is complete — NOT WORKING YET
Shut down the VM — DONE
Export VM as an OVA template — DONE
Convert that export to other formats for common hypervisors — DONE
Upload final images to our storage for delivery to clients — DONE
The goal is to fully automate the process — like a CI/CD pipeline for VM images.
Right now, I’m able to do nearly everything except reliably detecting when the VM installation is finished.
br
mark
hi
i am struggling with the api.
can i do the following using api?:
then it should start vm creation and run my iso (its a autoinstall iso)
i was able to make it work using packer but packer plugin is quit old and not really mantained...
br
mark
nice tool will there be an option to disable remote google font integration because of GDRP?
Hi i have done a Release upgrade from 20.04 to 22.04 LTS
one VM doesnt recognice the xentools....
i mounted tools from cd and installed it again ... all was fine but xenorchestra says
Management agent not detected
br
Mark
on my side importing backup config in a new XO installation worked (Using Webinterface). (i build from sources). Only thing wich bugs are backup jobs - i had to open and resubmit every backup job to get them work...
br
Mark
Hi do i need to patch my xenserver using AMD EPYC ? Those patches get offered to my AMD nodes by XO.
On intel Xeon nodes it makes sense to me ....