Page MenuHomeSolus

Virtual machines don't recognize Solus
Closed, InvalidPublic

Description

This isn't a bug, but fixing it would make Solus more MIS-friendly. VirtualBox and probably other VM apps (VMWare, Xen, HyperV, etc.) don't know about Solus, so we need to install it as generic Linux. This means various optimizations (not just via guest tools, but in the hypervisor itself) are unavailable.

Event Timeline

To clarify, this can only be fixed by contacting the particular virtualization project in question.

utybo added a subscriber: utybo.Oct 20 2016, 10:57 AM

There are actually loads of linux distributions not supported, but I think it is possible to install guest tools on Solus. Absolutely not sure, someone needs to check this.

NeoVsk added a subscriber: NeoVsk.Oct 20 2016, 11:31 AM

I just installed VirtualBox guest tools without any problems. You just need to install developer tools (sudo eopkg install -c system.devel) and kernel headers in virtual machine to compile kernel modules.

It's good that you can actually install guest tools, but who knows how Solus-aware they actually are, and therefore how well they're actually optimizing. The point is that, ideally, you would just choose "Solus" from the dropdown during VM creation. Recompiling the hypervisor should not be required. This should be easy. It's not Solus' fault that it's not, but someone would need to reach out to the various VM players in order to address this.

DataDrake triaged this task as Normal priority.Dec 25 2016, 1:34 AM
ikey closed this task as Invalid.Feb 5 2017, 2:28 AM
ikey added a subscriber: ikey.

No VM tools optimze anything. You can specify "Linux 64-bit" and this is sufficient. I see no bug here.