| 2016-12-05 16:24:35 |
Andreas Pokorny |
bug |
|
|
added bug |
| 2016-12-05 16:24:45 |
Andreas Pokorny |
tags |
|
vm |
|
| 2016-12-05 16:28:50 |
Andreas Pokorny |
description |
Steps to reproduce:
* install vmware workstation player
* setup an ubuntu image with the zesty iso image for amd64
* apt install mir-demos
* run sudo miral-shell --arw-file --vt 2 -f /tmp/mir_socket
* mir_demo_client_eglplasma -m /tmp/mir_socket
The client application exits and in the terminal output you should see:
VMWare: No 3D enabled (0, Success).
That message is from the mesa vmware driver:
https://github.com/mesa3d/mesa/blob/master/src/gallium/winsys/svga/drm/vmw_screen_ioctl.c#L880
The ioctl seems to complete successfully but yields the wrong result |
Steps to reproduce:
* install vmware workstation player
* setup an ubuntu image with the zesty iso image for amd64
* apt install mir-demos
* run sudo miral-shell --arw-file --vt 2 -f /tmp/mir_socket
* mir_demo_client_eglplasma -m /tmp/mir_socket
The client application exits and in the terminal output you should see:
VMWare: No 3D enabled (0, Success).
That message is from the mesa vmware driver:
https://github.com/mesa3d/mesa/blob/master/src/gallium/winsys/svga/drm/vmw_screen_ioctl.c#L880
The ioctl seems to complete successfully but yields the wrong result.
The same can be experienced with miral-shell running in X11.
GL clients within X11 work. EGL on DRM seems to work - since mir_proving_server on DRM works too. |
|
| 2016-12-05 21:38:17 |
Andreas Pokorny |
description |
Steps to reproduce:
* install vmware workstation player
* setup an ubuntu image with the zesty iso image for amd64
* apt install mir-demos
* run sudo miral-shell --arw-file --vt 2 -f /tmp/mir_socket
* mir_demo_client_eglplasma -m /tmp/mir_socket
The client application exits and in the terminal output you should see:
VMWare: No 3D enabled (0, Success).
That message is from the mesa vmware driver:
https://github.com/mesa3d/mesa/blob/master/src/gallium/winsys/svga/drm/vmw_screen_ioctl.c#L880
The ioctl seems to complete successfully but yields the wrong result.
The same can be experienced with miral-shell running in X11.
GL clients within X11 work. EGL on DRM seems to work - since mir_proving_server on DRM works too. |
Steps to reproduce:
* install vmware workstation player
* setup an ubuntu image with the zesty iso image for amd64
* apt install mir-demos
* run sudo miral-shell --arw-file --vt 2 -f /tmp/mir_socket
* mir_demo_client_eglplasma -m /tmp/mir_socket
The client application exits and in the terminal output you should see:
VMWare: No 3D enabled (0, Success).
That message is from the mesa vmware driver:
https://github.com/mesa3d/mesa/blob/master/src/gallium/winsys/svga/drm/vmw_screen_ioctl.c#L880
The ioctl seems to complete successfully but yields the wrong result.
The same can be experienced with miral-shell running in X11.
GL clients within X11 work. EGL on DRM seems to work - since mir_proving_server on DRM works too.
Update: The problem seems to be related to dmabuf fds. The error message mentioned above does not seem to stop the egl initialization. So later in the process when mirclient receives the buffers the driver fails to import the dmabuf fds. So maybe the interrupted initialization leaves the egl structures in a state incapable to perform the dmabuf fd to drm handle mapping. |
|
| 2016-12-06 01:48:47 |
Daniel van Vugt |
mir: status |
New |
Confirmed |
|
| 2016-12-06 01:50:05 |
Daniel van Vugt |
summary |
vmwares mesa driver fails on mir platform during init |
GL clients never show up in VMware [VMWare: No 3D enabled (0, Success).] |
|
| 2017-11-03 16:42:16 |
Michał Sawicz |
mir (Ubuntu): status |
New |
Confirmed |
|
