Bug 1227357 - Evidence that none of the versions 6.4.0-150600.21.2.x86_64, 6.4.0-150600.21.3.x86_64, and 6.4.0-150600.23.7.3.x86_64 of kernel-default and/or perhaps virtualbox-kmp-default and/or virtualbox-guest-tools worked totally well in VirtualBox 7.0.18
Summary: Evidence that none of the versions 6.4.0-150600.21.2.x86_64, 6.4.0-150600.21....
Status: NEW
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Virtualization:Other (show other bugs)
Version: Leap 15.6
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Larry Rainey
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-03 17:38 UTC by Lawrence Somerville
Modified: 2024-07-12 02:41 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lawrence Somerville 2024-07-03 17:38:19 UTC 
In messages displayed during “booting” into Leap 15.6 with probably any one of the Leap-15.6 versions 6.4.0-150600.21.2.x86_64, 6.4.0-150600.21.3.x86_64, or 6.4.0-150600.23.7.3.x86_64 of kernel-default and/or in /var/log/warn of Leap 15.6 the following trio of messages often appeared:

“vmwgfx seems to be running on an unsupported hypervisor”.

“This configuration is likely broken”.

“Please switch to a supported graphics device to avoid problems.”

My recent Leap-15.6 and, before upgrading to it, Leap-15.5 operating systems have been “guest” operating systems within Oracle Corporation’s VM (Virtual “Machine”) VirtualBox 7.0.18r162988 (Qt5.15.2).  And in that VirtualBox installation I have primarily been using the Virtual “Machine” Super Video Graphics Array (VMSVGA) Graphics Controller, which can be chosen in VirtualBox via “Settings, Display, Graphics Controller” for use in versions 15.5 and 15.6 of Leap.  And usually I used the Lightweight X Windows System, Version 11 (X11) Desktop Environment (LXDE) in Leap 15.5.  In Leap 15.5 this arrangement gratefully worked well with version 5.14.21-150500.55.65.1.x86_64 of kernel-default from an online, openSUSE, Leap-15.5, software repository when relying on the VirtualBox Guest Additions in kernel-default with the software packages virtualbox-guest-tools 7.0.18... and virtualbox-kmp-default, probably version 7.0.18_k5.14.21_150500.55.59-lp155.2.24.1.x86_64, installed.

Back to discussing my Leap-15.6 installation, when I instead “booted” into its LXDE with the version 5.14.21-150500.55.65.1.x86_64 of the software package kernel-default, which was likely “passed along” to my Leap-15.6 installation in an upgrade of my Leap-15.5 installation, I did not receive the above, quoted trio of messages!  I did, however, see the message

Invalid DMI field header

during such “booting.”

And it is possible that the so-called “bug” number 1226910 I reported on June 24, 2024 on https://bugzilla.opensuse.org/show_bug.cgi?id=1226910 on the Internet might somehow be related to the problem I report here.
But on the contrary when “booting” into Leap 15.6 with at least version 6.4.0-150600.21.2.x86_64 of kernel default I could gratefully have the desired VirtualBox Guest Additions (VBGA) functions of the copying and “pasting” of text between and the sharing of files and folders within a folder shared by my “host,” Windows-10 operating system and “guest,” Leap-15.6 operating systems, as well as have a wide window for my Leap-15.6 LXDE.  And in the later versions 6.4.0-150600.21.3.x86_64 and 6.4.0-150600.23.7.3.x86_64 of Leap-15.6 kernel-default I did not notice the narrow window for Leap-15.6 LXDE which is characteristic of a resizing problem when the VBGA are not installed or not working as they were designed to work.  So I conclude that probably none of the versions 6.4.0-150600.21.2.x86_64, 6.4.0-150600.21.3.x86_64, and 6.4.0-150600.23.7.3.x86_64 of kernel-default or else their associated software packages of virtualbox-kmp-default and/or virtualbox-guest-tools supplied through Leap-15.6 online repositories was designed to work totally well in the hypervisor VirtualBox 7.0.18r162988 (Qt5.15.2).  Therefore, at least in the short run of time, please produce a new version of kernel-default and/or its associated software packages virtualbox-kmp-default and virtualbox-guest-tools for a Leap-15.6 “guest” installation in VirtualBox 7.0.18r162988 (Qt5.15.2) that will at least not result in the problems I report here and the problem I reported on https://bugzilla.opensuse.org/show_bug.cgi?id=1226910 and what might be problems I reported on  https://bugzilla.opensuse.org/show_bug.cgi?id=1227354.  Thank you in advance for your efforts in these regards.
Comment 1 Lawrence Somerville 2024-07-12 02:41:01 UTC 
The “trio” of messages, including the strong one of “unsupported hypervisor” of VirtualBox 7.0.18, that I reported in this “bugzilla” report numbered 1227357 also appeared after performing my actions 1-4 in my July 11, 2024 comments in my “bugzilla” postings numbered 1226910 and 1227354, still using VirtualBox 7.0.18.  But so far, despite the look of severity of the message “unsupported hypervisor,” gratefully that message does not seem to be of any consequence in the LXDE of my Leap-15.6 installation

with version 6.4.0-150600.23.7.3.x86_64 of kernel-default running,

the Graphics Controller of VirtualBox 7.0.18 set to VMSVGA (Virtual “Machine” Super Video Graphics Array), and

with my relying on the VirtualBox Guest Additions which I assume are included by openSUSE in that version of kernel-default and depending well on the installed software packages virtualbox-kmp-default 7.0.18_k6.4.0_150600.21-lp156.1.4 and virtualbox-guest-tools 7.0.18-lp156.1.6!