RealVNC is not using NVIDIA GPU and driver

• Official comment

  

  Jack N RealVNC

  September 23, 2022 21:05

  Hi Sandip,

  Thanks for your post. Virtual Mode sessions are rendered by the CPU and as such cannot leverage hardware acceleration at this time. If you need hardware acceleration, please try using Service Mode instead:

  sudo systemctl enable vncserver-x11-serviced --now

  and connect on port 5900. Note: you will need a connected monitor in most cases for the OS to render the desktop correctly.

  Thanks,

  Jack N

  Comment actions Permalink
• 

  sandip thorat

  September 24, 2022 10:21

  I'm running virtual machine. Physical display is not connected to vm.  I can start my own X server on GPU. But looks like vnc is not starting X server on GPU. Below is my xorg.conf file. 

  root@nves-virtual-machine:~# cat /etc/X11/xorg.conf
  # nvidia-xconfig: X configuration file generated by nvidia-xconfig
  # nvidia-xconfig:  version 470.103.01

  Section "ServerLayout"
      Identifier     "Default Layout"
      Screen         "Screen0" 0 0
      InputDevice    "Keyboard0" "CoreKeyboard"
      InputDevice    "Mouse0" "CorePointer"
  EndSection

  Section "InputDevice"
      # generated from default
      Identifier     "Keyboard0"
      Driver         "kbd"
  EndSection

  Section "InputDevice"
      # generated from default
      Identifier     "Mouse0"
      Driver         "mouse"
      Option         "Protocol" "auto"
      Option         "Device" "/dev/psaux"
      Option         "Emulate3Buttons" "no"
      Option         "ZAxisMapping" "4 5"
  EndSection

  Section "Monitor"
      Identifier     "Monitor0"
      VendorName     "Unknown"
      ModelName      "Unknown"
      Option         "DPMS"
  EndSection

  Section "Device"
      Identifier     "Device0"
      Driver         "nvidia"
      VendorName     "NVIDIA Corporation"
      BusID          "PCI:2:1:0"
  EndSection

  Section "Screen"
      Identifier     "Screen0"
      Device         "Device0"
      Monitor        "Monitor0"
      DefaultDepth    24
      Option         "AllowEmptyInitialConfiguration" "True"
      SubSection     "Display"
          Depth       24
      EndSubSection
  EndSection

  root@nves-virtual-machine:~#

  0

  Comment actions Permalink
• 

  Jack N RealVNC

  September 26, 2022 12:21

  Hi Sandip,

  You can try copying /etc/X11/xorg.conf to /etc/X11/vncserver-virtual-dummy.conf but this probably won't work, as the Nvidia driver will be expecting to run in the console session.

  As for Service Mode, you may be able to connect anyway depending on how the VM presents GPU/monitors. If you run into any display issues, the first thing to try is adding:

  CaptureMethod=1

  to /root/.vnc/config.d/vncserver-x11

  and then restarting VNC Server

  Thanks,

  Jack

  0

  Comment actions Permalink
• 

  sandip thorat

  September 28, 2022 17:38 (Edited October 04, 2022 14:49)

  Thanks for clue. I was referring this doc - https://help.realvnc.com/hc/en-us/articles/360002253818

  I have copied my custom xorg.conf file to /etc/X11/vncserver-virtual-dummy.conf and started virtual vnc server as sudo/root user using command - "sudo vncserver-virtual" .  VNC started properly on NVIDIA GPU with NVIDIA driver. But VNC session is very sluggish.   

   

  user@sandip-19u:~$ sudo vncserver-virtual
  VNC(R) Server 6.10.1 (r47571) x64 (Jul 21 2022 17:20:14)
  Copyright (C) RealVNC Ltd.
  RealVNC and VNC are trademarks of RealVNC Ltd and are protected by trademark
  registrations and/or pending trademark applications in the European Union,
  United States of America and other jurisdictions.
  Protected by UK patent 2481870; US patent 8760366; EU patent 2652951.
  See https://www.realvnc.com for information on VNC.
  For third party acknowledgements see:
  https://www.realvnc.com/docs/6/foss.html
  OS: Ubuntu 20.04, Linux 5.4.0, amd64
  
  Xorg driver not found: Xorg void input driver
  You've set vncserver-virtual to use the system Xorg server. For more information
  on this alternative implementation, please see:
  https://www.realvnc.com/doclink/kb-546
  
  Running applications in /etc/vnc/xstartup
  
  VNC Server catchphrase: "Oregano smart Neptune. Brush content mambo."
               signature: 43-1b-a2-4d-e1-93-42-43
  
  Log file is /root/.vnc/sandip-19u:1.log
  New desktop is sandip-19u:1 (x.x.x.x:1)
  user@sandip-19u:~$ sudo ps -ef | grep -i vnc
  root       40485       1  0 22:51 ?        00:00:00 vncserver-virtual
  root       40487   40485  1 22:51 tty3     00:00:00 /usr/lib/xorg/Xorg :1 -config vncserver-virtual-dummy.conf -auth /root/.Xauthority -pn
  root       40490   40485  0 22:51 ?        00:00:00 /usr/bin/vncserver-x11-core -virtual -newinstance
  root       40499   40490  0 22:51 ?        00:00:00 /usr/bin/vncagent virtual 0
  root       40501   40485  0 22:51 ?        00:00:00 /usr/bin/dbus-daemon --session --nofork --address=unix:path=/tmp/.vnc-0/run/session-5b5afb84aad14b9c/bus --nopidfile --nosyslog
  root       40505   40485  0 22:51 ?        00:00:00 /bin/sh /etc/vnc/xstartup
  user       41087   29856  0 22:52 pts/1    00:00:00 grep --color=auto -i vnc

   

  Is it correct method ?  Why the xorg file name should be vncserver-virtual-dummy.conf  ?  

  Also I can only use root user for vnc session login.  Normal user not able to access VNC session started by sudo/root user.  How I can give permission to sudo users to access the vnc desktop started with command "sudo vncserver-virtual" ? 

   

   

   

  0

  Comment actions Permalink
• 

  sandip thorat

  November 07, 2022 14:44

  Hi Jack,   

  Is it correct method ?  Why the xorg file name should be vncserver-virtual-dummy.conf  ?  

  Also I can only use root user for vnc session login.  Normal user not able to access VNC session started by sudo/root user.  How I can give permission to sudo users to access the vnc desktop started with command "sudo vncserver-virtual" ? 

       

  0

  Comment actions Permalink

Please sign in to leave a comment.