On the other hand our virtual server library receives notifications from VirtualBox i.e. handling mouse/keyboard input) and passes them into VirtualBox’s VRDE. Our library just hooks the various callbacks that the FreeRDP API provides (i.e. We don’t have to worry about connection management, packet The great thing here is that thanks to FreeRDP, all the protocol related work has already been done for us. It provides a full featured RDP server, including clipboard and sound redirection, user management as well as RemoteFX and H.264 Remote desktop extension (VRDE) API and FreeRDP. One of the tasks of this library is to serve as a bridge between VirtualBox’s Our RDP server resides in a separate, platform independent library that we call “virtual server”. Together with our own powerful 3D graphics virtualization inside the guest we provide a smooth and rich user experience, no matter from where you are accessing your virtual machines.īut now let’s take a closer look at where and how FreeRDP comes into play in our product. We use FreeRDP’s server implementation to replace VirtualBox’s VRDP extension which is only available with the Oracle VM VirtualBox Extension Pack. In April 2018, Thincast released the first public Beta of Thincast Workstation, a new workstation hypervisor based on Oracle’s VirtualBox. Thincast Workstation - Virtual Desktop Streaming built around FreeRDP When launching weston with the gl-renderer you should get the same desktop in your remote host.Posted by Martin Fleisz on February 20, 2019 Launch an rdp client : on X e.g xfreerdp : When the compositor is up : do the ctrl alt s to fork the new compositor with rdp-backend that will share the screen through RDP Weston -tty=2 -backend=fbdev-backend.so -modules=screen-share.so -use-gl=1ģ/ In order to do remote desktop with the screen-sharing a keyboard and a mouse should be connected to target: The rdp-compositor has a dependency to freerdp.ġ/ Install the freerdp package on target : Make sure you have the TLS certificate/key couple server.crt and server.key (generally : at /etc/freerdp/keys)Ģ/ the command to fork a compositor with the rdp backend should be written in the weston.iniĪt $HOME/.config/weston.ini add the following:Ĭommand=/usr/bin/weston -backend=rdp-backend.so -shell=fullscreen-shell.so -no-clients-resize -rdp-tls-cert=/etc/freerdp/keys/server.crt -rdp-tls-key=/etc/freerdp/keys/server.keyĢ/ launch weston with the following command : Weston -imx should be built with rdp-compositor and screen sharing enabled :Īdd -enable-screen-sharing and -enable-rdp-compositor to the weston configs Here is how they did it on im圆 for your reference. At least I know there are customers used this features on im圆q The screen share should be supported on imx platform with wayland backend. Screen share failed: No wl_shm found <- Error message! What is this reason? launching '/usr/libexec/weston-desktop-shell' Registered plugin API 'weston_xwayland_surface_v1' of size 16 Registered plugin API 'weston_xwayland_v1' of size 32 Loading module '/usr/lib/libweston-9/xwayland.so' info: add 1 socket(s) provided by systemd Loading module '/usr/lib/weston/systemd-notify.so' Loading module '/usr/lib/weston/screen-share.so' However we got the error message as below. This is short cut key of Weston to share screen. Modules=screen-share.so <- Add this line. Sources\meta-imx\meta-bsp\recipes-graphics\wayland\weston_9.0.0.imx.bbappend So, we add as below to build rdp-backend.so. We are testing i.MX8 with below environment.Įvaluation Kit : 8MMINILPD4-EVK (Connect HDMI cable, USB keyboard and USB mouse.)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |