Installation and reboot went smoothly.

System:   Host: canopus Kernel: 5.2.10-desktop-1.mga7 x86_64 bits: 64 
CPU:      10-Core: Intel Core i9-7900X type: MT MCP speed: 1200 MHz 
Machine:  Type: Desktop Mobo: ASUSTeK model: TUF X299 MARK 2 v: Rev 1.xx 
Graphics  Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nouveau v: kernel

Everything works as before but the graphics driver needs to be changed.

CC: (none) => tarazed25

Pursuant to comment 1:

Ran drakx11 to install the proprietary nvidia graphics driver.
Rebooted.
$ graphicsGraphics:
  Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nvidia v: 430.26 
  Display: x11 server: Mageia X.org 1.20.4 driver: nvidia,v4l 
  resolution: 2560x1440~60Hz 
  OpenGL: renderer: GeForce GTX 1080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 430.26 

All is well, almost.
Stress tests ran fine, e.g.
$ stress -c 11 -t 30
Core temperature rose, graphics stayed cool.
Ran the other three options and tried out some common applications.
No problems except glmark2 failing with the familiar GLXBadContext error.
I have asked on the QA discuss list for people with nvidia graphics hardware to check how glmark2 behaves and report good or ill in order to isolate the cause of this problem.  No takers so far.  https://bugs.mageia.org/show_bug.cgi?id=25204
It has occurred in other versions of Mageia going back and has affected other applications but so far seems to affect glmark2 only in Mageia7.  I would suggest the cause lies somewhere in upgrading kernels or reinstalling the nvidia graphics driver.  It is too early to identify particular graphics cards or otherwise.

Referring to comment 2, installed dkms-nvidia-current having been reminded that glmark2 was known to have worked with nvidia 430.40.  After reboot glmark2 still fails.

Update installed in x86_64 : 2018 HP desktop with Intel GPU.

sudo urpmi --searchmedia testing kernel-desktop-latest virtualbox-kernel-desktop-latest cpupower

Reboot, all is Ok : networking, opengl, and Windows 7 VM.

CC: (none) => lists.jjorge

Tested also in i586 with a 2005 laptop : ATI X600 graphics.
Network, gl-117, power suspend ok.

on mga7-64  kernel-desktop  plasma

packages installed cleanly:
- cpupower-5.2.10-1.mga7.x86_64
- kernel-desktop-5.2.10-1.mga7-1-1.mga7.x86_64
- kernel-desktop-devel-5.2.10-1.mga7-1-1.mga7.x86_64
- kernel-desktop-devel-latest-5.2.10-1.mga7.x86_64
- kernel-desktop-latest-5.2.10-1.mga7.x86_64
- kernel-userspace-headers-5.2.10-1.mga7.x86_64
- virtualbox-kernel-5.2.10-desktop-1.mga7-6.0.10-4.mga7.x86_64
- virtualbox-kernel-desktop-latest-6.0.10-4.mga7.x86_64

system re-booted normally:
$ uname -r
5.2.10-desktop-1.mga7

# dkms status
virtualbox, 6.0.10-1.mga7, 5.2.10-desktop-1.mga7, x86_64: installed-binary from 5.2.10-desktop-1.mga7
virtualbox, 6.0.10-1.mga7, 5.2.7-desktop-1.mga7, x86_64: installed-binary from 5.2.7-desktop-1.mga7

vbox and client launched normally

no regressions observed

looks OK for mga7-64 on this system:

Mobo: Dell model: 09WH54 v: UEFI [Legacy]: Dell v: 2.13.1 
CPU: Intel Core i7-6700
Graphics: Intel HD Graphics 530 (Skylake GT2)

also updated to kernel-desktop586-5.2.10-1 in a mga7 32 bit vbox VM - 
no regressions observed

CC: (none) => jim

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2019-0108.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED