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

@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 !

@pavkamlc Hi !

Usually I convert my qcow2 file to VHD directly on Proxmox.

As far as I remember, when I crashed my Proxmox in the school lab, I didn't succeed to convert the image directly on a Linux box.

I found a workaround, but it's pretty messy:

• Install a Debian VM
• Install the proxmox-ve package (you'll need the Proxmox repository)
• Mount your shared storage directly on your new VM (with NFS for example).
• Then, you can convert

Let me know if it's working !

@kuznetcoff777 Hi !

If you want all the feature, you can use XO from sources: https://xen-orchestra.com/docs/installation.html#from-the-sources

If you are using Xen Orchestra for a production environment, I strongly recommend having a pro support for your infrastructure

@screame1 You can do something like this:

cd your_folder_where_xo_is
git checkout fix_continuous_replication
git pull -r
yarn
yarn build

(i didn't use XO source since a long time, so maybe i'm wrong ^^)

@jkissane Hi !

Did you install xen driver before exporting the VM ?
dracut --add-drivers "xen-blkfront xen-netfront" --force

@lsouai-vates (for reference i opened an issue a while ago about this https://github.com/vatesfr/xen-orchestra/issues/6600)

AtaxyaNetwork created this issue in vatesfr/xen-orchestra

open Possibility to make export of research in XOA #6600

@wezke That would be great ! Thank you !

@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.

@Statitica Hi !
Did you install the XenServer or the XCP-ng tools on your Windows VM ?
Without the tools, performance are bad

Also, the "Other OS" template can cause issues, because windows template have some supplemental parameter for Xen (like Viridian, and other thing I forgot)

@TheNorthernLight No problem, buying second-hand hardware is good for the planet
I'll give you an update as soon as I find some clues about the disk problem

@wezke Great news !

Also, If you'd like to share the packer configuration for windows, I'm interested! I'm curious to see the difference between Linux and Windows boot config

@wezke I see no obvious line to explain why you have an issue with the disk size. The only difference between my build and yours is that you are using the windows 386 version of the builder, and I'm running on Debian.
Can you try the amd64 version ?

@TheNorthernLight @pctechsolution
I'll have some time the next day to work on this.
So basically the things to check:

• Why CPU/RAM/DISK is not correctly displayed
• Have a way to plug a second disk and have it seen by OME
• Have a way to install tools

Do you know if the second disk has something special in it, or I can just add a disk via XOA and call it a day ?

(BTW, if you have support from Dell, you can push them to be compatible with XCP-ng/Xen. I'll be happy to discuss with them to make the appliance work natively )

@AtaxyaNetwork I just tested a build with your configuration, i have 20Gb on my disk

@wezke Do you still have the trace when packer is running ? Maybe i can found what's wrong.
(I'll try to test on my side today, but I can promise anything)