Thanks for the info. Hard to tell if it's related or not, but we take any info you can provide on your setup Thanks!
Controversial posts made by olivierlambert
-
RE: Very scary host reboot issue
-
RE: XOSTOR hyperconvergence preview
Likely a question for @ronan-a
edit: however, I'd love to have a chat with you to discuss your existing k8s workflow with XCP-ng/XOA!
-
RE: EACCES: permission denied on xo-ce backups
Hi,
For any usage of 3rd party scripts, please ask on the Github provider of that person
-
RE: XO Hub Template: what do you want next?
Noted for CoreOS and ClearLinux (I'm not sure Clear got Xen drivers bundled but I'll take a look)
@HeMaN you need to use CloudInit capabilities, there's no passwd (user is
debian
) -
RE: XCP-ng Centre 20.04.01 - VM Autostart on Server Boot not working
That's why we sell support So you don't have to understand everything (which is OK I mean, but if you don't have time, we are here for you!)
-
RE: Add server, Connection Failed
This is so basic that it must be a configuration issue somewhere.
I would start to see if locally XAPI is answering, by issuing
xe vm-list
on the host itself and see if there's a valid answer.Then, to avoid any configuration issue, I would use a XOA Free to deploy and see if it works
-
RE: XO from source and CentOS 7
Indeed So OP thought there was a CentOS 7 support at the first place, I don't know where he found this information.
edit : and Happy new year too!!
-
RE: ova problems
So XOA import works. You are a bit vague on "the VM doesn't work". Can you be more specific? I mean, it's hard to assist with only that data.
-
RE: ova problems
Please re-read my post. Now we evacuated the OVA import issue, it's a problem of having the operating system to load.
You can use a live CD (like Ubuntu) in the VM and try to see what can you see inside the VM disk.
-
RE: WHMCS integration
We'll be happy to assist on what you need API wise to make it real
-
RE: S3 Remote with encryption: VHDFile implementation is not compatible
Ah I see, it's by default on S3, it was added after the initial S3 release. Maybe you created your remote in the past?