Description of problem: Installing Vbox 6.0 on M7 x86_64 Plasma Hardware: Intel Core i5-4460 Haswell Quad-Core 3.2GHz LGA 115 Gigabyte GA-B85M-D3H LGA 1150 Intel B85 chipset Integrated Graphics Processor - Intel HD Graphics support Audito chipset - Realtek ALC892, 7.1 channels Corsair Vengeance 8GB ( 2 x 4GB ) 240-pin DDR3 SDRAM 1600 isos used to create clients: Mageia-6.1-LiveDVD-GNOME-x86_64-DVD.iso Mageia-7-beta2-Live-Xfce-i586.iso Results in the clients only displaying a 640x480 window. The client works but in a very tiny box.
rpms installed: The following 20 packages are going to be installed: - dkms-2.0.19-39.mga6.noarch - dkms-minimal-2.0.19-39.mga6.noarch - dkms-vboxadditions-6.0.4-4.mga7.noarch - dkms-virtualbox-6.0.4-4.mga7.noarch - kernel-desktop-devel-4.20.11-2.mga7-1-1.mga7.x86_64 - kernel-desktop-devel-4.20.12-1.mga7-1-1.mga7.x86_64 - kernel-desktop-devel-latest-4.20.12-1.mga7.x86_64 - lib64bz2-devel-1.0.6-12.mga7.x86_64 - lib64elfutils-devel-0.175-2.mga7.x86_64 - lib64lzma-devel-5.2.4-2.mga7.x86_64 - lib64ncurses-devel-6.1-20181117.3.mga7.x86_64 - lib64zlib-devel-1.2.11-7.mga7.x86_64 - multiarch-utils-1.0.14-2.mga7.noarch - virtualbox-6.0.4-4.mga7.x86_64 - virtualbox-guest-additions-6.0.4-4.mga7.x86_64 - virtualbox-kernel-4.20.11-desktop-2.mga7-6.0.4-26.mga7.x86_64 - virtualbox-kernel-4.20.12-desktop-1.mga7-6.0.4-28.mga7.x86_64 - virtualbox-kernel-desktop-latest-6.0.4-28.mga7.x86_64 - x11-driver-video-vboxvideo-1.0.0-5.mga7.x86_64 - xrandr-1.5.0-2.mga7.x86_64 274MB of additional disk space will be used. 90MB of packages will be retrieved.
There was a kernel update today so maybe the Vbox additions are not up to date with this.
CC: (none) => marja11Assignee: bugsquad => tmb
I noticed this after trying to create a 64-bit M6.1 Xfce guest from the Live iso. At the time, I assumed that the problem was that the guest additions we supply with Mageia 6(.1) are for the vbox 5.2 series, rather than the 6.0 series. But, after removing the guest additions we provide, I attempted to install the 6.0.4 guest additions from a downloaded CD image. That seemed to work - for that session. After shutting down and rebooting, the guest's display was back to the same size. Guests that were created using the 5.2 series vbox from Mageia 6 don't have this problem. They display in the correct resolution, although I always get a notice about the installed guest additions being out of date.
CC: (none) => andrewsfarm
CC: (none) => marci_r
Install: Mageia-7-beta3-x86_64.iso 3/24/19 md5sum 67a73adf6926f2fe5106188174aa0e52 To Intel non-nvidia platform all goes well Install Vbox to that same install and nothing seems to have changed If anything gotten worse. Login text on the log in screen is blank but logs in to a 640x480 screen. I did notice that: vboxadditions-kernel-desktop-latest is missing during the install. That rpm has always been there. Now in M7 it's missing. Is that the problem? There's a new file: dkms-vboxadditions does that replace it?
Still in effect with the beta3 Round 3 isos. New guests created in VirtualBox 6.0.4 do not show the proper resolution. This is true of Mageia 6 and Mageia 7 guests. I have not yet tried creating a Windows guest in VirtualBox 6.0.4 Guests that were created in VirtualBox 5.2.24 and earlier do show the correct resolution when imported to VirtualBox 6.0.4. This includes Mageia 7 guests, and Mageia 6 guests that are upgraded to Mageia 7 after being imported. It also includes a Windows XP guest. Guests exported from VirtualBox 6.0.4 will not even boot in VirtualBox 5.2.24. (Not unexpected.)
Keywords: (none) => 7beta3
(In reply to Thomas Andrews from comment #5) > Still in effect with the beta3 Round 3 isos..... Yes, this still persists on my M7 Hosts here. I would like to raise the Priorty of this Bug to "High" if not Release Blocker And the Severity to at least "major" We can't release M7 with Vbox in this condition.
Changing Priority to Release Blocker Changing Severity to major
Severity: normal => majorPriority: Normal => release_blocker
[copied from qa-discuss] Just tested creating a new guest in VBox on Mageia 7, keeping all the default settings, then installing a minimal Xfce system from Mageia-7-beta3-x86_64. I found that the guest display size was fixed at 1024x768, and couldn't be resized. Investigating the difference in settings between that and an old guest (which could be resized) showed that the Graphics controller for the old guest was set to VBoxVGA, but for the new guest was set to VMSVGA. Setting the new guest to use VBoxVGA caused it to default to 800x600, but it could then be resized by dragging the corner of the window. Notes: 1. Resizing via the View->Virtual Screen 1 menu doesn't work initially. After resizing by dragging the corner of the window it does. This has always been the case for me. 2. After power cycling, the guest reverts to 800x600, and has to be resized again. From previous tests, I believe this behaviour depends on the age of the guest - a guest installed from beta2 (and not updated) retained the last selected size. 3. LightDM cannot be resized - you have to wait until you get to the DE.
CC: (none) => mageia
Thanks Martin for the tip. On my Nvidia i7 platform by simply changing the Clients Graphics controller from the default VMSVGA to VboxVGA lots of things are now working correctly. I've still got lots of combinations to test but maybe, just maybe, making that simple change gets Vbox back in shape. I need a few days to try the various combinations. Note: Changing it to VboxSVGA rsults in booting to a black screen.
Virtualbox 6.0.6 is now in Cauldron, and has several fixes to vmsvga support, including remembering changed resolution... https://www.virtualbox.org/wiki/Changelog-6.0#v6
On my i5 Intel Graphics platform this simple change seems to have worked. I have even created Vbox Clients and updated them and the resolution is correct. The two platforms under test are using a 1920x1200 monitor.
Testing 6.0.6, I find: 1. Using VMSVGA, you still can't resize by dragging the window corner or from the View menu. But you can resize using the DE system settings (tested in Xfce and in Cinnamon). And when resized that way, it is remembered after a power cycle, although it only applies to the DE, not to the DM. One other plus - 3D acceleration works. One oddity - the Plymouth boot splash doesn't show in the main window, although it does show in the Preview. 2. The VBoxSVGA option now works, but I see no difference in behaviour between that and VBoxVGA. In both cases the display size can be changed by dragging the window corner or from the View menu, but gets reset after a power cycle.
Ok, so lets tinker with this as it is and in a week or so we'll decide if it's acceptable. We'll probably have to put something in the release notes.
Setting the Display Graphics Controller to "VBoxVGA" fixes the problem 100% of the time. Setting this Bug to "RESOLVED"
Resolution: (none) => FIXEDStatus: NEW => RESOLVED