@JCS-RVK You likely need to install the dependencies to use with VDDK.
This is a WIP from the vates team where you can find information regarding it here https://github.com/vatesfr/xen-orchestra/pull/8840
My guess, and I'm still sorting it out for my GH is that you likely need to run sudo apt install libnbd-bin nbdkit nbdkit-plugin-vddk on your XOCE installation, but that is just a guess at this time as the VDDK version number is also in flux (going from 9 to version 8 ) etc.
@ccesario There is a running topic regarding the 2TB limit and removing it with QCOW/2 format https://xcp-ng.org/forum/topic/10308/dedicated-thread-removing-the-2tib-limit-with-qcow2-volumes/156
I've not kept up with it as I don't have this issue, but this is very much a work in progress.
@Forza said in NVMe SSD not found when installing:
We have been using software raid1 for years on Intel hardware for industrial focused computers. However since Intel switched to VMD we started to get very odd problems like blue screens (windows) and spontaneous reboots and hard lockups where the raid volume wouldn't come back unless we did full power cycle. After some months we found a reproducer which we sent to our vendor, who in turn were able to reproduce it on different motherboards of different manufacturers with different chipsets supporting VMD. Until today we have not found a fix.
Yeah this doesn't sound any different from every fakeRAID that has ever existed... it's doing all of the work on the motherboard, writing little to disk and hoping for the best.
@olivierlambert said in NVMe SSD not found when installing:
@DustinB Last time I checked, VMD is a shitty half-baked soft/hard RAID.
@Forza said in NVMe SSD not found when installing:
@olivierlambert said in NVMe SSD not found when installing:
@DustinB Last time I checked, VMD is a shitting half-baked soft/hard RAID.
Indeed. The firmware hides pci devices behind this vmd thing. It is absolutely unstable and unfixable.
Good to know, will steer well clear of it.
@TeddyAstie said in NVMe SSD not found when installing:
Hello,
Make sure Intel VMD is disabled (this is the hardware RAID feature of Intel, and it doesn't currently work on XCP-ng; you probably don't need it unless you are looking to make a RAID). We found some modern platforms enabling by default (which also causes issues with Windows).
Is VMD actually hardware raid or is it some bastardization of Hardware Raid?
@kevdog a memtest is going to check the physical memory for any issues, if you're not seeing any other errors on other VMs I would lean more towards this VM having some kind of corruption issue.
A memtest won't hurt and it would help to eliminate a possible issue, it would definitely take some time to complete, which may not be an option if you have any sort of uptime requirements.
@AlbertK said in XCP-ng - XOA vs. XOCE:
@Danp ,
Is it possible to add the comparison of the XOCE together wit XO in this page?.
https://vates.tech/pricing-and-support/#features-matrix
XOCE is a term that I came up with when I originally started writing the deployment script that exists today.
It's stuck around. Vates uses the terms XOA and "XO from Sources" as their unique products. XOCE would be "you used a github script to deploy" (my github) XO.
XO from Sources is a completely manual process where you're following the documentation to deploy XO. This approach gets you the same thing that XOCE does, but takes longer to complete since you're finishing each step over SSH rather than running a single bash command on a Ubuntu/Debian VM.
@L1512191 Dan answered, but there are features of XOA that are only available from having a support agreement with Vates. If you don't need those features or can use other approaches for the things that you might need, then XOCE might be for you.
@L1512191 said in XCP-ng - XOA vs. XOCE:
Forked discussion from https://xcp-ng.org/forum/post/96400
I read the readme of the XOCE installation script. Nice job @DustinB!
Can someone tell me about the limitations of XOCE, compared to XOA? I assume there are some, as XOCE "is not officially supported by the Vates team", but please correct me if I'm wrong.
XOCE is offered free of charge, support is offered from that community (also free of charge). It is not officially supported by Vates, as Vates is the business that has created XO and XCP-ng, they sell support, but you could also use XOA free which has limitations on its functionality.
XOCE is built from the source documentation and is unrestricted to what you can do, but support is from good will, and best effort rather than paid support of the Vates organization.
XOCE gives you a completely functional system that works to manage, backup and restore your VM's that is available from the source documentation. Features that are only available from XOA Hub, aren't available. This is because the Hub is tied to a license that you would get with your subscription from Vates.
Otherwise there aren't any "limitations" it's that XOCE literally has no way to get access to that particular feature.
@Piefje01 I'd say try to read the help docs of Vinchin but their website doesn't seem to be working properly... https://www.vinchin.com/vm-migration/xcp-ng-live-migration.html
You could use any V2V migration tool, I think StarWinds has a V2V tool that works too - https://www.starwindsoftware.com/starwind-v2v-converter
I can't speak to the validity of it though.
This is likely an HTTP limit of the S3 bucket where it only shows so many records at once over HTTP. B2 has a similar issue if you're viewing your bucket and files over HTTP.
Over an SSH session you can list everything.
@jangar This doesn't make a lot of technical sense.
You should keep your software/firmware up to date as these are updated to address different issues.
Pinning your firmware to a specific version doesn't make sense.... because that version may have major issues with it that are fixed in a later update...
@r10n_fumo Why are you unable to install the guest tools into a given VM?
That seems like the better approach without some sort of justification..
@L1512191 As @Danp said XO Lite is a Work In Progress, so while the functionality is shown, it's only displayed as coming soon.
You can deploy the XOA Trial to get going (highly recommended) and immediately as soon as the Trial is working and your environment configured I'd recommend you deploy XOCE.
The Trial is just that, a trial and good enough to get started.
XOCE is an installation process that follows the from Sources documentation, and is a completely operable solution. You can check out my profile or just google "XOCE github".
As @Andrew said, your host itself is unhealthy, you might be able to disassemble the CPU and heatseat, clean it up and add some new paste to address the issue with the CPU overheating (if the paste is shot).
As for the memory issue, run a memtest on the host and see what is reported.
@cichy You can absolutely install netdata on your hosts https://xcp-ng.org/forum/topic/2288/netdata-package-is-now-available-in-xcp-ng, you simply don't get a SPOG from within XO unless you're on XOA.
It certainly appears that netbox can be configured as well on XOCE
This install is using my script, I can't speak for ronivoy's but the plugin is definitely there.
@john.c So hypothetical issues that may require paid support for a testbed is your concern. Is that correct?
@john.c point being? Nothing prevents this person from getting XOA once they are live, but staging and testing XOCE has been completely stable.
@cichy said in Pre-Setup for Migration of 75+ VM's from Proxmox VE to XCP-ng:
@john.c correct. It's the auto updates and automations that come with the appliance that I am after. I believe the trial is only one month? Or possibly only 15 days? The support element is mostly irrelevant to me/us. I do a fair bit of automation via Ansible/Terraform, so developing our own unique library of Templates is ideal. Again, new to all this. So, it may just be that I've not come across this within my XO from "sources" build
Take a look at my provide or lookup Jarli01 on GitHub if you want a simple yet effective installation and maintenance approach to installing and managing XOCE.
Yeah holy cow ~18K Petabytes of storage space... that was definitely a pretty penny, I just hope it's not an OBR5, lol.
