Solved How to redirect/retarget Hyper-V machines


I have confirmed with QNAP support that due to my model of NAS having an ARM processor I cannot even use their own brand of virtualization station to run Windows VMs. No big deal though. I'll figure something out or just accept the limitations on my physical equipment. Thank you to everyone for your input. Marking this resolved/closed.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro v. 23H2
    Computer type
    Laptop
    Manufacturer/Model
    MSI Katana GF66 11UE
    CPU
    Intel Core i7
    Memory
    32GB
  • Operating System
    Windows 11 Pro 23H2 Version 10.0.22631 Build 22631
    Computer type
    PC/Desktop
    Manufacturer/Model
    DIY Self Built
    CPU
    Intel 13th Gen Core i9 13900K
    Motherboard
    MSI MPG Edge Z790 DDR4 Wi-Fi
    Memory
    3GB
    Graphics card(s)
    ZOTAC Gaming GEForce RTX 3080 Trinity White
    Sound Card
    NONE
    Hard Drives
    2x Samsung 980 Pro SSD 2TB M.2 NVMe
    PSU
    Phanteks 1000w
    Case
    Mars Gaming Pink
    Cooling
    Corsair Hydro-x system, pump/res, CPU block & radiator w/their brand coolant liquid
    Other Info
    Build completed. Currently using it
No, I was more responding to Jimbo's (seeming) suggestion to run the VMs directly on the NAS device itself. Some NAS devices can do that, but yours cannot. I'm not even really sure that's what Jimbo was suggesting; just saying it's not an option.

@WonderWoman

If an ARM processor device can share DATA with Windows --then there's no reason why you can't set up the VM's Virtual files to exist on the ARM machine but run the VMWare WKS program from Windows. The VM files are just "Data" for VMWare wks.

So you just need some way of copying / moving the VMWare files from one device to the other. If you do that though on VM ist reboot specify I Moved it rather then I copied it --otherwise the GUUID of the Guest will change and you'll probably lose Windows Activation.

I hope that's clearer now -- any NAS should be able to have DATA stored on it !!!!!!-- I accept the fact that some can't run the actual VM program itself but any other computer capable of running the application should so long as the remote data files are accessible.


Cheers
jimbo
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7
It is Hyper-V not VM ware. And QNAP has stated that ARM processors and Hyper-V VMs with Windows (any version) are not compatible.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro v. 23H2
    Computer type
    Laptop
    Manufacturer/Model
    MSI Katana GF66 11UE
    CPU
    Intel Core i7
    Memory
    32GB
  • Operating System
    Windows 11 Pro 23H2 Version 10.0.22631 Build 22631
    Computer type
    PC/Desktop
    Manufacturer/Model
    DIY Self Built
    CPU
    Intel 13th Gen Core i9 13900K
    Motherboard
    MSI MPG Edge Z790 DDR4 Wi-Fi
    Memory
    3GB
    Graphics card(s)
    ZOTAC Gaming GEForce RTX 3080 Trinity White
    Sound Card
    NONE
    Hard Drives
    2x Samsung 980 Pro SSD 2TB M.2 NVMe
    PSU
    Phanteks 1000w
    Case
    Mars Gaming Pink
    Cooling
    Corsair Hydro-x system, pump/res, CPU block & radiator w/their brand coolant liquid
    Other Info
    Build completed. Currently using it
QNAP has stated that ARM processors and Hyper-V VMs with Windows (any version) are not compatible.
That is at odds with Microsoft's advice. Of course, on an ARM host you'd need to have an ARM guest....

Microsoft said:

Can I host a Windows 11 virtual machine using Hyper-V on a Windows 11 Arm64 device?​

Yes, you can. The easiest way to do so is to download the Windows 11 on Arm Insider Preview VHDX from Windows Insider Preview Downloads and use it to create a VM.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Lattitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
That is at odds with Microsoft's advice. Of course, on an ARM host you'd need to have an ARM guest....
That’s exactly the reason it’s not compatible. There are specific versions available for hyper visor to be able to run on ARM processors but they are impossible to find because they are mostly dedicated to people who are either developing or testing Windows software on Apple devices.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro v. 23H2
    Computer type
    Laptop
    Manufacturer/Model
    MSI Katana GF66 11UE
    CPU
    Intel Core i7
    Memory
    32GB
  • Operating System
    Windows 11 Pro 23H2 Version 10.0.22631 Build 22631
    Computer type
    PC/Desktop
    Manufacturer/Model
    DIY Self Built
    CPU
    Intel 13th Gen Core i9 13900K
    Motherboard
    MSI MPG Edge Z790 DDR4 Wi-Fi
    Memory
    3GB
    Graphics card(s)
    ZOTAC Gaming GEForce RTX 3080 Trinity White
    Sound Card
    NONE
    Hard Drives
    2x Samsung 980 Pro SSD 2TB M.2 NVMe
    PSU
    Phanteks 1000w
    Case
    Mars Gaming Pink
    Cooling
    Corsair Hydro-x system, pump/res, CPU block & radiator w/their brand coolant liquid
    Other Info
    Build completed. Currently using it

Latest Support Threads

Back
Top Bottom