Much much cleaner and readable, very professionnal in look and feel. Great job guys

Amazing guys ! By this way, the platform will become better than ever
I will follow this very closely.

Keep going !

Done

Tested on Fedora 33 and CentOS 8 Stream (can't test live migration in my homelab)

• Fedora 33 : nope at all

  It failed because of chkconfig requirements and legacy init system unit => no more supported in
  very recent version of systemd (here is 246 for Fedora). The officiel RPM from Fedora xe-guest- utilities-latest doesn't have these issues.

• CentOS 8 Stream : way better than Fedora

  • IP addresses reporting : OK
  • Management agent detected : OK
  • Clean shutdown/reboot : OK

Tested on Windows 10 1903 (French locale as usual), seems good too and easier than ever.
I let you know if something bad happens.

Wow didn't expected this kind of news so early after the launch of the project.
Congrats team, this is so much merited

No problem here, RHEL 8 support for guest tools works as expected (tested on the last RHEL 8.1 release), good job

Just updated my homelab server from XCP-ng 7.6 to XCP-ng 8.0 Beta, so far so good. I also tested the new experimental UEFI mode with Windows VM, seems good too.

I also tested the new XOA deployment through the Web interface of my host, perfect !

We will see during the following week how it goes

Niiicce Especially the new quick XOA deployment, that is more turnkey than ever
I will migrate to XCP-ng 8.0 in my lab this weekend and start provide some tests.

I continue to work on it but the results are not that good. The main problem is one of the main feature, "everything is container".

I managed to start the xe-daemon in a privileged CentOS container by installing the xe-guest RPMs, but only the show of virtualization mode worked, nothing for the network or soft shutdown. RancherOS should work in PVHVM mode by default for sure due to it's recent 4.14 kernel btw.

I hate give up on things, but I start to think more and more to use CoreOS instead of RancherOS, and use Rancher Server or RKE on top, it will be the same and much more hassle-free. Moreover, the XenServer tools supports CoreOS, it's clearly a better way to proceed.

Regarding to logs on the machine where the network configuration is commented, there is this error : 2021-06-20 21:22:59,657 - util.py[WARNING]: Getting data from <class 'cloudinit.sources.DataSourceNoCloud.DataSourceNoCloudNet'> failed

No other errors, but it seems sufficient to broke the provisionning.

Commented :

Empty :

Seems consistent imo.

I can confirm this behavior :

• empty/generic network config (i.e basic DHCP) : OK
• commented : not OK

@olivierlambert I must be blind, no other explaination....

Hello everyone !

I have a question about memory in general with XCP-ng (pure curiosity).

I have my homelab host with 64GB of RAM, so the Dom0 memory is about 4.2GB, all fine (and it's correct according calculation provided by Citrix : https://docs.citrix.com/en-us/citrix-hypervisor/memory-usage.html)

But when I looked in Xen Orchestra memory stats graphs, it indicate me that 5.28 GB is used on the host (with no vm running). Using the xe CLI, I got the same information (using the commands provided on the link above).

Is there some kind of "overhead" or memory reservation by the Xen hypervisor itself under the hood (or something else) ? I can't find any information about this.

IIRC ESXi has a more or less similar behavior where it reserve some memory for it's own operations, dunno if it's the same here with XS/XCP-ng.

Nested virt is quiet random and not viable sometimes. I already had case where nested virt won't work on a recent i7 and worked wonderful on old CPU

@stormi For now, only a sysvinit script is available right ? If needed for systemd, can we re-use the unit from the Fedora packagers ? Looks pretty simple :

[Unit]
Description=Linux Guest Agent
ConditionVirtualization=xen

[Service]
ExecStartPre=/usr/sbin/sysctl net.ipv4.conf.all.arp_notify=1
ExecStartPre=/usr/sbin/xe-linux-distribution /var/cache/xe-linux-distribution
ExecStart=/usr/sbin/xe-daemon

[Install]
WantedBy=multi-user.target

Tested on Fedora 33 and CentOS 8 Stream (can't test live migration in my homelab)

• Fedora 33 : nope at all

  It failed because of chkconfig requirements and legacy init system unit => no more supported in
  very recent version of systemd (here is 246 for Fedora). The officiel RPM from Fedora xe-guest- utilities-latest doesn't have these issues.

• CentOS 8 Stream : way better than Fedora

  • IP addresses reporting : OK
  • Management agent detected : OK
  • Clean shutdown/reboot : OK

I didn't try the provider, but there is an option cloud_network_config, you should be able to pass network config as in Xen Orchestra UI using cloud-init.

Much much cleaner and readable, very professionnal in look and feel. Great job guys