Still running. Must have been the change I did in the BIOS.

Went into BIOS today and found some settings on maximum cpu. I set it to maximum efficiency. I read somewhere that some cpu throttling functions in bios could cause issues.

So far so good, recent days it crashed in the evening every day, and now it is soon midnight so fingers crossed.

@olivierlambert Yes this is really great. I have a windows box where I experiment with bluetooth a bit and having backup on this machine at least once a week or so feels very good I think
I think it also makes sense that a machine that needs to be taken down in order to make backup also probably will need another backup schedule.

@olivierlambert Thanks @olivierlambert it did indeed work well!
I did not know I had to create a separate backup job, thought I could set it on one VM in the existing backup job, but I now understand the setup

@olivierlambert @marcungeschikts I saw in the recent release notes that it should be possible but that it will shut down and start the vm again? Did I dream this or did I understand it right?
My VM with USB is still not backing up, maybe there is a setting somewhere I need to enable?

Kind regards
Jens

Hi

I have a development machine on xcp-ng, and I had to use Bluetooth for a project so I enabled USB passthru in order to access the Bluetooth device on the machine.

I also in another project have a couple of modems connected to a VM on VMWare ESXi.

None of these would require constant access to the hardware. It would be perfectly OK to disable USB passthru while doing backups and I am sure there are other users who have a similar need.

Would it be possible to add a setting in Backup. "Disable USB passthru if required" I am thinkink then that USB passthru could be disabled during backup and then enabled again.

Kind regards
Jens

@stormi Thanks, it was easily solved and now there is no extra step in XCP-ng center

[16:57 xcp-ng-btdjnqqd ~]# xe pool-list
uuid ( RO)                : 1f12bb2e-3138-36fd-bfc7-a572186271cf
          name-label ( RW): xcp-ng-3
    name-description ( RW): 
              master ( RO): 08a4a440-3c00-4d5e-af8c-46dd412a32cc
          default-SR ( RW): e5b243b2-28ba-31e8-6c8c-c0ab5e9d1c23


[16:57 xcp-ng-btdjnqqd ~]# xe pool-param-set
Required parameter not found: uuid
For usage run: 'xe help'
[16:58 xcp-ng-btdjnqqd ~]# xe pool-param-set uuid=1f12bb2e-3138-36fd-bfc7-a572186271cf name-label=
[16:58 xcp-ng-btdjnqqd ~]# xe pool-list
uuid ( RO)                : 1f12bb2e-3138-36fd-bfc7-a572186271cf
          name-label ( RW): 
    name-description ( RW): 
              master ( RO): 08a4a440-3c00-4d5e-af8c-46dd412a32cc
          default-SR ( RW): e5b243b2-28ba-31e8-6c8c-c0ab5e9d1c23


[16:58 xcp-ng-btdjnqqd ~]# 

I wonder why it has named itself xcp-ng-btdjnqqd when I set its name to xcp-ng-3. Everything in XCP-ng center and in XO sais xcp-ng-3 but not in the command prompt.

Still running. Must have been the change I did in the BIOS.

Went into BIOS today and found some settings on maximum cpu. I set it to maximum efficiency. I read somewhere that some cpu throttling functions in bios could cause issues.

So far so good, recent days it crashed in the evening every day, and now it is soon midnight so fingers crossed.

@olivierlambert Interesting is it possible to simply remove the namelabel. I know it does not matter but I think it is nice to do the same on all hosts

@stormi Thanks, I found 2 crashes there, unfortunately these are much older than the latest crashes, so something else must be happening as well.

crash.txt

I had to rename a .tgz to .txt, could not upload otherwise.

Kind regards
Jens

Thanks for clarifying

Jens