Ok so i created a symlink from @aws-sdk to was-sdk and now it works.
as the error was looking for node_modules/aws-sdk and not node_modules/@aws-sdk

@Aimdev eh man people use a lot of different browsers and don't always remember all the options, the dev's here are top 5 star really.

I did it because I do use Safari and simply replicated the steps and noticed the pop-up warning (I never allow pop-ups by default) so I figured that could be the issue.

Have a great weekend you too and you're welcome!

@olivierlambert Thank you

@ITJamie Alma Linux 8.5 template is finished and should be added to the hub in the next day or two. I should have Rocky Linux done shortly after that. Note that in CentOS/RHEL related distros, the hostname: {name}% parameter that's filled in under the cloud-init config is not enough to change the hostname for the machine, CentOS (and related) expects a fully qualified domain name. To get the newly spawned VM have the hostname you'd like, supply fqdn parameter as well:

use VM name as hostname:

#cloud-config hostname: {name}% fqdn: {name}%.localdomain.local

use custom hostname:

#cloud-config hostname: testvm fqdn: testvm.localdomain.local

It's just a warning 🙂 It just means you are running XO on a non-Xen VM, but it shouldn't be a problem to run it.

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

@stormi yes, that we be helpful indeed so we can stick to a build version at least for a while.

I updated the doc accordingly: https://xen-orchestra.com/docs/community.html

@mauzilla To boot an ISO in a VM, you need to select "DVD" in the boot order, put it first, and hit "Save". Then boot the VM.

For ANY system (real or VM), you need boot it with the same type of bootstrap as it was installed to use. BIOS or UEFI. If you change the boot type then you have to make the OS ready to use the new/different settings (not just a VM problem).

If you created a Windows image from a working system that booted with UEFI then you have to copy ALL partitions (the whole disk), not just the C windows drive.

@stormi

Thanks for the big help that fixed the issue.

Hi,

first of all, thank you for developing and supporting these awesome products.

I witnessed a similar issue upon running continuous replication on a VM after growing one of the disks on the source side. I run delta backup to a NFS share and continuous replication to another XCP-ng host in one job.

The most important part of the relevant log messages remind me of this issue - this topic is the only similar reference I was able to find, so I hope this is the right place to post. If not, please let me know, and I'll create a new topic 🙂

Mar 21 01:00:29 xcp-ng-2 xapi: [ info||8947241 INET :::80|Importing raw VDI R:3967654dad6b|vhd_tool_wrapper] Executing /bin/vhd-tool serve --source-format vhd --source-protocol none --source-fd 1f47b1fe-a9ea-4bda-ab8e-2101e5677059 --tar-filename-prefix --destination file:///dev/sm/backend/f7aca870-12e0-8352-9f86-f52d575eb313/6cd16448-6839-476d-93b1-2f8b816c827f --destination-format raw --progress --machine --direct --destination-size 0 --prezeroed Mar 21 01:00:29 xcp-ng-2 xapi: [error||8947241 INET :::80|Importing raw VDI R:3967654dad6b|vhd_tool_wrapper] vhd-tool failed, returning VDI_IO_ERROR Mar 21 01:00:29 xcp-ng-2 xapi: [error||8947241 INET :::80|Importing raw VDI R:3967654dad6b|vhd_tool_wrapper] vhd-tool output: vhd-tool: Non-zero size required (either a pre-existing destination file or specified via --destination-size on the command line)\x0A

I'm currently running Xen Orchestra compiled from sources, on commit 5bc44363f9ac9fa534f3247e697f1b3c6991e916. XCP-ng is on version 8.2.0.
I know that this is not fully up-to-date, but after retrying that backup as a first measure, Xen Orchestra ran a full backup for that VM, so I can't reproduce that issue anymore, but I figured posting that here might help resolving the aforementioned issue, if the causes correlate.

Hi @LTSFGriffin

Netbox sync plugin is available in Enterprise tier 🙂

@Darkbeldin I wasn't sure about turning on two-factor. I went through that process and generated the "app password" and it seems to be working.

Thanks for the info!

FYI, we modified the deploy script to be able to automatically modify XOA's VIF to run on the management network.

So even in case of using only bonded networks like @Low351, this will now work.

@davidg said in Dashboard Health gives 'an error has occurred':

5.58.1

That's ancient, so not a valid comparison. It's likely that a recent commit has broken something that they will eventually identify / fix.

I did for sure. But I noticed that a new commit(886ff2cd7) was made literally in about the last hour and after updating again to that version all is good!

@olivierlambert We are using rrd2csv to get host cpu stats into SQL to provide nice Grafana page sorted by pool. It would be nice to dial even further down to the vm's that are running high cpu or have memory burden.

Indeed it is in our backlog : USB passthrough with snapshots
and we will need to groom it (study it) before starting development.

@BenjiReis XO from the appliance.

I hadn't noticed the tasks queue counting up like that before I tried the recipe, but I'm perfectly willing to accept that I'm just not that observant.

Thanks!