@florent so it's like https://github.com/vatesfr/xen-orchestra/commit/a459015ca91c159123bb682f16237b4371a312a6 might introduced a regression? 0 fbeauchamp committed to vatesfr/xen-orchestra Fix(replication): VDI_NOT_MANAGED error (#8935) from ticket #40151

@tmk said in Cloudbase-init on Windows: @jkatz I ran into the same issue when trying to configure a network adapter with cloudbase-init. The documentation says that the MAC address value is optional but in reality it is required. In my case I want Xen Orchestra to choose a unique MAC during deployment, and I since I am deploying from a template, the NIC name is a known value. The fix that ended up working for me was to modify the networkconfig.py file in cloudbase-init so that the NIC name is required and the MAC address is optional. I ended up making some additional changes to allow for the network-config v2 format along with the existing v1 support and some additional logic to aid in setting the dns search domains (I can't recall if this was originally supported or not but I had issues getting it to work with the original networkconfig.py file) This file needs to replace the existing one that is installed in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Lib\site-packages\cloudbaseinit\plugins\common\ directory. To replace it you should make sure that the cloudbase-init service is stopped, then replace the file. Once this file is replaced, delete the pycache folder in the same parent folder as networkconfig.py - this will ensure that python recompiles this file on service start. Start the cloudbase-init service and confirm that you see a new pycache get created. I'm not a python programmer by trade so others may be able to point out areas for improvement but this ended up working for me and I wanted to share in case it could help others needing to deploy new servers without manually specifying a new MAC address. Below is an example network-config v2 format that works with the updated file. version: 2 ethernets: Ethernet 2: dhcp4: false addresses: - 10.20.30.10/24 nameservers: addresses: - 10.20.5.12 - 10.20.5.13 - 10.20.5.14 search: - intranet.domain.org - domain.org - public-domain.org routes: - to: default via: 10.20.30.1 Updated networkconfig.py file: networkconfig.py.txt Thank you for posting! I followed your directions verbatim and I'm still having trouble getting the network config to take. Does it work with Windows Server 2025?

@TheMonkeyBrain Hi ! Let me find the link I had or reupload the file. I'll give it to you via DM ASAP If you need to uplaod the appliance, you need to replace sda to xvda on this two files: /opt/dell/omc/utilities/tui/bin/ome_disk_config.sh /opt/dell/mcsi/appliance/scripts/appliance_ressource.sh

Hi, Do you have any error message? What's happening? Anything visible or not?

@idar21 said in Xen Orchestra 5.110 V2V not working: I certainly didn't mean to dismiss the significant work that's already been done. At the same time, I think it's important for us all to be open to constructive criticism. Sometimes, even with the most thorough testing, unique configurations slip through the cracks, and that's nobody's fault—it's just the nature of complex IT systems. That was exactly my own point. And this forum is filled with posts of us solving bugs from people's feedback, all along from the last 10 years at least. So we do appreciate a LOT any constructive feedback: we want to fix what's broken, even for free! I was talking about this sentence: I don't think the tool has been tested properly. Which doesn't sound very constructive in my opinion. That was my point, nothing more. Constructive feedback: yes. Non-constructive feedback: no. So let's move over, to be able to assist, we need to know your XOA version (or XO commit), exact ESXi version, the kind of storage you use. That is the base of constructive feedback

@PaulDCL [image: 1757633451167-9eb17eb5-9a99-4743-9df5-51edcc2b1847-image.png] This benchmark was taken inside the Windows Server VM on that iSCSI device. The iSCSI host is a QNAP NAS with Toshiba 18 TB drives configured in RAID-6. I think this is a decent speed for non-flash storage. Both devices are on a 10Gbit network. If you need more specific details, I'll be happy to help.

@DustinB Yeah I thought about doing something like this, but then we are getting into overkill costs lol. My main point behind this post was to get info on what other people are doing, I presumed most are just relying on config backups and will restore it at the other site if needed, which is fine. I was just also debating about whether or not I wanted the subnets to match between these 2 sites, since that can create some routing headaches, but should still be doable and would make recovery even faster. @olivierlambert yeah I do use that feature, so that's very helpful! Should make this all doable.

Yes! That's a good guide for what you want to achieve

@yann said in New Rust Xen guest tools: @john.c OK, that will be useful when the repo is signed, but for now I don't see what adverse effect it can have. Do I miss something? Also we try to avoid breaking support for older OS versions, so we'll likely continue to advertise the old format for older versions of Debian. @yann From Debian 13.0.0 (code name Trixie) having repository signing is mandatory. Without it apt will straight refuse to install, update or upgrade its packages. Also doing with deb822 format will help to protect the GPG Key, used by Vates from abuse by another repository. Especially if that repository is hosting malware laden deb packages. As only the Vates repository can then use that signing key, as defined in the sources file. Refusing to install, update or upgrade is an adverse effect wouldn’t you say?

@AtaxyaNetwork said in Unbootable VHD backups: @Schmidty86 Try to detach the disk and reattach, it should be xvda in order to be bootable That's what I was thinking as well, but obviously something is off with this VM. @Schmidty86 is the old host still online? If so you might be able to perform a Live Migration or a replication job to copy it from the old host to the new.

I had this tab still open which lets me realize that despite we packaged vmfs6-tools and updated the documentation at https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/#local-migration-same-host, we didn't inform you here. Now it's done

@lsouai-vates we should try to reproduce and if we can, to fix it ASAP. Thanks!

AlmaLinux 8.10

That's nice! It means it scales relatively well with many threads, it's a good result

Hi, There is an issue and/or a PR (I don't remember where though) to have a specific extra file to manage user config without overwriting it. Until then, it will be overwritten after updates. @Team-XAPI-Network could provide the link to the issue (or PR?) and check to make it merged when possible

@mdavico said in Debian 9 virtual machine does not start in xcp-ng 8.3: Update: If I change the vCPU configuration to 1 socket with 4 cores per socket the VM starts correctly Interesring. First time I heard it had any effect at all on a VM.

@Danp Hi, I'll try this. Thank you very much. Best regards Mattmurdock78