twoj

I can report that the issue of the the flat vmdk file not being able to edit any fields has being fixed in ESXi 7.0U3l, Client version: 2.9.2, so to be able to properly import the flat vmdk and attach it you need to update to the latest update as of today (20230413). dj_nsk - i was having the issue that the drive format would fail at 8% - it was necessary to follow the information here; https://github.com/fbelavenuto/arpl/issues/604 hope that helps

First Post here; I ran into this exact issue - very frustrating when it happens. After some tests i can confirm that this issue is not with the ARPL vmdk files, arpl.vmdk & arpl-flat.vmdk, but the issue is a bug with the new ESXi Host Client version 2 that was introduced in ESXi v8 and v7 ESXi-7.0U3i (ESXi 7.0 Update 3i). The new web client interface which is the default way to manage a stand-alone ESXi hypervisor. This bug I don't believe is effecting the vCenter Web GUI, however if you have the free version of ESXi embedded hypervisor or you don't have a vCenter server then you would only have access to the ESXi Host Client to manage the hypervisor. I am running v7 of ESXi and as of today the last update is ESXi-7.0U3k and the bug still has not been resolved. You can see some information as well as some solutions here; https://williamlam.com/2022/12/heads-up-esxi-8-0-host-client-unable-to-attach-existing-virtual-disk-to-vm.html The person who wrote the article says that VMware is aware of the issue however the fix is still not in the last update for v7 in Feb 21 2023 ( Build 21313628 ) As for solutions, I am not a big fan of going in to downgrade the web gui vib back to the original v1 ESXi Host Client, the 2nd choice is to get the VMware PowerCLI powershell module installed and manipulate it with that. For me, i have VMware Workstation so i'm going to try to manipulate loading the file by going through Workstation. I hope this will help some people - there should probably be an alert put in the flat file that there is this issue with ESXi 7.0U3i and 8.x so that people aren't concluding that the problem is with the ARPL files. thanks