@Greg_E said in XCP vm fails to boot after newest kernel applied.:

@bberndt
I just installed a fresh Alma 8, did yum update to see what would happen, and it's still working. Gave out the same kernel as above.

This was installed UEFI on XCP-ng 8.3 which was a fresh install a few days ago from a nightly (near release?) ISO. It was installed to an NFS share, 2 cores and 4GB with an Intel i1000 interface. Xenserver tools 8.4.0-1 installed.

There are no extra packages installed yet, could this be a package conflict.

Anything else I can check to see why mine works and others are failing?

Hmm....I did the same and that VM died just like any other with the broken kernel.
Although I used the Cloud Image so not completly new install from scratch.
Maybe I'll check building a new cloud image what will happen then.

@Murf There is a blog post about using XenOrchestra for a dynamic inventory.
https://xen-orchestra.com/blog/virtops3-ansible-with-xen-orchestra/

Creating VMs is usually a job done by terraform and not ansible. I know there is an ansible collection for VMWare which can do that but as far as I know there is no collection that is able to manage VMs and sadly Satellite's virt-who doesn't seem to have XenOrchestra support at the moment and since RedHat is pushing OpenShift I don't think it will ever come.

But there was a wish for a colletion on the DevOps Megathread
https://xcp-ng.org/forum/post/88993

Upgraded my dev Pool

2 HP EliteDesk 800 G3 Mini
One with i5 6500T and one i7 6700T
Both 32GB RAM, SATA and NVMe Storage
1x Intel NIC
1x RTL8139 NIC

Updated Master first and then the second node. No issues so far.

@nathanael-h said in DevOps Megathread: what you need and how we can help!:

@bufanda I think we'll be able to add backup support to Terraform when 1. the provider will use the new Rest API, and 2. when this API will offer endpoints for backups management. I took note. (This won't be done in minutes )
About Ansible, it'll depends also if/when we start work on it.

No worries it's not a critical issue for me. It's jsut been on my wish list and I already was about to look myself into it by either writing some ansible module for it or finally have a reason to learn go but as you said the current API has some limitations in that regard.

Backup management with the Terraform provider would be a great feature. Maybe also for an upcoming ansible module. I always struggle to find the right backup for a VM since I grouped them in logical groups. So one Backup may handle multiple VMs and Sometimes it would be just easier to edit some IaC then the GUI, especially when I destroy a VM, I always forget to check if Backups exists.

In the Tasks menu on the left it should show all active tasks including the VM creation or it's sub tasks like VDI cloning.

@gb-123 said in XCP-ng 8.3 betas and RCs feedback :

@stormi @olivierlambert

I have also successfully run a test install of RC1 on my lab. Everything seems to be working fine. The TLS issue also seems to go away (will also put a separate post on the topic concerned).

Good Job guys !

One thing I noticed :

I seem to get an error message

no crontab for root

while running crontab -e the first time.

Is that normal? Is it ok to run a cron job for root ?

Could be very well happen if you have a fresh install and no cronjobs in the crontab. Most distributions would put corn jobs in /etc/cron.d anyways and so does xcp-ng too. And the users crontab then will be created on the first edit.

@gb-123 I don't see the relevance of performance. It's in both cases the same software running it's just diffrent how a boot is handled and UEFI has some more security features to ensure the OS running on the hardware is authentic where as in BIOS malware can easily overtake the OS or tamper with the OS.

In normal operation you wouldn't see performance diffrence in my opinion.

@Houbsi Did you setup the pfsense VM according to the guide?
https://docs.xcp-ng.org/guides/pfsense/

@456Q XenOrchestra will create a Snapshot during the migration as far as I understand the process.

@jkissane Did you try to migrate the VM while it is running? I personally don‘t really have experience, but as the V2V was designed with almost 0 down time could be it is reading some Informations VMWare is only reporting on running VMs. Just a thought.

@nikade Yeah for my small homelab I don't need as much, but I can see it in a enterprise environment be useful yes.

Hi,

I see this driver is ZFS only at the moment. I have a question regarding ZFS though I am not really familiar with it and only started to read in to it recently (Still an ext4 enjoyer) and from what I gathered is that ZFS can be pretty memory hungy, but how does that fit into the dom0 with only 3GB RAM or so or in general with a Hypervisor where the memory should be used primarily for Guest OSes. Are there any draw backs in using ZFS. Will it perform poorly if not getting enough RAM for cache operations. Or is that more a thing for NAS that use ZFS to serve shares. Maybe an expert on that matter can enlighten me.

Thanks and I will see if I can free up a drive in my test pool to test the driver.

@wtdrisco There should be no Problem if the core counts don't match. you just can't place a VM that has 32vCPUs on the 24 core host.

But one thing you should have equal over all hosts is the amount of network interfaces and also have them configured equally (which should be done by XOA/XO form sources). Otherwise a VM might not migrate because a network Interface is missing on the target host.

Also passed through hardware might prevent migrating to another host.

I run a pool with two diffrent hosts, one has 8 Cores and one only 4 cores, also one has 64 GB RAM and the other one has only 32GB and in this limitations I can easily migrate VMs back and forth between hosts.

@gb-123 In case of restart I never had it reverted only in case of update. After an update I just run an ansible playbook to add my whitelist entries again. sure it's a work around and some include file like usb-policy.conf.d/*conf would be nice to have.

On an HP EliteDesk 800 G3 35W Mini i5 6500T

XTF:
with no-exec-sp:
All Test SKIP/SUCCESS

with exec-sp:
Hard Freeze.

dom0 Test all Tests passed.

Installed on a HP EliteDesg 800 G3 Mini running 6VMs Linux nad FreeBSD all iwith UEFI one Linux with vTPM so far no issues. Will keep monitoring and testing.

@stormi Tested the new edk package at looks good to me. was able to reboot linux and freebsd VMs without a hitch with UEFI boot mode.

@stormi Thx for the info. And I understand that there is no guarantee, was just curious if I had a problem on my cluster or if there was really nothing inbetween. It's a test cluster in the end so no mission critical things running on it anyways.

@stormi Yeah sure, just thought it may help with the issue that was reported if the container used is outdated.

But anyways to the topic of XPC-NG 8.3beta. Are there any updates planned in the near future it has been a while since I recieved Updates on my test cluster. And while I don't run an AMD Processor on my test cluster there were security fixes for 8.2 but they didn't made to my 8.3 or did the repo config change and I missed that?