Description of problem: As outlined in the QA meeting of 24 Sept 2020 Virtualbox 6.1 as used in Cauldron (M8) does not support higher frame resolutions for older versions of Megeia. The highest frame size appears to be just 1024x768 There were several reasons mentioned for this such as the absence of VboxVGA and VboxSVGA. This bug is to better define what this issue is and when, or if, it can be resolved. The QA meeting Log can be found here: http://meetbot.mageia.org/mageia-qa/2020/mageia-qa.2020-09-24-19.02.log.html
This sounds like a very unfortunate bug, to say the least, especially since we'll have to update Mageia 7 to VirtualBox 6.1.x for kernel 5.8 support. There's nothing we can so about it though unless upstream fixes it, so it needs to be reported there if hasn't been already (probably has, just have to find the upstream bug report).
Need testing. I do see VMSVGA, VboxSVGA and VboxVGA as proposed video drivers for client with virtualbox 6.1.
CC: (none) => ouaurelienKeywords: (none) => NEEDINFO, NEEDTEST
Aurelien's comment above counters what Bill suggested in comment 0: "the absence of VboxVGA and VboxSVGA". Can this be clarified?
Source RPM: (none) => virtualbox-6.1.14-3.mga8.src.rpmCC: (none) => lewyssmith
(In reply to Lewis Smith from comment #3) > Aurelien's comment above counters what Bill suggested in comment 0: > "the absence of VboxVGA and VboxSVGA". Can this be clarified? Back you you shortly. I'm just finishing up some extensive testing.
Where I'm at: On real hardware. The platform: Dell Inspiron 5000 15.6in Model 5593 Laptop 10th Generation Intel® Core™ i5-1035G1 Processor, 4 cores, 8 threads Intel® UHD Graphics with shared graphics memory 8 GB, 1 x 8 GB, DDR4, 2666 MHz DRAM 256GB M.2 PCIe NVMe SSD The internal SSD is turned off. All bootable media is via the USB port(s). Media is a combination of either SSD's or Flashdrives. All very fast. The feel and performace between the internal NVMe drive and the external SSD or Flashdrives is basically the same. I've a couple of SSD drives that feel faster then the internal NMVe drive. Media Mageia 7.1 5.7.19-desktop-1.mga7 virtualbox-6.0.24-1.mga7.x86_64 M7.1 x86_64 Plasma VBoxVGA 1920x1080 netinstall client M7.1 x86_64 Plasma VMSVGA 1024x768 netinstall client M7.1 x86_64 Plasma VBoxSVGA 1920x1080 netinstall client M8 x86_64 Plasma VBoxVGA 1920x1080 netinstall client M8 x86_64 Plasma VMSVGA 1920x1080 netinstall client M8 x86_64 Plasma VBoxSVGA 1920x1080 netinstall client M7.1 x86_64 Xfce VBoxVGA 1920x1080 Live-DVD client M7.1 x86_64 Xfce VMSVGA 1024x768 Live-DVD client M7.1 x86_64 Xfce VBoxSVGA 1920x1080 Live-DVD client M8 x86_64 Xfce VBoxVGA 1920x1080 Live-DVD client M8 x86_64 Xfce VMSVGA 1920x1080 Live-DVD client M8 x86_64 Xfce VBoxSVGA 1920x1080 Live-DVD client Media Mageia 8 5.8.11-desktop-2.mga8 irtualbox-6.1.14-3.mga8.x86_64 M7.1 x86_64 Plasma VBoxVGA conneot be selected M7.1 x86_64 Plasma VMSVGA 1024x768 netinstall client M7.1 x86_64 Plasma VBoxSVGA cannot be selected M8 x86_64 Plasma VBoxVGA cannot be selected M8 x86_64 Plasma VMSVGA 1920x1080 netinstall client M8 x86_64 Plasma VBoxSVGA cannot be selected M7.1 x86_64 Xfce VBoxVGA cannot be selected Live-DVD M7.1 x86_64 Xfce VMSVGA critical error at launch Live-DVD M7.1 x86_64 Xfce VBoxSVGA cannot be selected Live-DVD M8 x86_64 Xfce VBoxVGA cannot be selected Live-DVD M8 x86_64 Xfce VMSVGA 1920x1080 Live-DVD Live-DVD M8 x86_64 Xfce VBoxSVGA cannot be selected Live-DVD It's important to note that in the cases of the VBoxVGA and VBoxSVGA the selections are displayed but when selected bounce back to VMSVGA when the next setup selection is made.
Media Mageia 8 5.8.11-desktop-2.mga8 irtualbox-6.1.14-3.mga8.x86_64 M7.1 x86_64 Xfce VMSVGA critical error at launch Live-DVD Critical error displayed: A critical error has occurred while running the virtual machine and the machine execution has been stopped. For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /home/wilcal/VirtualBox VMs/M7.1 x86_64 Xfce Live-DVD/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now. critical_error_VBox.log file attached.
Created attachment 11894 [details] critical error Vbox log file
Got it to work. First make sure the user is a member of the vboxusers group. Logout/in after any group change for that to take effect. As root. run "chgrp vboxusers /dev/vbox*", and "chmod g+rw /dev/vboxdrv". Then, using the VMSVGA display driver, started the client with 7.1 x86_64 installed. After login, restored the dialog box containing the guest display using the down arrow near the top right of that dialog, then maximized it. The guest resized to match, as normal. Shutdown and restarted the guest to confirm the resized display stuck, which it did. So it's a permissions problem in the virtualbox rpm. Found it based on http://www.mgreene.org/?cat=39 though that fix alone is not enough.
CC: (none) => davidwhodginsKeywords: NEEDINFO, NEEDTEST => (none)
Another tour-de-force, Dave. Thanks to Bill for his tests. There is enough info here to assign to the kernel group, for VB.
Assignee: bugsquad => kernelCC: lewyssmith => (none)
VirtualBox 6.1.16 (released October 16 2020) This is a maintenance release. The following items were fixed and/or added: VMM: Fixed random memory corruption and XMM register state corruption inside the VM when Hyper-V is used (bug #19695) VMM: Fixed VMSVGA 3D support with Linux guests when Hyper-V is used (bug #19884) GUI: Fixed some Qt related crashes on macOS Big Sur Oracle Cloud Infrastructure integration: Fixed network integration not working behind some proxies USB: Mask out remote wake capability to avoid unresponsive devices Audio: Fixed issues with audio playback after host goes to sleep (bug #18594) Serial: Keep transferring data if the status line monitoring fails Serial: Fixed blocking a re-connect when TCP mode is used (bug #19878) HPET: Fixed inability of guests to use the last timer VBoxManage: Fixed detection of system locale when running 'VBoxManage unattended install' without --locale (bug #19856) macOS host: Installer on Big Sur is now reminding user that system has to be rebooted to load the installed KEXTs Linux host and guest: Support kernel version 5.9 (bug #19845) Linux guest: Workaround to improve resizing of 32-bit VMs with VMSVGA graphics controller, and do not try to use RandR version 1.3 due to bugs causing the X server to hang Linux guest: Fixed VBoxService crashing in the CPU hot-plug service under certain circumstances during a CPU hot-unplug event (bugs #19902 and #19903) Linux guest: Fixed Guest additions build for RHEL 8.3 beta (bug #19863)
(In reply to Dave Hodgins from comment #8) > Got it to work. First make sure the user is a member of the vboxusers group. > Logout/in after any group change for that to take effect. > > As root. run "chgrp vboxusers /dev/vbox*", and "chmod g+rw /dev/vbox*". > > Then, using the VMSVGA display driver, started the client with 7.1 x86_64 > installed. After login, restored the dialog box containing the guest display > using the down arrow near the top right of that dialog, then maximized it. > The guest resized to match, as normal. > > Shutdown and restarted the guest to confirm the resized display stuck, which > it did. > > So it's a permissions problem in the virtualbox rpm. Found it based on > http://www.mgreene.org/?cat=39 though that fix alone is not enough. Doing this give a working Console resolution to Mageia UEFI VM and also BIOS VM. Note that sddm displays itself correctly to the size of the window VM. But as soon as Plasma is launched, the resolution switches to 800x600 and trying to set it to a higher one results to a set back to 800x600.
Also, as a side note: Tested today some VM under M8 Plasma x86_64, fully updated. $ uname -a Linux mageia.local 5.10.2-desktop-1.mga8 #1 SMP Mon Dec 21 13:01:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ urpmq -i virtualbox virtualbox-6.1.16-8.mga8.src.rpm Run a M8 Xfce VM (x86_64) with VMSVGA: good screen support resolution which fits the virtualbox window. Run a M7 Xfce VM (x86_64) with VMSVGA: idem. But: Run a M7 Plasma VM (x86_64) with VMSVGA: screen fixed to 1024x768 which gets even worse after updating and a reboot: I only get 800x600 resolution. Workaround: Run same VM with VboxSVGA graphic adapter, Resolution can be set to what you want. NOT TESTED: Run a M8 Plasma VM with VMSVGA RATIONALE: I do think a issue in KWin / KScreen stack: See: https://bugs.kde.org/show_bug.cgi?id=407058 So UPSTREAM tag. Please ping here.
Source RPM: virtualbox-6.1.14-3.mga8.src.rpm => virtualbox-6.1.16-8.mga8.src.rpmCC: (none) => tmbURL: (none) => https://bugs.kde.org/show_bug.cgi?id=407058Assignee: kernel => pkg-bugsKeywords: (none) => UPSTREAM
Summary: Vbox 6.1 does not support M7.1 client higher screen size resolutions => Virtualbox 6.1 does not support Plasma client higher screen size resolutions
And yet the display on my M7 Plasma (x86_64) VM is working as it should using VMSVGA. But x86 VMs are a different story. With an M7 host: M7 Plasma boots with an error message in a small box that seems informational, but... VMSVGA fixes the screen size at 800x600. VBoxVGA works, except that it overscans if the window is maximized, cutting off the "Mageia" at the bottom of the screen. VBoxSVGA changes size, but always overscans. I was going to open a new bug about the error message, but after some experimentation it looks like this complaint may belong here... M7 Xfce doesn't have the error message, but... None of the graphic controller options make a bit of difference in screen size. M8 Xfce is the same as M7 Xfce. That makes me wonder about the 6.1.16 guest additions, the 32-bit ones in particular.
CC: (none) => andrewsfarm
Under M8 host with Plasma and nvidia-current nonfree drivers, Virtualbox is virtualbox-6.1.16-10.mga8 M8 Client with Plasma can do have higher screen resolution with VMSVGA (default for Linux guest) if 3D acceleration is enabled in guest VM configuration. But, each windows is opened, guest system logs: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. twice, each time a window is opened.
please try with virtualbox-6.1.16-12.mga8 it provides VBoxDRMClient and systemd integration
there is now a virtualbox-6.1.16-15.mga8 with even more fixes
(In reply to Aurelien Oudelet from comment #14) > > But, each windows is opened, guest system logs: > [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. > [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. > This is a known upstream issue, afaik they have some fixes coming in 6.1.18
Note that support for higher screen resolution and resizing has been landed in virtualbox-6.1.18-2.mga8 For the latter:(In reply to Thomas Backlund from comment #17) > (In reply to Aurelien Oudelet from comment #14) > > > > > But, each windows is opened, guest system logs: > > [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. > > [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. > > > > This is a known upstream issue, afaik they have some fixes coming in 6.1.18 This is still valid. Closing for screen size resolution in Plasma VM Client with VMSVGA video driver. Cloning for the above error.
Really. Feel free to reopen for this.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED