@archw hello.

I had the same issue with xoa VM (vates build).
Body timeout error on backups.
I tried another VM XO from sources. Didn't fix the issue and some backups are also failing.
To my understanding is not XO issue.
Also this started when i upgrade the hosts from 8.2 to 8.3, im not sure if this is relevant or not, or is just a coincidence.
Also i have 2 hosts in the same pool. Backups are failing on both hosts.

Any updates from your side?? What is your suggestion on what i should try next?

@DustinB yes, i did that some days ago.

Hello everyone,

do we have any news for the body timeout error on backups ?

I've had this error for the last two months, using XOA and XO from sources.

The master is 2 commits behind. (93a11)
XO is 34c1c

what i can do now for this ?

@olivierlambert Thank you olivier !

So the "Mirror incremental backup" will be enough to replicate the local backup repository to offsite backup repository ??

Great feature !

Hello everyone,

i'm testing the new feature of XOA called VM mirror backup. This is really usefull to have offsite backups to another remote location.

I want to ask if anyone knows what is the difference between the 2 options :
mirror incremental and mirror full. does this taking into consideration the type of backups to copy ?

thanks for any comments.

@olivierlambert said in XCP-ng host not seeing storage after unmount / mount:

xe vm-disk-list uuid=<VM UUID>

Hello Sir, i have SSH on the host and run the command , using the uuid of the VM we are trying to start.

@olivierlambert df -h
looks like it mounts correctly the specific NFS

dmesg nothing special, toolstack restart i did also from Xen Orchestra , i guess is executing the same command.

@Bambos

@olivierlambert no, just 2 vdi. i tried to disable the dvd-drive from boot order without any change.

@olivierlambert this is by mistake, i used to have a host 2 also in the pool that i don't use. now i removed it by the pool.

error log: still same without the line of host 2 missing.

vm.start
{
  "id": "95991d36-a94c-4efe-62e0-3d15b2245bce",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "errors": [
    "Host 1: VM_REQUIRES_SR(OpaqueRef:7371d453-759a-4870-934c-9a1b13fa40a7, OpaqueRef:8a929bf4-9b17-4bce-ab59-e2d5665baa0b)"
  ],
  "message": "",
  "name": "Error",
  "stack": "Error: 
    at Xapi._startVm (file:///opt/xo/xo-builds/xen-orchestra-202205201634/packages/xo-server/src/xapi/index.mjs:990:15)
    at Xapi.startVm (file:///opt/xo/xo-builds/xen-orchestra-202205201634/packages/xo-server/src/xapi/index.mjs:1026:7)
    at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202205201634/packages/xo-server/src/xo-mixins/api.mjs:314:20)"
}

@olivierlambert Hello Olivier,

the error on the red notification is : unknown error from the peer:

and the complete error log:

vm.start
{
  "id": "95991d36-a94c-4efe-62e0-3d15b2245bce",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "errors": [
    "Host 1: VM_REQUIRES_SR(OpaqueRef:7371d453-759a-4870-934c-9a1b13fa40a7, OpaqueRef:8a929bf4-9b17-4bce-ab59-e2d5665baa0b)",
    "Host 2: HOST_NOT_LIVE()"
  ],
  "message": "",
  "name": "Error",
  "stack": "Error: 
    at Xapi._startVm (file:///opt/xo/xo-builds/xen-orchestra-202205201634/packages/xo-server/src/xapi/index.mjs:990:15)
    at Xapi.startVm (file:///opt/xo/xo-builds/xen-orchestra-202205201634/packages/xo-server/src/xapi/index.mjs:1026:7)
    at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202205201634/packages/xo-server/src/xo-mixins/api.mjs:314:20)"
}

the storage is exactly as it was, same name , same type, same paths on NFS.

Hello everyone,

after problem on the NFS storage i was using for VM Space, i had perform unmount / mount after repair the NFS server.
Now the VM's are not starting with error missing storage.
Even if i mount the NFS with same name and same IP, it seems that is not finding the relevant storage of the VM's, it thinks that is other storage.

I'm using XOA from sources as interface (not center)
Any comments ?

@Andrew thank you , it's NFS mount yes.
i perform forget and remount and now is ok, most probably i chose older storage from another host, the menu to select storage for VM showing everything associated with the pool and sometimes this is confusing.

Thanks for your comment.

I got the error:

SR_BACKEND_FAILURE_47(, The SR is not available [opterr=[Errno 116] Stale file handle: '/var/run/sr-mount/5a031a17-96c8-4e11-062b-246035067500'], )

when i'm trying to create a second virtual disk for a VM.
There is no issue with one disk.

@olivierlambert thank you Olivier. Indeed you are right, we need to change also the max vcpu limits in advanced.

Then is booting normally.

@olivierlambert yes, agree with everything ! thank you.

the question is why XOA not taking the new setting for the 2 vCPU's ?

@olivierlambert Dear Sir,

i have notice that vcpus assignment has to be the maximum number of cores available, for example 4 core cpu, we can have VM's with 1-2-3-4 vcores.

When over assign vcores, for example assign 16vcores on 4 core cpu, we have the error :

"errors": [
"localhost: HOST_NOT_ENOUGH_PCPUS(16, 4)"
[no problem on that]

But after going back to edit the settings and put 2vcores,

the machine still not booting and return the same error, (16,4), it seems that is not getting the new setting. Is there any step we can do to update the VM settings?

Site note: creation of a new vm with 4 vcore will boot normally !

Thanks for your great support. any comments or suggestions appreciated.