Drivers drivers drivers

[Daniel van Vugt]

Yes, bug 1118903 is the catch-all bug for anyone trying to use Mir in an 
unsupported VM, or on bare metal with an unsupported GPU and/or no DRM.

Indeed it seems people hitting bug 1118903 lately are trying to use Mir 
in VirtualBox (even VirtualBox on Windows).

As for KVM and VMware, it seems users of those are getting a bit further 
but also hitting this crash now:
 
https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
    https://bugs.launchpad.net/mir/+bug/1560498

The good news is that we are making some progress on the generic 
solution now though:
    https://bugs.launchpad.net/mir/+bug/1118903


On 07/04/16 16:14, Andreas Pokorny wrote:
> Hi,
>
> On Wed, Apr 6, 2016 at 4:55 AM, Daniel van Vugt
> <daniel.van.vugt at canonical.com <mailto:daniel.van.vugt at canonical.com>>
> wrote:
>
>     Here's an observation: Two out of the top three hottest [1] Mir bugs
>     are Mir failing to start (USC/Unity8) due to insufficient graphics
>     drivers:
>
>     Running in a VM:
>     https://bugs.launchpad.net/mir/+bug/1118903
>
>
> Is this really about running mir or unity8 in a VM? Both kvm and vmware
> support enough of drm/kms to run mir.
> I am not sure how far virtual box is with its drm/kms support. Two years
> ago some parts were missing. Maybe
> virtual box could also use qxl + spice for that purpose? But back to the
> statement, I think there is a bigger problem
> with running ubuntu on systems without shader support and lack of cpu to
> use llvmpipe to compensate that. Those systems
> are likely to have drm support.
>
> regards
> Andreas