Hi there. Author of said inventory plugin.

If you ever wish to migrate you should be able to retain most of what you did on XOA side (I'm thinking tags), but you'll have something that's more standard and require less setup as long as the XOA API is accessible to the machine running the playbook.

You can keep the groups with the composable groups in your inventory plugin configuration:

simple_config_file: plugin: community.general.xen_orchestra api_host: 192.168.1.255 user: xo password: xo_pwd validate_certs: true use_ssl: true groups: kube-master: "name_label == 'kube-master'" compose: ansible_port: 2222

https://docs.ansible.com/ansible/devel/collections/community/general/xen_orchestra_inventory.html#ansible-collections-community-general-xen-orchestra-inventory

Hii,

yes its working,
but not the second 2.5 Gb ethernet, since it requires newer kernel,
same with PCI passthrough the wifi card is new popular AX200 which requires newer kernel also,

I have USB passthrough a Wifi USB adapter, the speed looks underperforming, but i haven't test the adapter plugged in to laptop and see its speed comparison,
I didnt ask much about it, since I guess its not coorporate use case except closely to edge computing? maybe not too important?

if you need other info, you can tell me, perhaps some logs or debuging, i will share 🙂

@axiom00 No I was not able to get it working.

No, I don't know where the problem resides exactly.

Hi all!

A new ISO is available here to test IPv6 in dom0.
Whats new:

aligned patches with Citrix upstream merges fix regardings tunnels, Sriovs network, VLAN and bonds when creating from IPv6 PIF netinstall support in IPv6 (netinstall repo info coming soon) NFS support in an IPv6 Pool

Do not use this in production this is an experimental feature!

What to test?

upgrade from an already configured IPv6 host netinstall when a repo will be available what you'd normally do with an xcp-ng host

For fresh installs, do not forget to add the ipv6 rpm repo for future updates:

[xcp-ng-ipv6] name=XCP-ng IPv6 Repository baseurl=http://mirrors.xcp-ng.org/8/8.2/ipv6/x86_64/ http://updates.xcp-ng.org/8/8.2/ipv6/x86_64/ enabled=1 gpgcheck=1 repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xcpng

For existing IPv6 hosts, yum update --disablerepo=* --enablerepo=xcp-ng-ipv6

An easy way to automate VM template build, like an up-to-date packer plugin, would love a terraform ressource

Xen and Linux kernel inside XCP-ng are completely custom, so it's pretty different than the those shipped in CentOS or even Alpine.

Unrelated. vGPU isn't GPU passthrough.

@abatex

I solved the problem by removing the external hard drive that I use for backup windows backup.

The update is now available for everyone https://xcp-ng.org/blog/2021/01/28/security-issue-in-sudo/

Has anyone tried importing VM with XCP-ng Center 20.04.01 to XCP-ng 8.2? I'm getting 1Mbps transfer speed.

When I connect the same XCP-ng Center 20.04.01 instance to XCP-ng 8.0 and do an import I get 100Mbps transfer speed.

Anyone can help?

I suspect the slow upload during import is related to this... https://xcp-ng.org/forum/post/34970 ?

@ricardowec I completely second @olivierlambert here. Although there is potential for security issues with an OS that loses support, a hypervisor should be treated with extreme caution anyway. I personally never expose a hypervisor in any capacity directly to the internet (for inbound traffic anyway 🙂 ). This practice alongside using very specific and often highly customised software packages should keep everything running smooth.

On top of all this, the underlying kernel, storage systems and such are all custom, so there is nothing really to worry about 🙂

I will be completely open when I admin that I am very new to XCP-NG, but the team seem to be really responsive if you have an issue. I have never seen such fast reply's, even from an unnamed big brand competitor who charge us $$$ for support.

@hoerup Hi, I can't remember too much to be honest.

I created a Debian 10 VM with 20GB disk, set up all the stuff that needed to be common for the Ceph pool pretty much following the Ceph documentation using the cephadm method - so Docker etc. This would be my 'Ceph admin VM'

Once that was all sorted I cloned the VM 3 times, for my actual Ceph pool and changed the hostname and static IP etc. I've got 3 hosts with Supermicro boards that have two SATA controllers on board, so on each one I passed though one of the controllers to the Ceph VM and then just deployed Ceph and followed the documentation. The only issues I ran into and any other tips are in the other post I linked to. Now Ceph is all containerised it all seams a bit too easy! Hope they're not my famous last words!! 😖 It does like a lot of RAM, so I've reduced the OSD limits down a bit and its fine for me.

Cheers.

@r1 said in XCP-ng 8.2.0 RC now available!:

@jmccoy555 said in XCP-ng 8.2.0 RC now available!:

CephFS is working nicely, but the update deleted my previous secret in /etc and I had to reinstall the extra packages and recreate the SR and then obviously move the virtual disks back across and refresh

Were you not able to attach the pre-existing SR on CephFS? Accordingly, I'll take a look in the documentation or the driver.

No look. I ended up with a load of orphaned discs with no name or description, just a uuid so it was easier to restore the backups.

I guess this is because the test driver had the CephFS storage as a NFS type, so I have to forget and then re attached as a CephFS type which I guess it didn't like! But its all correct now so I guess this was just a one off moving from the test driver.

Anyway all sorted now and back up and running with no CephFS issues! 🙂