From our docs --
XO requires Node.js 18.
From our docs --
XO requires Node.js 18.
Have you tried running vhd-util check
on the affected VHD file?
What does node -v
return?
@k11maris Yes, that's common sense.
There are a few requirements for the import from VMWare process to work correctly --
The dev team is constantly improving this process, so some of these requirement may be changing soon. Also, you may want to switch to the Latest release channel since that will include the most recent improvements to the V2V process.
Hi Andrew,
This feature was added last month, and it appears to be using settings from the template to make this determination. Which template(s) are these VMs using? Can you show us the output of xe template-param-list uuid=<Template-UUID>
where you replace <Template-UUID> with the actual UUID of one of the templates involved.
Regards,
Dan
@jkissane With ESXi 6.5 & VMFS 5 it should work either way as long as the snapshot exists.
@jkissane Please try it with an existing snapshot as I believe that is required.
@jkissane Did the source VM have an existing snapshot when you tried the import?
@k11maris Do you have the guest tools installed on the Windows VMs?
Running grep -B 5 -A 5 -i exception /var/log/SMlog
on your pool master will likely point out the source of the coalesce issues.
Hi,
A lot going on here...
Because snapshots take too much space
I'm guessing that you are thick provisioned. What storage type is being used on the SAN?
coalesce does not work while the VMs are running ("error: unexpected bump in size")
This isn't normal AFAIK, so sounds like you have some type of issue with your configuration
Xen Orchestra is running as a VM and I have a script which also backups this (since I assume it cannot backup itself).
This is incorrect. XO is capable of backing up itself along with other VMs in a single backup job
On monday morning, all VMs were shutdown. The VMs which were running on the pool master were in a paused state.
I recommend that you check your logs on the pool master.
I am wondering if this could be improved with better error handling. Maybe some kind of pre-flight check before starting the backups? And what about the paused state of the VMs?
Like I stated at the beginning, a lot going on here. We don't know the cause until you investigate further, but I can't see how offline backups would have caused this much failure to occur.
@jmannik It's only meant for testing on local storage at this time.
@parsedave Can you share the .vmx file here for @florent to review? I've not seen this error before, but it appears to be related to CBT from VMWare.
I would recommend switching to the "latest" release channel in XOA since it will contain the latest fixes to the V2V process. Also, make sure the VM has at least one snapshot. If you still encounter problems afterwards, then be sure to post the full error log.
@KjellCouck said in Xen Orchestra Lite:
connect to the host via the IP address followed by /xolite.html"
This is correct, but maybe there is something else wrong. Which guide were you following?
If you go to https://docs.xcp-ng.org/management/manage-locally/xo-lite/, it explains how to correctly run XOLite on XCP-ng 8.2.1.
@cyford said in after downgrading xcp host from trail 90% of my vms are not booting..:
just want to say after reinstalling all and recreating the all repositories i do have any disk errors or IO issues
I assume that you meant to Include a not
in there.
@aqua-calc said in Full VM backup is scheduled but not started:
The log is empty
Please check on the CLI.
@aqua-calc Is your XO up-to-date? What commit?
Have you checked the logs? https://xen-orchestra.com/docs/troubleshooting.html#logs
That'll report on the status of the array's disks, I also believe the Vates team was working on getting this information into the Pool Health Overview but I'm not 100% certain on that.
This is available now under Host > Advanced tab, but it will only with XCP-ng 8.3.