Forum

VirtualBox Emulator graph UI launch failed

Hi, I am new guy playing webos, following VirtualBox Emulator User Guide, the boot success, login with ssh success, but graph UI launch failed, what ever pre-built images or self built.
I check some log, found the following

[ 7.780691] uvesafb: Oracle Corporation, Oracle VM VirtualBox VBE Adapter, Oracle VM VirtualBox Version 6.0.8, OEM: VirtualBox VESA BIOS, VBE v2.0
[ 7.833493] uvesafb: protected mode interface info at c000:4400
[ 7.834338] uvesafb: pmi: set display start = 0c5f393f, set palette = 3dcae7a4
[ 7.836004] uvesafb: pmi: ports = 1ce 1cf 1cf 1d0 3b6 3b7
[ 7.837231] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 7.839027] uvesafb: scrolling: ypan using protected mode interface, yres_virtual=2400
[ 7.840854] uvesafb: cannot reserve video memory at 0xf0000000
[ 7.841959] uvesafb: probe of uvesafb.0 failed with error -5
[ 7.780691] uvesafb: Oracle Corporation, Oracle VM VirtualBox VBE Adapter, Oracle VM VirtualBox Version 6.0.8, OEM: VirtualBox VESA BIOS, VBE v2.0
[ 7.833493] uvesafb: protected mode interface info at c000:4400
[ 7.834338] uvesafb: pmi: set display start = 0c5f393f, set palette = 3dcae7a4
[ 7.836004] uvesafb: pmi: ports = 1ce 1cf 1cf 1d0 3b6 3b7
[ 7.837231] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 7.839027] uvesafb: scrolling: ypan using protected mode interface, yres_virtual=2400
[ 7.840854] uvesafb: cannot reserve video memory at 0xf0000000
[ 7.841959] uvesafb: probe of uvesafb.0 failed with error -5

Dec 12 23:27:32 qemux86 systemd[1]: Failed to start webos - "surface-manager-daemon.service".
Dec 12 23:27:32 qemux86 surface-manager[16299]: [] [pmlog] surface-manager LSM {} (null), Could not create GBM device (No such file or directory)
Dec 12 23:27:32 qemux86 surface-manager[16299]: [] [pmlog] surface-manager LSM {} (null), Could not open DRM device

Dec 12 23:34:46 qemux86 surface-manager.sh[144]: QSocketNotifier: Can only be used with threads started with QThread
Dec 12 23:34:46 qemux86 surface-manager.sh[144]: VMware: No 3D enabled (0, Success).
Dec 12 23:34:46 qemux86 surface-manager.sh[144]: MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/dri)
Dec 12 23:34:46 qemux86 surface-manager.sh[144]: failed to load driver: kms_swrast
Dec 12 23:34:46 qemux86 surface-manager.sh[144]: MESA-LOADER: failed to open swrast (search paths /usr/lib/dri)
Dec 12 23:34:46 qemux86 surface-manager.sh[144]: failed to load swrast driver
Dec 12 23:34:46 qemux86 surface-manager[144]: [[0;1;31m[[0;1;39m[[0;1;31m[] [pmlog] surface-manager LSM {} (null), Could not create GBM device (No such file or directory)[[0m
Dec 12 23:34:46 qemux86 surface-manager[144]: [[0;1;31m[[0;1;39m[[0;1;31m[] [pmlog] surface-manager LSM {} (null), Could not open DRM device[[0m
Dec 12 23:34:46 qemux86 crashd[246]: [] [pmlog] crashd CRASHED {"process":"surface-manager.144"}

But I didn't know how to solve it, anyone kind to give some clue, Thanks very much.

by the way, I use virtualbox Version 6.0.8 r130520 (Qt5.6.2) and windows10 os.

B&R
HyJiang

Hi @hongyong_jiang, welcome to the forum.
Could you share which version of webOS OSE you're testing with?

I use webos-image-qemux86-master-20191120010922.wic.vmdk, it should be webos-2.1.0

root@qemux86:/etc# uname -a
Linux qemux86 4.18.33-yocto-standard #1 SMP PREEMPT Wed Nov 20 01:25:47 UTC 2019 i686 GNU/Linux

root@qemux86:~# more /etc/build
-----------------------
Build Configuration:  |
-----------------------
DISTRO = webos
DISTRO_VERSION = 1.0.g
-----------------------
Layer Revisions:      |
-----------------------
meta-security     = thud:31dc4e7532fa7a82060e0b50e5eb8d0414aa7e93
meta-webos-smack  = master:2edb5047fbb369fdc55a00cc579abf795e1997b5
meta-webos-virtualization = master:2edb5047fbb369fdc55a00cc579abf795e1997b5
meta-webos-updater = master:2edb5047fbb369fdc55a00cc579abf795e1997b5
meta-webos-raspberrypi = master:2edb5047fbb369fdc55a00cc579abf795e1997b5
meta-raspberrypi  = thud:4e5be97d75668804694412f9b86e9291edb38b9d
meta-webos        = master:2edb5047fbb369fdc55a00cc579abf795e1997b5
meta-webos-backports-2.8 = master:2edb5047fbb369fdc55a00cc579abf795e1997b5
meta-webos-backports-2.7 = master:2edb5047fbb369fdc55a00cc579abf795e1997b5
meta-qt5          = warrior:6ee18b290fe5daf6a12e6cb756a27bf2f60936e2
meta-virtualization = thud:7685c7d415e0002c448007960837ae8898cd57a5
meta-updater      = thud:ee1548d2228498a8e8ff2a44d7cead23eb5cc7ed
meta-filesystems  = thud:2d088d252624b19df384aecc434d23afb636178f
meta-python       = thud:2d088d252624b19df384aecc434d23afb636178f
meta-networking   = thud:2d088d252624b19df384aecc434d23afb636178f
meta-multimedia   = thud:2d088d252624b19df384aecc434d23afb636178f
meta-oe           = thud:2d088d252624b19df384aecc434d23afb636178f
meta              = thud:cd7cf933b3235560ec71576d8f3836dff736a39f

Hi,
Please check that graphics controller is set to VMSVGA and ensure "Enable 3D Acceleration" option is selected.

Yes, already setting like these.

11

OK, then something wrong happened..
Could you please attach following logs like

  1. full dmesg logs after boot
  2. host side virtualbox log : c:\users\you\VirtualBox VMs???\Logs*

Hi all, thanks very much, I change to my home pc, it works. It seems likely office pc have some privilege limitation.

1 Like