If you already tried to use the OVA appliance of Wazuh, you probably saw the Wazuh splash screen, and then left with a black screen.
Unlike the Dell OME appliance (https://xcp-ng.org/forum/post/78651), the fix is pretty simple: we just need to reconfigure the grub.

To do that:

• Boot with any live CD with rescue you want (I use Debian)
• Follow the installer, and mount the /dev/xvda1 partition, and execute the shell on /dev/xvda1
• cat /etc/default/grub, you should see this file:
  
• From here, you can vi /etc/default/grub replace /dev/sda by /dev/xvda. Then :wq
• To reconfigure the grub, just do a grub2-mkconfig, the grub will display all its config.
• When the grub is done vomiting all its configuration, umount the DVD on your VM, and reboot, and tada !

To install the tool, log in the console, sudo -i, plug the guest-tools.iso, mount /dev/cdrom /mnt, and bash /mnt/Linux/install.sh -d rhel -m 9
The tools are now installed !

If you have a question, don't hesitate to ping me !

@AtaxyaNetwork And for the blog post:
https://blog.ataxya.net/add-xen-driver-to-ome-dell-open-manage-enterprise/

@rk9268vc Hi !

i'm confirming the issue:

I'm currently digging, shoud be a missing driver or a harcoded /dev/sda, as usual.....

will report back.

@CloudX0520 Personally i use Dark reader extension on Firefox, so every page is in dark mode by default

@cichy the documentation for the Kvm/proxmox part is really weird with unnecessary steps

Normally you just have to do:

qemu-img convert -O vpc proxmox-disk.qcow2 `uuidgen`.vhd
scp thegenerateduuid.vhd ip.xcp-ng.server:/run/sr-mount/uuid-of-your-SR

Then with XO, create a VM and attach the disk

I really need to find some time to finish the rework of this part of the docs, I'm sorry I didn't do it earlier

@Statitica I don't think you can change the template on the go (but I might be wrong)

The safest way is to create a new VM with the right template, same spec, without disk. Then don't boot it, shut the VM with the wrong template, detach the disk (rename it if the name is not obvious), and attach it to the new VM with the right template.

@anik Hi !

When I did migrate from Proxmox to XCP-ng, I just had to do the conversion and import the disk. The step in the documentation was not needed (I suppose it's for old OS or in case of failure)

You can convert directly to VHD instead of convert to VMDK. Here's the step I followed:

qemu-img convert -O vpc proxmox-disk.qcow2 `uuidgen`.vhd
scp thegenerateduuid.vhd ip.xcp-ng.server:/run/sr-mount/uuid-of-your-SR

Then with XO, create a VM and attach the disk

@BenjiReis Hello !
Thank you for the ISO !

I just tested the install in a VM (for the moment, soon I will have a physical machine available)

First review:
So far, the autoconf seem to be working !
But, during the installation, I provide a IPv6 DNS (the Cloudflare one, 2606:4700:4700::1111), but DNS is not working, as I have 1.1.1.1 in my /etc/resolv.conf
I don't know if is the autoconf who is pushing the 1.1.1.1 (i need to check my router first), but I think is better if when we give a DNS, it bypass the autoconf

More test is coming the next few day

(sorry if my English is a bit bad)

Thank you and the team for all you work !

Hello all !

I was able to make some tests these last days on my lab servers.
My lab is currently 1 Dell R610 with IPv6 only. I plan to add 2 more servers to test all the features.

I already noticed some blocking points:

• The DNS server (v6) that I gave at installation is no longer present once the server is installed. I had to edit /etc/resolv.conf and add my server by hand to have working DNS.
• Once the server is installed, I tried to do a quick deploy via https://xen-orchestra.com/?#!/xoa, without success. I asked @olivierlambert to add a AAAA DNS record, because it was not there in the first place, but once the record was added, the quick deploy still didn't work. I don't have any debug message to give back, and I don't know how to debug more

Feel free to contact me if you want to do some live testing, or if you need more information !

Thanks for all this work !

Cécile ~ AtaxyaNetwork

@olivierlambert Seems to work perfectly on Debian 12 and Debian 11 !

@carloum70 Yep I tested on XOA, latest version
You can use https://vates.tech/en/deploy/ to deploy the XOA, register for free and reimport your XO configuration

@carloum70 I just tested on my side, I had some error because other disk was mounted, but after a xo-server restart, it works as expected

Debian 13, UEFI + LVM

# lsblk -f
NAME                        FSTYPE      FSVER    LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
xvda
├─xvda1                     vfat        FAT32          C1A9-1A42                               477.2M     2% /boot/efi
├─xvda2                     ext4        1.0            54c89c90-ac93-4ee2-9ff3-11930697a3de    739.2M    15% /boot
└─xvda3                     LVM2_member LVM2 001       T01yqz-9m5K-j5gW-6XWB-p1vz-VTjI-LFSO6A
  ├─rootvg-root             ext4        1.0            c8573984-d3a7-4548-b43b-b106e9a5f413      9.6G    30% /
  └─rootvg-swap             swap        1              8004e072-be5f-436a-a202-45afe3067eb4                  [SWAP]
xvdb                        LVM2_member LVM2 001       nZhQHF-x7lS-crVW-vlQq-zkJ7-dZMZ-cWZOxM
├─datavg-var_lib_docker     ext4        1.0            adfbddc2-1625-4f27-b041-e6003b4679f5     14.1G     4% /var/lib/docker
└─datavg-var_lib_containerd ext4        1.0            253cd0a7-cc7a-4062-aed0-2efd53aff322     10.5G    27% /var/lib/containerd

If you are running XO form source, can you try with an XOA ?
Are you running an XO source with LVM for the OS ?

@carloum70 Hi !

Could you tell us which version of XOA you're using and what guest OS the disk you want to mount comes from?
Also, is it BIOS or UEFI?

My boyfriend submitted a PR a while ago to fix LVM + UEFI disk mounting. It fixed file restore for the guests we tested, but we might have missed some rare cases. Maybe we can provide a fix base of the info you can give

@bvivi57 Hello !

Déjà bravo pour le travail d'écriture, faire plusieurs articles aussi long, avec screenshot et commandes CLI intégré, c'est un boulot de fou !
J'ai rapidement parcouru tous tes articles, je prendrais le temps de tout relire pour te faire un feedback complet avec quelques tips, si tu le souhaites !

Sur le dernier article, j'ai vu que tu as redémarré xo-serveur parce que tu n'arrivais pas à te reconnecter au master: tu peux (dans XO5, pas encore XO6) juste aller dans setting server, et cliquer sur le bouton "disconnect" et "reconnect". Ça va forcer une reconnexion à la XAPI, et si elle est disponible, ça va reconnecter ton pool instantanément à ton XO.
Redémarrer un XO, surtout si tu as plusieurs pools, peut avoir certaines conséquences : Si tu as des backups en cours, ça va les kill instantanément, pareil pour les migrations entre deux pools différents. Il faut y aller doucement avec un systemctl restart xo-server

En tout cas merci pour ces articles, je suis heureuse de voir que la communauté francophone s'intéresse de plus en plus à l'écosystème XCP-ng/XO (et je dit ça en tant qu'"early" qui utilise la solution depuis... longtemps ! )

@fdhabhar Hi !
IIRC the host affinity is checked by the XAPI only at the start of the VM, not during its life.
So it's "normal", but not ideal, I agree

@Dezerd Hi !

Just add the third host via New -> Server, it will appear as an independent host in his own pool (assuming the third host was just installed).

@SuperDuckGuy Hi !

Are you on XOA trial and/or air gap environment ?
I remember seeing the -32000 error a while ago, but I don't remember why

You are looking on the host, right ?

Hello everyone !

I rebuild a new OME appliance with the latest version (4.6)
Dell decided to give this appliance Proxmox, Nutanix and OpenShift compatibility, but no XCP-ng yet... If someone from Dell want to reach out about this, please contact me !

What i did on the rebuild:

• Via live CD
  • add xen-blkfront and xen-netfront driver, and rebuild the initrd
  • change root password
  • activate SSH.
• Via SSH

sed -i -e 's/sda/xvda/g' /opt/dell/omc/utilities/tui/bin/ome_disk_config.sh
sed -i -e 's/sda/xvda/g' /opt/dell/mcsi/appliance/scripts/appliance_resources.sh
bash /mnt/Linux/install.sh # To install XCP-ng tools

As usual, please send a DM if you want the link to the VHD

Feedback is welcome !

(Disclamer: This build is something I create on my free time and to help people who have difficulty running Dell appliances on XCP-ng. I do not guarantee a fully functional appliance, but I do my best to make it work. If you have a support contract with Dell and require official support for OME, please contact Dell and request compatibility with XCP-ng.)

@fluxtor Hi !

First thing to check is dmesg -T, to see if you have any hardware error