Hi @McHenry .
You should obfuscate the IP address in your first screenshot. Also check your profile and private chat
Hope everyone had a joyful Christmas and I wish everyone the best for 2026.
Regards,
Marc
Terraform provider release v0.37.0
Enables the secure boot parameter for the VM resource
Terraform provider release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.0
Hi,
There's no known mount issue at the moment. You can use SMB or NFS.
XAPI is not able to push files, when you backup, an HTTP handle is created in the dom0, so it has to be fetched by something (XO in this case, or a proxy).
@nicolai-comar said in Error when taking a snapshot in XO:
xo-server 5.12.1 and xo-web 5.12.0
Those are really out-of-date. Please update to the latest available versions and try again.
@busthead If you are importing a VM from your browser, you should not navigate away from XO as it will interrupt the upload. You can navigate to another page of XO though.
I concentrated here, after upgrading my second server:
Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /root/xen-orchestra/node_modules/argon2/lib/binding/napi-v3/argon2.node)
I've found circumstantial evidence that this depends on libraries found in newer gcc than is in the Cent OS 7 repo at this time.
strings /usr/lib64/libstdc++.so.6 | grep CXXABI
CXXABI_1.3
CXXABI_1.3.1
CXXABI_1.3.2
CXXABI_1.3.3
CXXABI_1.3.4
CXXABI_1.3.5
CXXABI_1.3.6
CXXABI_1.3.7
CXXABI_TM_1
so argon2.node requires something newer than centos7 can provide?!
and upgrading gcc does the trick? I may have to try when I have more time.
https://stackoverflow.com/questions/63374392/node-module-argon2-usr-lib-x86-64-linux-gnu-libstdc-so-6-version-cxxabi-1
Indeed here is Centos 8.
$ strings /usr/lib64/libstdc++.so.6 | grep CXXABI
CXXABI_1.3
CXXABI_1.3.1
CXXABI_1.3.2
CXXABI_1.3.3
CXXABI_1.3.4
CXXABI_1.3.5
CXXABI_1.3.6
CXXABI_1.3.7
CXXABI_1.3.8
CXXABI_1.3.9
CXXABI_1.3.10
CXXABI_1.3.11
CXXABI_TM_1
CXXABI_FLOAT128
and yes, I understand that XO doesn't target CentOS, but its our 'standard' right now.
@bsodmike Increase memory to node.js as described in the docs under memory management. Adding mem to VM is insufficient in isolation, so my post above may have been misleading (sorry!).
@olivierlambert I think that the default behavior should be VMs stay on the SR that they are on. If you are taking a host down and moving the VMs to another host why would you move the VM storage location, that defeats one of the reasons you use shared storage.
Hi,
See https://github.com/vatesfr/xen-orchestra/issues/1426
fufroma created this issue in vatesfr/xen-orchestra
open
Virtual keyboard for console
#1426
Yes, that's the plan: involving community for feedback. But keep in mind we don't want to make a clone of XenCenter
It's a web application, so it comes with some perks but also drawbacks from a heavy client (you are running in a browser with XO, and we don't want to change all web behavior without necessity to do it).
Thanks for the feedback (so feature wise I think we are at parity level, UI it's another story I agree)
It's not a matter of believing, it's a matter of providing a way to reproduce the issue It's really hard to fix something if:
we aren't aware of the issue
we can't reproduce it
Not enough space means not enough space to coalesce, and therefore XO will prevent to continue and fill entirely your storage because of uncoalesced chains.
@tonyp90 I did file a feature suggestion, https://github.com/vatesfr/xen-orchestra/issues/4273 , but not a bug report.
I'm using the xsconsole on the xcp-ng server itself in the few cases where I need to re-attach an SR.
gitterdude created this issue in vatesfr/xen-orchestra
closed
Reattach SR icon is non-obvious
#4273
