Date: Tue, 25 Jun 2019 13:47:38 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: Johannes Lundberg <johalun@FreeBSD.org> Cc: vbox@freebsd.org, FreeBSD X11 <x11@FreeBSD.org> Subject: Re: Accelerated graphics in vbox 6 Message-ID: <a26e5ea8-e1c1-1546-83fb-0a853729a7ff@FreeBSD.org> In-Reply-To: <c021b0dc-b909-cca7-8d7f-9bb61c23e32b@FreeBSD.org> References: <4a697e5a-8ecc-cda9-6f80-3e78d09c924f@FreeBSD.org> <874a0def-1e1e-971b-ae65-4e700295a9e9@FreeBSD.org> <d2bc45b6-171d-01d9-4962-ab4665111003@FreeBSD.org> <c021b0dc-b909-cca7-8d7f-9bb61c23e32b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NtWFx1HzCdBcKW9oGYZcCbYD8YzVu3B29 Content-Type: multipart/mixed; boundary="HoTf2FBgAbHKqPlZmDximuyxVevNteD1n"; protected-headers="v1" From: Jung-uk Kim <jkim@FreeBSD.org> To: Johannes Lundberg <johalun@FreeBSD.org> Cc: vbox@freebsd.org, FreeBSD X11 <x11@FreeBSD.org> Message-ID: <a26e5ea8-e1c1-1546-83fb-0a853729a7ff@FreeBSD.org> Subject: Re: Accelerated graphics in vbox 6 References: <4a697e5a-8ecc-cda9-6f80-3e78d09c924f@FreeBSD.org> <874a0def-1e1e-971b-ae65-4e700295a9e9@FreeBSD.org> <d2bc45b6-171d-01d9-4962-ab4665111003@FreeBSD.org> <c021b0dc-b909-cca7-8d7f-9bb61c23e32b@FreeBSD.org> In-Reply-To: <c021b0dc-b909-cca7-8d7f-9bb61c23e32b@FreeBSD.org> --HoTf2FBgAbHKqPlZmDximuyxVevNteD1n Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 19. 5. 21., Jung-uk Kim wrote: > On 19. 5. 21., Johannes Lundberg wrote: >> Hi >> >> On 5/21/19 11:46 AM, Jung-uk Kim wrote: >>> On 19. 5. 21., Johannes Lundberg wrote: >>>> Hi vbox folks! (cc: x11 list) >>>> >>>> According to this >>>> https://www.phoronix.com/scan.php?page=3Darticle&item=3Dvirtualbox-6= 0-vmsvga&num=3D1 >>>> vbox can now use the vmwgfx kernel driver for accelerated graphics. = With >>>> that I assume that virtualbox's own drm driver project is scrapped. >>> Actually, they moved vboxvideo KMS/DRM driver to Linux kernel. >>> >>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tr= ee/drivers/gpu/drm/vboxvideo >> >> It's been there for quite some time and no progress have been made for= >> the time I've been tracking it. Seems abandoned to me and my impressio= n >> is that that one is scrapped in favor of vmwgfx... Do anyone know if >> vboxvideo is suppose to be in working state (the one in linux kernel)?= >=20 > It was added to staging for almost two years ago. Please see the > original patch submission. >=20 > https://lwn.net/Articles/726355/ >=20 > Recently they moved it out of staging (via merging drm-next-2019-05-09)= =2E >=20 > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm= it/?id=3D131abc56e1bacef23cb7b340519d36e2f5adb2a9 >=20 > It means Linux 5.2 release will have it by default. >=20 > It doesn't look dead to me. ;-) >=20 >>> And DDX driver was moved to Xorg repository. >>> >>> https://cgit.freedesktop.org/xorg/driver/xf86-video-vbox >>> >>>> I've been working on porting vmwgfx from Linux to our linuxkpi. It w= orks >>>> pretty well with freebsd 13 as vmware guest on macos as long you're >>>> using only one vcpu (some race condition issue to be solved..).=C2=A0= It >>>> would be cool if we could get accelerated graphics in vbox, with fre= ebsd >>>> as both host and guest since vmware can't run as host on freebsd. >>> Can you please port the vboxvideo driver to linuxkpi? >> >> vmwgfx seems like the better choice if it's used by both vmware and vb= ox >> (v6+). But if it's suppose to be in a working state I can take a look.= =2E >=20 > ... >=20 > AFAIK VirtualBox graphics stack is in a working state. I found it is ported now. https://github.com/FreeBSDDesktop/kms-drm/commits/drm-v5.0 I tried it and it's somewhat working, thanks! However, I found two problems. 1. Console does not refresh automatically. When vboxvideo.ko is loaded, console stays black. Console preview looks fine, though. I found it's redrawn when the window is resized. Note I only tried it on a Windows host. I will try it with FreeBSD host soon but I think it'll be the same. 2. Console does not resize dynamically. Actually, it is not vboxvideo.ko's fault. It happens because vt(4) does not support monitor hotplug. https://www.virtualbox.org/wiki/Guest_resizing After I tried it out, I realized vboxvideo.ko is just a KMS driver and modesetting driver is used for X.org. IOW, we cannot resize X.org window dynamically when vboxvideo.ko is used. With vboxvideo.ko or vboxvideo_drv.so, 3D acceleration is still handled by the Chromium OpenGL pass-through stub. As always, it may be enabled with setting OPENGL option for emulators/virtualbox-ose-additions. BTW, Phoronix once reported 3D acceleration with VMware driver does not look good on VirtualBox anyway. :-p http://www.phoronix.com/vr.php?view=3D27348 Jung-uk Kim --HoTf2FBgAbHKqPlZmDximuyxVevNteD1n-- --NtWFx1HzCdBcKW9oGYZcCbYD8YzVu3B29 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAl0SXkEACgkQfJ+WJvzb 8UbzAQf8D3N3WHbmbI3ZHUvHh0fI5WRrzT9KWkYbf7z7MQXTtzCBx95zqfTfXYWs zARWN90W8FGdLR0p9BkJ2f+R7xSB9W1DrB0wjGVNsX9FN6jMwIMXKBgxJ3D8YQOd pFQqCKiuGYlZobRU5YFmqm2w2iZgRdSCuLygDXNKs1OcwcSQ+T3cmoSZHJiaseor FeDd+tq5KiXv1ubJDMakVOUwlUUBwGWKBzEXOm4EckT7CVujn6TQWV3pWeFRCHka ozD+5jnhxtQcJ+vcbFLSYO9tPdXRjThpvueaO5OFdYmYD995L65P6xxTwfXvjwBW PECt92UUapGqapqB7MhSCpW1TxZDAA== =OxuG -----END PGP SIGNATURE----- --NtWFx1HzCdBcKW9oGYZcCbYD8YzVu3B29--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a26e5ea8-e1c1-1546-83fb-0a853729a7ff>