@MajorP93 here are some screenshots of my XOA RAM [image: 1770137975094-648fbf59-9143-4517-892c-6ba9a5fdb5e1-cc6a2183-cef2-4139-8792-5e5bf5457be3.png] (lost before sunday stats since I crashed my host in RPU this weekend...) [image: 1770138023972-ecb141c6-fce7-4571-9f3c-9b138ca9c35c-3a43a1db-c18b-4787-8791-95fb4e0c6531.png] you can clearly see RAM crawling and beeing dumped each reboot. here is one of my XOA Proxies (4 in total, they totally offload backups from my main XOA) [image: 1770138140983-490f8a00-67db-4aeb-aa61-6eb3b8c7b570-59efe2ab-72b7-43e6-b89a-bced3ea399f2.png] there is also a slope of RAM crawling up... little spikes are overhead when backups are ongoing. I started to reboot XOA+all 4 proxxies every morning.

@MathieuRA As announced, I have now installed branch xo6/update-site-dashboard and it seems to be working. It no longer loads endlessly and shows me that I haven't configured anything yet Thank you very much!

@busthead said in Windows 11 (Win11_25H2_English_x64.iso) Fails to Install: It appears I missed the key press to start setup Dont you know your are not suppose to blink when doing working. You might miss something Glad you figured it out.

@henri9813 Ahh alright, I understand now! Thanks for clarifying.

@Tristis-Oris There are many features missing since it's alpha now, but you can open bug tracker request on github if you want to keep track of progress for this particular feature.

@dinhngtu I think it just have been a bad migration or the Win 11 Template did other things to the windows 10 os. Since new test vm did not show the time issues, and a fresh migration of the vim with correct template selected did not have the issues either. I dont know but maybe there is a way to put detect the correct VM template or make note. I didnt think using the win 11 template would have caused issues since using the "wrong" template on vm creation does not have the same effect.

Keep us posted, happy to hear from it!

To elaborate: it was already in progress, but delayed due to 1. the fact that I underestimated the impact (I thought we'd overwrite the file only when we'd modify it, not every update the package) and 2. lots of other priorities keeping the team busy. But it's clearly the reminder, and the help in better diagnosing it, that allowed to have it re-prioritized and (partly, we've mostly bought time to fix it properly, by simply avoiding to touch the file at all at the moment) fixed so fast.

Ouch. @andyhhp in case that trace rings a bell.

@dave.opc that's it keep us updated on this

@florent said in vmware vm migration: @acebmxer yes after the first migration, XO knwo that the migration is incomplete and that you may want to finish it later. But if you start this VM direvtly , it will write some data, thus it won't be in sync anymore with the Vmware snapshot. Then XO won't be able to resume You can start a copy of the VM ( XO will handle it for you ) and delete the copy when you're done My advice is to migrate this VM to the right SR and then do the resume. But keep in mind that the V2V tool is intended to target only one SR, so migrate all they disk to the same SR, and select the right one when resuming the V2V. You can change the network after My previous migration was successful with no issues. Previously test vm was fresh install so no vmtools installed. But I did shut the vm down myself prior to starting the migration. VM boots no issues no prompts. This time I decided to follow the steps listed in the documentation as i have been following the changes and updates for the v2v migration. Following the steps as mention XO presented me with that prompt which was not mention in the documentation. As i was typing the post to gather my information it was then i noticed i did not select the proper destination SR and the appropriate nic/vlan for networking. So I noted that in the post. With the assumption i could correct that on the final migration. With that said the I guess the documentation should state - Start vm to test if boots, etc.. When prompted choose "Start a copy". When done shutdown vm and remove.

One more question! How can I add the contents of that field to the output? This curl -k -b authenticationToken=$tk "https://xoa.pc.scharp.org/rest/v0/vms?filter=other:XenCenter.CustomFields.export_vga:"*"&fields=name_label,other:XenCenter.CustomFields.export_vga" doesn't work. I did double check that multiple fields are comma delimited, I can set fields to fields=name_label,power_state I'm assuming this is something weird about properly quoting and escaping different parts of the call. For example, thee above example is actually passing three chunks because of that quoted * within the quotes. But if I try to make it make more sense it stops working at all. OK, this works: curl -k -b authenticationToken=$tk "https://xoa.pc.scharp.org/rest/v0/vms?filter=other:XenCenter.CustomFields.export_vga:*&fields=name_label,other:XenCenter.CustomFields.export_vga,power_state" and returns the name and power state but not the custom field OK, I didn't expect different results but I get the same behavior in python using the requests module.

Hi! ISO-SR over HBA/FC would be very nice, especially when migration form a SAN vmware-System to XCP-NG. One other thing is altering. Errors like "VM cannot be migrated" or similar should not be silent but should be very visible / even mailed to the admin. Another thing (could be cosmetical though) in my opinion is that a failed Rolling upgrade remains visible with a half fulled progress bar in the task-view. this is confusing.

@Danp will try it ASAP. Thanks for the hint!

@olivierlambert so strange though. i have it enabled on 4 pools, that didn't propagte on hosts. still VM boots up when not needed as explained on fist post of the thread. i'll try différent combinations to see what's really going on

@bleader Hopefully the palm print on my forehead isn't visible from where you are sitting. Of course the interface needs an IP address. In my defense, normally for something like this, I wouldn't put it on the bonded interface with all the trunked VLAN's for guest traffic (we don't give that one an IP) and it would go on the other bonded interface that isn't trunked and does get an IP, but these are test hosts and I didn't set up the other bond, so it is pulling double duty. I was able to set the IP's and get SDN working. Thanks!

@Danp thank you for the help. I have looked at all vhd in my disk and they are all good as per vhd-tool check. Regarding the logs in xensource logs the first error is showing up few mins after I trigger the export. #!/bin/bash # Script to check all VHD files in the current directory using vhd-tool set +e # Don't exit on error total=0 failed=0 echo "Checking VHD files..." echo "" # Loop through all .vhd files in current directory for vhd_file in *.vhd; do # Skip if no .vhd files found [ -e "$vhd_file" ] || continue ((total++)) # Run vhd-tool check if vhd-tool check "$vhd_file" > /dev/null 2>&1; then echo "PASS: $vhd_file" else echo "FAIL: $vhd_file" ((failed++)) fi done # Report echo "" echo "====================" echo "Total: $total" echo "Failed: $failed" echo "====================" [ $failed -eq 0 ] && exit 0 || exit 1 /checkvhd.sh Checking VHD files... PASS: 014e122e-7908-4566-be52-31fc40ea6042.vhd PASS: 054f3177-e40b-4c87-86c6-88ac9db3edfe.vhd PASS: 154c4dd3-651d-404b-8df0-e85a07aa5bf6.vhd PASS: 16f68c2a-74d7-4698-8276-56bdc686e161.vhd PASS: 18b4a57f-3c77-42da-973c-d136375878da.vhd PASS: 1a129b44-a562-4555-8785-2bfaa1f98455.vhd PASS: 1e62a336-bb27-40f0-8da5-1f53cbeeee83.vhd PASS: 24b6ede5-b698-4a9d-acb1-a4898d78cf8c.vhd PASS: 24b82a29-9fe2-47af-a68b-f36a73b34624.vhd PASS: 2d8b1375-4fc8-46eb-b1f6-2d887e37602c.vhd PASS: 2e3897fb-7d45-4098-9956-d985636d9a12.vhd PASS: 3165bf7b-ca6f-4a30-b33d-bda31e2c67ab.vhd PASS: 31832728-0001-407d-85f6-0de340e2dbda.vhd PASS: 32f501b3-47df-4730-824b-f9e297e9d12c.vhd PASS: 346c5bf0-6635-4f1b-af32-fc9f8fac5088.vhd PASS: 3a7f68ce-b342-4d03-878f-956e74074b6a.vhd PASS: 406f2750-fea7-4389-920f-0b080335284f.vhd PASS: 4156d2ea-d39d-436d-b89f-06ad64949c53.vhd PASS: 475b16f8-f1c0-40b6-b181-99f83f14dd73.vhd PASS: 52656fa5-d418-45e0-9e65-07a450af2476.vhd PASS: 69042c99-b0a3-47ab-8c2b-48303c4cc6bc.vhd PASS: 6a79914e-67e0-4ac9-b93e-2e393aaa7b97.vhd PASS: 6b0919bb-7d0a-4036-a833-0313476a11a3.vhd PASS: 7e2fc00c-7208-4132-aa4a-7db818c7a94b.vhd PASS: 824af8d0-112b-479b-b474-6e5a26e0d8b2.vhd PASS: 8f6d6a7c-5390-43bd-b0b5-55f8e681453a.vhd PASS: 94453b92-3a69-416b-9c08-9f0b91b2aee1.vhd PASS: 947ad175-06a7-4881-8725-aba36d2cda66.vhd PASS: 97e577dc-b0be-4990-8e06-c0c4333aef82.vhd PASS: 9889a738-cfd4-447d-962a-8fd88222d8ab.vhd PASS: 9c93fa78-4b17-41b1-b794-8bfa165ed4b4.vhd PASS: a3408bda-9c26-4333-b535-3a008109b98c.vhd PASS: a3c69ec6-f56e-4d25-ba71-023a38eef8e3.vhd PASS: a8c45c4c-8925-41a3-a78d-c30d6e20c261.vhd PASS: b119ad26-f0dc-4965-b726-9dc3fc815130.vhd PASS: b12002da-56b6-451c-ad4d-a6c16a79fc12.vhd PASS: b24f9236-6b68-4214-812d-9e98994467aa.vhd PASS: b34f20b8-6681-42e9-b234-116989286699.vhd PASS: b5ff8f04-0ace-4b23-9f0b-7a6c5328bef5.vhd PASS: b932bc63-a47d-49cb-9d28-a57ad61e7ad9.vhd PASS: be06df0b-cbb7-4dfe-8eaf-697de4d8850b.vhd PASS: cb88a496-8c80-41e2-b3de-055916a3a32c.vhd PASS: ce66b785-5b1b-43c8-9ece-dc456508014c.vhd PASS: ddb84192-3e35-4541-86da-d4326a6bbea7.vhd PASS: de27f27e-65b8-42d3-929f-f34f0544149a.vhd PASS: e054e9da-08e7-40b1-8c55-0fd2ae97ee5f.vhd PASS: e449742e-5007-4be6-89c0-2529d00dbf28.vhd PASS: f0ee695e-dcb4-49e6-ac17-4a64f65998a6.vhd PASS: f20e6bb0-4cba-4030-87fc-ddbaca262169.vhd PASS: f28a0554-6530-4055-a67e-d970ab1c4cc1.vhd PASS: f5dd3ee4-7006-43fc-8254-98eb45505639.vhd ==================== Total: 51 Failed: 0 ==================== I'll give another export try to see if it works this time. best.

Mentioning also @Team-Hypervisor-Kernel who now manages the drivers. Maybe it's related to https://github.com/xcp-ng-rpms/microsemi-aacraid/issues/2#issuecomment-3837183087 It looks like the switch to the vendor driver instead of the kernel built-in for 8.3 (initiated by XenServer, and that we followed at the time as it was probably made in order to support newer cards) was not without drawbacks. 0nelight created this issue in xcp-ng-rpms/microsemi-aacraid open Microsemi Adaptec Series-8 Card not working in XCP-NG 8.3 #2