@nullpunktnull XO is trying to prevent bruteforce and at the same time avoid annoying users by blocking valid authentication attempts.

The current policy is to require a delay of at least 2 seconds between every tries for a given user.

It's very basic but more than enough to protect accounts with reasonable passwords

You have weird keys also. Please be sure to remove the key entirely.

@danp i couldnt get the log from command line, sorry

But i was able to complete the backup to another remote, so i think the main problem is the remote im using

After installing the drivers I do see the device in the OS! Unfortunately, I do not believe using an Nvidia GPU like the Quadro P400 is possible with standard Nvidia drivers. I am getting error code 43 as I now read so many others are...

I removed my pci device from the vm using the following command:

xe vm-param-remove param-name=other-config uuid=6ffb8f66-297e-98ef-f7c9-2c930c5e4ce2 param-key=pci 0/0000:01:00.0,1/0000:01:00.1

To see parameters of the vm in general I used:

xe vm-param-list uuid=6ffb8f66-297e-98ef-f7c9-2c930c5e4ce2

I tested in Debian 10 and have similar problems when trying to use the card. The card is visible but will not run.

root@debian:/home/user# nvidia-detect Detected NVIDIA GPUs: 00:05.0 VGA compatible controller [0300]: NVIDIA Corporation GP107GL [Quadro P400][10de:1cb3] (rev a1) Checking card: NVIDIA Corporation GP107GL [Quadro P400] (rev a1) Your card is supported by the default drivers and legacy driver series 390. It is recommended to install the nvidia-driver root@debian:/home/user# apt install nvidia-driver root@debian:/home/user# apt install nvidia-smi root@debian:/home/user# nvidia-smi Unable to determine the device handle for GPU 0000:00:05.0: Unknown Error

Max vCPU means the number max of vCPU the VM can have when it runs. So it means you can change that number in live between 1 and max vCPUs.

@harajukakei I dont use it but it does work for me (XO build from Source), although not from my android phone (the hosts don't move across to the Available list), so could it be browser related?

@julien-f no it didn't

@andy you're welcome!

@julien-f

Thank you for explaining your plans. I am very eager to see the new XO 6! Perhaps a Christmas present for all of us?

I just realised I have one more "peeve" with XOA. That is the console view which does not work well with Swedish keyboard layout. For example pressing Alt-Gr+2 to get at-sign '@' doesn't work. It also crashes the keyboard input so it doesn't release the alt-key. This always works correctly in XCP-ng center. The problem is in both Linux and Windows guests.

Have you checked our guide to install Windows drivers? Check https://xcp-ng.org/docs/guests.html#windows

If you still have issues, with your current XOA account in trial, you can open support tickets already so we can take a look remotely (https://support.vates.fr)

Feature request oped

https://github.com/vatesfr/xen-orchestra/issues/5391

brezlord created this issue in vatesfr/xen-orchestra open Set pool wide Xen Motion Network #5391

@danp said in XO created snapshots are too visible:

I seem to recall this issue coming up previously. I think non-XO snapshots are flagged as templates to that they aren't included in the VM list.

Yes, I just found it here, https://xcp-ng.org/forum/topic/2718/xcp-ng-center-20-03-00-released/ , in the discussion between you, @hvilches , and @olivierlambert

It looks like it's not just XCP-ng Center / XenCenter that create snapshots with the is-a-template parameter set true. The xe CLI does as well when creating a snapshot with the xe vm-snapshot command and some xe commands like xe vm-list show the snapshots with is-a-template set false but not the ones with is-a-template set true. xe snapshot-list shows both types but allows you to select just one or the other with is-a-template=true (or false). xe template-list doesn't seem to allow showing the snapshots by trying to select using is-a-snapshot=true though the parameter is accepted and not flagged as an error.

Odd behavior all around. I only noticed it because I have scripts that parse through the vm-list output and end up catching XO snapshots but not others in the process.

I was originally thinking this might be a bug in XO but maybe it's actually a problem in the xe vm-list command or XAPI in general, i.e. a list of VMs shouldn't list snapshots the way it already doesn't list templates.

@akurzawa s3 backups/delta backups are not working great for big vms
but I never had this problem! check the bucket and directory

@moradin
Hello I also have this issue. Image 1 shows you the VM I want to migrate from server 1.
Image 2 shows you a VM on server 2 were I want to migrate to.

They have the same setting but it doesn't work.

I'm getting this errors on big vms:

{ "data": { "mode": "full", "reportWhen": "failure" }, "id": "1605563266089", "jobId": "abfed8aa-b445-4c94-be5c-b6ed723792b8", "jobName": "amazonteste", "message": "backup", "scheduleId": "44840d13-2302-45ae-9460-53ed451183ed", "start": 1605563266089, "status": "failure", "infos": [ { "data": { "vms": [ "68b2bf30-8693-8419-20ab-18162d4042aa", "fbea839a-72ac-ca3d-51e5-d4248e363d72", "b24d8810-b7f5-5576-af97-6a6d5f9a8730" ] }, "message": "vms" } ], "tasks": [ { "data": { "type": "VM", "id": "68b2bf30-8693-8419-20ab-18162d4042aa" }, "id": "1605563266118:0", "message": "Starting backup of TEST. (abfed8aa-b445-4c94-be5c-b6ed723792b8)", "start": 1605563266118, "status": "failure", "tasks": [ { "id": "1605563266136", "message": "snapshot", "start": 1605563266136, "status": "success", "end": 1605563271882, "result": "a700da10-a281-a124-8283-970aa7675d39" }, { "id": "1605563271885", "message": "add metadata to snapshot", "start": 1605563271885, "status": "success", "end": 1605563271899 }, { "id": "1605563272085", "message": "waiting for uptodate snapshot record", "start": 1605563272085, "status": "success", "end": 1605563272287 }, { "id": "1605563272340", "message": "start VM export", "start": 1605563272340, "status": "success", "end": 1605563272362 }, { "data": { "id": "7847ac06-d46f-476a-84c1-608f9302cb67", "type": "remote" }, "id": "1605563272372", "message": "export", "start": 1605563272372, "status": "failure", "tasks": [ { "id": "1605563273029", "message": "transfer", "start": 1605563273029, "status": "failure", "end": 1605563715136, "result": { "message": "write EPIPE", "errno": "EPIPE", "code": "NetworkingError", "syscall": "write", "region": "eu-central-1", "hostname": "s3.eu-central-1.amazonaws.com", "retryable": true, "time": "2020-11-16T21:55:08.319Z", "name": "NetworkingError", "stack": "Error: write EPIPE\n at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)" } } ], "end": 1605563715348, "result": { "message": "write EPIPE", "errno": "EPIPE", "code": "NetworkingError", "syscall": "write", "region": "eu-central-1", "hostname": "s3.eu-central-1.amazonaws.com", "retryable": true, "time": "2020-11-16T21:55:08.319Z", "name": "NetworkingError", "stack": "Error: write EPIPE\n at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)" } }, { "id": "1605563717917", "message": "set snapshot.other_config[xo:backup:exported]", "start": 1605563717917, "status": "success", "end": 1605563721061 } ], "end": 1605564045507 }, { "data": { "type": "VM", "id": "fbea839a-72ac-ca3d-51e5-d4248e363d72" }, "id": "1605564045510", "message": "Starting backup of DESKTOPGREEN. (abfed8aa-b445-4c94-be5c-b6ed723792b8)", "start": 1605564045510, "status": "failure", "tasks": [ { "id": "1605564045533", "message": "snapshot", "start": 1605564045533, "status": "success", "end": 1605564047224, "result": "3e5fb1b5-c93e-f242-95a2-90757b38f727" }, { "id": "1605564047229", "message": "add metadata to snapshot", "start": 1605564047229, "status": "success", "end": 1605564047240 }, { "id": "1605564047429", "message": "waiting for uptodate snapshot record", "start": 1605564047429, "status": "success", "end": 1605564047631 }, { "id": "1605564047634", "message": "start VM export", "start": 1605564047634, "status": "success", "end": 1605564047652 }, { "data": { "id": "7847ac06-d46f-476a-84c1-608f9302cb67", "type": "remote" }, "id": "1605564047657", "message": "export", "start": 1605564047657, "status": "failure", "tasks": [ { "id": "1605564048778", "message": "transfer", "start": 1605564048778, "status": "failure", "end": 1605564534530, "result": { "message": "write EPIPE", "errno": "EPIPE", "code": "NetworkingError", "syscall": "write", "region": "eu-central-1", "hostname": "s3.eu-central-1.amazonaws.com", "retryable": true, "time": "2020-11-16T22:08:35.991Z", "name": "NetworkingError", "stack": "Error: write EPIPE\n at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)" } } ], "end": 1605564534693, "result": { "message": "write EPIPE", "errno": "EPIPE", "code": "NetworkingError", "syscall": "write", "region": "eu-central-1", "hostname": "s3.eu-central-1.amazonaws.com", "retryable": true, "time": "2020-11-16T22:08:35.991Z", "name": "NetworkingError", "stack": "Error: write EPIPE\n at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)" } }, { "id": "1605564535540", "message": "set snapshot.other_config[xo:backup:exported]", "start": 1605564535540, "status": "success", "end": 1605564538346 } ], "end": 1605571759789 }, { "data": { "type": "VM", "id": "b24d8810-b7f5-5576-af97-6a6d5f9a8730" }, "id": "1605571759883", "message": "Starting backup of grayLog. (abfed8aa-b445-4c94-be5c-b6ed723792b8)", "start": 1605571759883, "status": "failure", "tasks": [ { "id": "1605571759912", "message": "snapshot", "start": 1605571759912, "status": "success", "end": 1605571773047, "result": "600bf528-8c1d-5035-1876-615e1dd89fea" }, { "id": "1605571773051", "message": "add metadata to snapshot", "start": 1605571773051, "status": "success", "end": 1605571773081 }, { "id": "1605571773391", "message": "waiting for uptodate snapshot record", "start": 1605571773391, "status": "success", "end": 1605571773601 }, { "id": "1605571773603", "message": "start VM export", "start": 1605571773603, "status": "success", "end": 1605571773687 }, { "data": { "id": "7847ac06-d46f-476a-84c1-608f9302cb67", "type": "remote" }, "id": "1605571773719", "message": "export", "start": 1605571773719, "status": "failure", "tasks": [ { "id": "1605571774218", "message": "transfer", "start": 1605571774218, "status": "failure", "end": 1605572239807, "result": { "message": "write EPIPE", "errno": "EPIPE", "code": "NetworkingError", "syscall": "write", "region": "eu-central-1", "hostname": "s3.eu-central-1.amazonaws.com", "retryable": true, "time": "2020-11-17T00:17:01.143Z", "name": "NetworkingError", "stack": "Error: write EPIPE\n at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)" } } ], "end": 1605572239942, "result": { "message": "write EPIPE", "errno": "EPIPE", "code": "NetworkingError", "syscall": "write", "region": "eu-central-1", "hostname": "s3.eu-central-1.amazonaws.com", "retryable": true, "time": "2020-11-17T00:17:01.143Z", "name": "NetworkingError", "stack": "Error: write EPIPE\n at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)" } }, { "id": "1605572242195", "message": "set snapshot.other_config[xo:backup:exported]", "start": 1605572242195, "status": "success", "end": 1605572246834 } ], "end": 1605572705448 } ], "end": 1605572705499 }

also delta backup have the same problem

@naeemarsalan Good catch, It will be added to the cloudinit script creating the master and the nodes.

This will save one reboot to everyone.

It's a little different, but if in Xen Orchestra you go:
Home => Hosts => <host> => Network
there I can see my storage IP addresses comparable to that "IP Address Configuration" part.

Except that here, all the networks are listed in the same list.
Can you see if that's what you are looking for?

Is there a way to access your OVA so we can try to reproduce?

Existing HA level is at VM level. It means, if the VM is down (or the host on the VM is running is down), it will be booted on a working host in that pool.

For hyperconvergence, it's far from being a miracle solution. It costs a lot of thinking, planning and maintenance (and careful usage of it).

Like HA in the end.

So before asking for advanced features, it's good to think about what you really need.