Thank you for this constructive argument

Have a nice day.

Thank you all, this is now fixed.

https://github.com/vatesfr/xen-orchestra/commit/07bd9cadd4732554c57e441cd9d860b63f73fe02

0 julien-f committed to vatesfr/xen-orchestra

fix(xo-server/vm.create): typo during VIF creation

Introduced by ecae554a7

Fixes https://xcp-ng.org/forum/post/49143

@markhewitt1978 Hi, thank you for your feedbacks!

We are aware that this limitation bothers a lot of users and we have plan to address that in the next major version of XO.

XO 5 was already a major improvement over its predecessor because it allows viewing and handling a much bigger infra.

XO 6 will go further in this direction by introducing a tree view and the possibility to edit and handle many objects at the same time.

@Danp That may not be directly to script but to the external environment: SMB works much better if cifs-utils is installed on the system, something that is present on our doc but might be missing in some install scripts.

We have no animosity whatsoever regarding these scripts but we prefer our appliances (or even manual installs from our documentation) because we understand much better what's going on and it's easier to replicate and fix the issues

Regarding your idea of including the commit identifier for the source version, that's not a bad idea, a (as simple as possible) implementation in a PR would be welcome

@olivierlambert Done: https://github.com/vatesfr/xen-orchestra/commit/33b45d2eda2ce6d8071541da246bdcfd06b133b8

It's not perfect but that should help

Example:

vm.start
{
  "id": "123e4f2b-498e-d0af-15ae-f835a1e9f59f",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "errors": [
    "R620-L3: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)",
    "R620-L1: HOST_NOT_ENOUGH_FREE_MEMORY(216430280704, 18778341376)",
    "R620-L2: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)"
  ],
  "message": "",
  "name": "Error",
  "stack": "Error: 
    at Xapi._startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1358:15)
    at Xapi.startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1393:7)
    at Api.callApiMethod (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:307:20)"
}

2 julien-f committed to vatesfr/xen-orchestra

feat(xo-server): better info when failing to start a VM

Fixes https://xcp-ng.org/forum/post/47329

The DNS cache has been merged, keep us posted if you have any issues.

Fixed, thanks for the report

https://github.com/vatesfr/xen-orchestra/commit/7830c89e66e178921695aa5e17670717703ef290

0 julien-f committed to vatesfr/xen-orchestra

fix(xo-server/Xapi#exportVm): correctly use getRecord

Introduced by 6aa5ec6eb

@olivierlambert Indeed, expect a patch release of this package very soon

Done.

I've added the support of advanced filtering in the API, it does no have first class support in xo-cli yet but it's usable anyway:

xo-cli xo.getAllObjects limit=json:10 filter='type:/^VM$/ snapshots:length:>2'

Should be fixed, sorry for this

Thanks all for your feedback!

@Spunky_Surveyor XO detected an XVA file in this VM backup dir, it appears to be invalid.

As our heuristic is not perfect, XO does not delete it automatically but simply reports it.

If you have a subscription and an official XO VM Appliance, you can open a support tunnel and we'll see if it's indeed broken or if we can improve our heuristic.

Otherwise, you can try to manually import it.

Ping @rajaa-b

@krakers This is unrelated to the current thread and very likely not an XO problem. Please open a separate thread, maybe the community will be able to help.

@Andrew @krakers Unfortunately now, it's an unrelated issue, which usually indicates that the VHD that was just downloaded from the host is incomplete. Deleting the snapshots related to this backup job on the source VM will trigger a full export, which might help.

@Andrew Interesting

@Andrew Could show us the info of the problematic VHD files?

> cd xo-vm-backups/<VM UUID>/vdis/<job UUID>/<VDI UUID>/
> npx vhd-cli info *.vhd

@Andrew Thank you, I'm investigating

@someone2b Just install this work-around xenstore-read with the following commands and hopefully it will work.

sudo -s
cd /usr/local/bin
curl -O https://gist.githubusercontent.com/julien-f/a6f98de3bd5a775f3f04b2fa14a9a102/raw/xenstore-read
chmod +x xenstore-read

@sbz71 The stable channel should not have the issue, not sure when we'll release a fix for latest.

If you have an XO subscription, you can open a support ticket and a support tunnel and we'll be able to patch your install

My bad, I misunderstood the question

@sbz71 Please make sure you are on master: https://github.com/vatesfr/xen-orchestra/commit/7387ac2411bcdb9880d85fe25760bb67a545340d

0 julien-f committed to vatesfr/xen-orchestra

fix(xo-server/disk.import): fix `xapi._getOrWaitObject` call

Maybe related to #6282

Introduced by 5063a6982