|
Bugzilla – Full Text Bug Listing |
| Summary: | Virtualbox: "vmwgfx seems to be running on an unsupported hypervisor" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Rihards Olups <richlv> |
| Component: | Virtualization:Other | Assignee: | Larry Rainey <llrainey15> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Rihards Olups
2024-03-10 21:34:36 UTC
Host OS Are you using zypper dup to do the updates. What commands did you use to install virtualbox. I have Tumbleweed host and guests - no issues I have Leap host and Tumbleweed guests - no issues Please try the following On host zypper dup zypper rm virtualbox reboot zypper in virtualbox reboot Virtualbox is not in the kernel until you reboot. now see if all works. Sorry for missing some of the detail in the initial report. Host: MacOS, tried Virtualbox 7.0.10 and 7.0.14. Guest: Latest Tumbleweed, updated with dup. In https://www.virtualbox.org/wiki/Changelog, there's an entry "Added initial support for kernels 6.5 and 6.6", but nothing about kernel 6.7, is that OK? You do not install Virtualbox host on a guest. First remove virtualbox and reboot zypper rm virtualbox after reboot zypper in virtualbox-kmp-default virtualbox-guest-tools reboot the gui in tumbleweed should work now. the Virtualbox gui is in MacOS and if there is a problem with it, you need to report it to Oracle Virtualbox as we do not support any MacOS only OpenSUSE Linux. Very sorry if the initial report was confusing. On the guest, only virtualbox-kmp-default and virtualbox-guest-tools are installed. With the "graphical interface" I meant X.org etc - it still seems to be X.org. The vmwgfx error message pops up in terminal. /var/log/Xorg.0.log also contains: (EE) Could not open default font(EE) Wondering whether this might be the real culprint and the vmwgfx error is just a red herring. Found https://forums.opensuse.org/t/unable-to-start-x-after-power-failure-during-zypper-dup-could-not-open-default-font-fixed/120311/2 - cannot fix it the same way, as no rollback seems to be easily possible. Based on the error message, did zypper in -f xorg-x11-fonts-core, and xorg now starts up again. Marking this as resolved-invalid, as it seems to have been (somehow) corrupted package install, not a bug. Sorry again if the original report was not detailed enough. |