VMware vSphere

 View Only
  • 1.  "vCenter Converter Standalone" - Feature Requests v22 (25H2) Machines w/ NVMe and OS Detection with Hyper-V Source

    Posted 26 days ago

    Is this product (free utility?) under active development?

    • When I convert Hyper-V VMs (from Svr2025 Hyper-V), OS Identification doesn't seem to function.  The resulting .vmx has OS type as "Other"
    • When I convert Hyper-V VMs (from Svr2025 Hyper-V platform), the resulting disks are "IDE".

    However, they need to be NVMe , and OS must be "Windows Server 2xxx" otherwise UEFI boot fails, so I end up using VMWare Workstation 25H2 to convert to a vSphere 8.x compatible machine.

    VMX Changes:

    Start With:

    guestOS = "other"
    virtualHW.version = "21"

    ide0:0.present = "TRUE"
    ide0:0.fileName = "SQL-GOLDEN.usineDor.vmdk"

    Instead we want it to produce a VMX with:

    guestos = "windows2022srvNext-64" # Or similar

    virtualHW.version = "22"

    nvme0:0.present = "TRUE"

    nvme0:0.deviceType = "disk"

    nvme0:0.fileName = "SQL-GOLDEN.usineDor.vmdk"

    It looks like in the GUI someone was planning to add the ability to designate the destination HBA/Controller/Disk format, but it's no implemented.

    Until then, we can do this PowerShell / sed/awk shell scripting, but the .vmdks still need to be format converted to newer standard I guess too (Haven't researched this)

    Thanks.

    ~Brian



    -------------------------------------------


  • 2.  RE: "vCenter Converter Standalone" - Feature Requests v22 (25H2) Machines w/ NVMe and OS Detection with Hyper-V Source

    Posted 25 days ago

    To add to list:

    • I also notice that creates the Virtual NICs as "vlance" (10 mbps) instead of vmxnet3.

     ( I assume that this is because the assumption is that the Hyper-V Guests OSs feature absolute minimum driver support, themselves relying on IDE/ATAPI,  non-Paravirtualized hardware?)

    -------------------------------------------



  • 3.  RE: "vCenter Converter Standalone" - Feature Requests v22 (25H2) Machines w/ NVMe and OS Detection with Hyper-V Source

    Posted 24 days ago

    Piling On:

       It seems to create the VMDKs in an older format that are prompted to convert to a new format (Not sure if this corresponds the Machine Version associated with 25H2 or not (virtualHW.version = "22"))

    To conclude:

    • VMDK Disk Format
    • Network: VLANCE => VMXNET3
    • Make Guest OS Detection Function
    • IDE => NVMe (Optional to force, or accompanying OS Detection)
    • Machine Version v22 Compatible 
    -------------------------------------------