Hyper-V Support?

  • Hi, I would like Hyper-V support in order to easily test builds, specifically Plex Media Player embedded builds.
    Why Hyper-V, because it comes included in Windows 10, free of charge in Pro editions, no need to install any 3rd party VM software.


    It seems like the Hyper-V networking and video drivers are not included in the build.


    I created a blank boot 1GB VHDX disk.
    I wrote the install image to the mounted VHDX disk using Active Data studio, WinImage works but gives an error.
    I created a type 1 VM, and added the boot VHDX as the boot drive.
    Boot the VM, install on second VHDX, remove the boot VHDX from config, reboot.
    System boots, no video driver detected, and waits for networking, that never starts.


    If Hyper-V support will not be added to the native image, is there a way I can add it myself?


    Thanks

  • Thx, can you please point me to the build scripts?


    I'd also like you to consider Hyper-V as a first class citizen, it is part of Win10, and Linux it is actively supported by Microsoft.

  • If you do the changes we promise Hyper-V will be neglected equally to vmware and vbox. Virtual is an internal testing tool not a "supported" project for broad public consumption. We have no objections to a few people using it as long as the support status is clearly understood. Some in the wider community would like Virtual to be taken seriously and supported, but as none of them want to step forward and act as its maintainer it's current status is unlikely to change anytime soon.

  • Understood, and that is fair.


    Can you still please point me to the scripts?


    One last thought;
    I see an overlap between users with unsupported hardware drivers, and some of those drivers being for VM environments.
    What about a driver injection tool, similar to how image servicing works in Windows, where standard tools exists to inject drivers into boot / WIM images.
    Such a tool, friendly enough for advanced end users, no Linux required, may be generally useful (vs. a user needing to be sufficiently skilled to build their own distribution)?


  • Understood, and that is fair.


    Can you still please point me to the scripts?


    GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI




    One last thought;
    I see an overlap between users with unsupported hardware drivers, and some of those drivers being for VM environments.
    What about a driver injection tool, similar to how image servicing works in Windows, where standard tools exists to inject drivers into boot / WIM images.
    Such a tool, friendly enough for advanced end users, no Linux required, may be generally useful (vs. a user needing to be sufficiently skilled to build their own distribution)?


    no, we are a small embedded distribution with a read only squashfs filesystem.

  • Would also like to see hyperv as it is included with windows 10. Drivers are available in the mainline kernel... so just add the hyperv-daemons package and we are done.

  • For official dev purposes vmware does what we need, and we don't formally support it. If the community wants Hyper-V support, the community needs to band together and create/maintain a community release that provides it. If we see strong demand we can always later adopt the changes, but from experience virtual things are very niche. In its heydey the 'Virtual' image saw a maximum of 38 users. That would currently be 0.0001% of our userbase.

  • Arch Linux - hyperv 4.14-1 (x86_64) doesn't looks too easy/trivial


    Also Hyper-V would be nice to have as it is shipped with Windows so you have no need for an VMWare licence for proper usage (as the free VMWare Player is rather limited).

    But like chewitt said, we stop nobody to pr a working solution, our time is also limited and the possible gain here is rather small.

  • It is a bit difficult to repro and test bugs in production systems... I cannot create such a PR myself because of lack of knowledge.