Xcp-ng Download Iso
Sofiel Kustra
The primary goal of XCP-ng is to deliver an easy way to deploy a VM based infrastructure using Xen as the hypervisor, and the powerful XAPI to deliver a turnkey, working out-of-the-box solution. XCP-ng is compatible with most x86 servers currently on the market.
To install and test XCP-ng go to xcp-ng.org and follow the instructions in the installation guide. Github repositories are at github.com/xcp-ng, including a complete documentation set covering information about usage and development.
Copyright The Linux Foundation. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page. Linux is a registered trademark of Linus Torvalds. Privacy Policy and Terms of Use
I do wish xcp-ng had support for Veeam without having to install the app on each vm. The built in backup is not application aware but in speaking to the guys are Vates, they seem pretty confident that they can onboard me and make it all work out with their own backup.
Project is alive, my hardware person was out of town, he should be back soon and then things can pick up. Unfortunately I have so much travel planned that I will try to get the hardware in and start in August.
W10 Template with UEFI boot: Scrambled with both VGA and KMS mode.
W10 Template with BIOS boot: Display is not scrambled, but the boot process freezes partway. The last thing onscreen is "xenbus_probe_frontend: waiting for devices to initialise"
I include BIOS boot as a point of comparison, but we are needing to use UEFI mostly. The big problem for us is that there is no way to use Clonezilla to image W10 VMs, as there is no mode that will work under a W10 template (and templates cannot be changed after the VM is created.)
Mostly this kind of issue is related to the Linux kernel/hardware support issue. Since Clonezilla live is based on Debian or Ubuntu... Have you tried Ubuntu 20.04.2 live CD to enter console mode only? Not X-window?
Hi, I had some time to try and dig into this by setting up a VM with a "virtual" serial console as well as the regular console, so I could still console into the VM (albeit now over a text serial console) and run some commands after the vga console froze up. The culprit seems to be the nomodeset kernel parameter that clonezilla uses by default. It seems to set a weird vga mode and the xen virtual EFI vga adapter does not like it. I've attached dumps of both boots (default broken, and working after removing nomodeset) that include dmesg output as well as output from the big info dump command ubuntu recommends running in the case of display issues. The main difference I could find between them are this:
Also, for windows templates, there was 1 other thing breaking it, however this one is expected. WIndows templates have the device-id (a virtual pci device xen presents to the OS) set to 0002 - however linux looks for 0001 (because that's what proper linux templates present). So to boot clonezilla on your windows 10 VMs/templates, you just need to remove nomodeset from the boot options (press e on the default option in the clonezilla boot menu), and before even booting the live iso, change the device-id property of the VM to something linux expects:
Long story short, removing nomodeset from clonezilla boot options remedies this. If the template is a windows VM, you need to also temporarily change the VM device-id. Also, the reason Ubuntu (and other) vanilla linux distros didn't have this problem is because none of them use nomodeset by default, it's supposed to only be used when encountering graphics issues. In fact on the ubuntu live iso, the "safe graphics" boot option appends nomodeset, and ironically it will break the console just like it does in clonezilla. This is probably an issue upstream with QEMU which handles the virtual EFI vga adapter, we will see who we can contact :)
Hi Steven,
I downloaded the latest versions, neither solved it. Worked fine on the source (esxi7, win10) but on the target I got the garbled screens (fresh xcp-ng latest w xen orchestra home compiled. Inside xen orchestra as well as xcp center I get the garbled screens.
After trying several builds of the amd64 version without success I tried the 686 version and had no issues with the screen or the nic and hard drive. I previously tried the kms option with the amd64 version which doesn't include the vga and nomodetest flags which worked for the video but got messages that it couldn't find the nic or hard drive.
In other news, another XCP-NG user has shared that the 686 Debian version of Clonezilla works fine out of the box without any messing around needed. I have verified this with the latest 686 Debian available as of writing.
my install works and shows in cloud dashboard, but it is not loading in the xcp-ng plugin
as per Xen XCP-ng Learn Netdata
I have installed xen-dom0-libs-devel and yajl-devel before running --reinstall
References are unique internal XenAPI identifiers. Each object, including hosts and VMs, has one. XenAPI internaly deals with the objects using references instead of names like xcp-ng-r740. Anyway, it seems that Ansible module somehow at some point got a corrupted or invalid reference to a host or the host is missing.
Bvitnik,
Do you think that I should to try execute this playbook, but using other template? In this case, I would create a new template, and run a playbook to see if with a new template the problem does not repeat itself?