Solus 4 on Hyper-V

tobcro

One thought: Before the message "Failed to start Load Kernel Modules", there is a couple of messages from vboxsf/vboxguest. Can it be that Solus detects it is running in a VM, assumes it is a VirtualBox VM and tries to start the modules for that (obviously failing)?

eherle

I am experiencing exactly the same problem. Have you been able to solve it? Can you share your solution?

DataDrake

eherle We don't support Hyper-V.

ruskofd

Hyper-V is not good with graphical environment with Linux. Don't expected to have good video performance on this, use VirtualBox or VMware instead.

dyseac

ruskofd
There are fixes. Some easier than others (VNC, Remote Desktop Clients etc..)

DataDrake
What's moot is focusing on features that enable a fringe OS to virtualise / perpetuate within itself (or similar family) Why the #%CK wouldn't you focus on developing support for one of the most rapidly growing VM ecosystems (thanks to win10-pro H-V & M$ Mass marketing dominance). As a windows power user for more than 20 years, I shifted to *nix based OS's for reduced overheads and improved security / reliability (during XP/7 era)- It's becoming less the case these days.... Win 10 has come a long way.... /scared

Seriously - you want < adaption ? Help this man (and many others) with allowing for easy HV deployment.

tothecloudd0
It is Gen2 if you enable the right settings and deploy correctly. Its far from baremetal...

PS: I am really enjoying Solus, but often return to distro's like MX for broader cross-kernal app support (or ports). - I mean, the amount of effort getting simple stuff installed like Skype or even a mapped OneDrive has been frustrating at the best of times. .... I sometimes feel feel the hardcore purists/devs/propellarheads might be somewhat narcissistic. Reminds me of a talented artist who will only paint his bedroom walls....

tothecloudd0

Any particular reason you wan't to use hyper-v compared to a type 2 hypervisors? (vitual box, vmware worstation etc). Another option would be... lol reverse the whole set up. Image the windows OS, install Solus as host and run windows on virtualbox/vmware or hell even docker 😀

Also, this might be a stupid question but is virtualization enabled in BIOS?

DataDrake

tothecloudd0 We don't have the kernel modules for Hyper-V devices enabled, so anything else wrong with the setup is moot.

kyrios

dyseac What's moot is focusing on features that enable a fringe OS to virtualise / perpetuate within itself (or similar family) Why the #%CK wouldn't you focus on developing support for one of the most rapidly growing VM ecosystems (thanks to win10-pro H-V & M$ Mass marketing dominance)

Hyper-V is very niche at the moment, it is also not available on windows 10 home (which is the only edition that targets mass market btw) and Solus is designated for home computing.

Anyway, the intended behavior of Solus is to run on physical hardware, not a virtualized environment.

DataDrake

dyseac What's moot is focusing on features that enable a fringe OS to virtualise / perpetuate within itself (or similar family) Why the #%CK wouldn't you focus on developing support for one of the most rapidly growing VM ecosystems (thanks to win10-pro H-V & M$ Mass marketing dominance). As a windows power user for more than 20 years, I shifted to *nix based OS's for reduced overheads and improved security / reliability (during XP/7 era)- It's becoming less the case these days.... Win 10 has come a long way.... /scared

Citation needed on "most rapidly growing VM ecosystems". We support QEMU/KVM, VirtualBox, and VMWare. Hyper-V is popular in some corporate environments. But you could make the same argument about why we don't support Xen or XenServer. If your only metric is install-base and not actual demand, you've already lost the plot. And even then, I find it really hard to believe that the majority of the demand that Solus has for virtualization support is at all Hyper-V related as that has only come up at all in the past year or so, and fewer than a handful of times. Regardless, we support Virtualization for you to be able to try out Solus before installing. It is not intended for long-term installations. If you can't be bothered to install VirtualBox or VMWare to give it a try, that's not my problem.

dyseac Seriously - you want < adaption ? Help this man (and many others) with allowing for easy HV deployment.

I see zero proof that not supporting Hyper-V is somehow affecting our adoption rate. Hyper-V isn't included unless you have a Pro or higher license of Windows. That already limits the amount of people possibly trying to install that way. Most people have Windows Home and would need to install something like VirtualBox to go make a virtual machine. So now that means there's a technical skill level needed to both know to install a VM solution for Windows and then to actually create and install a VM in that tool, further narrowing the field.

Conversely, I have definite proof by example of hundreds of cases each year of people switching from one Linux distro or another to Solus after installing it in QEMU/KVM or VirtualBox to try things out.

Staudey

dyseac PS: I am really enjoying Solus, but often return to distro's like MX for broader cross-kernal app support (or ports). - I mean, the amount of effort getting simple stuff installed like Skype or even a mapped OneDrive has been frustrating at the best of times. .... I sometimes feel feel the hardcore purists/devs/propellarheads might be somewhat narcissistic

Installing Skype takes four clicks (counting the one to open the Software Center and to confirm the password prompt), you might have a point about OneDrive. A point about it being hard, not the reason for it being hard. I don't see any hardcore purists here, just people trying their hardest to make this distro work, and sometimes simply lacking the time and/or manpower to implement certain features.

DataDrake

Staudey Yeah, it has far more to do with pragmatism than narcissism. My general response to things outside of our main focus is "pull requests welcome", but I'm not polluting the Kernel with modules that hardly ever get used.