VirtualBox

Changes between Initial Version and Version 1 of Ticket #19950, comment 3


Ignore:
Timestamp:
Oct 13, 2020 1:20:20 PM (4 years ago)
Author:
burdi01

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #19950, comment 3

    initial v1  
    1 As an experiment I fell back on Slackware's Current64 generic kernel: 5.4.70. The VB version still is the patched VirtualBox-6.1.14-140239-Linux_amd64.run. To my very surprise starting a VM went without a hitch![[BR]]
     1As an experiment I fell back on Slackware's Current64 generic kernel: 5.4.70. The VB version still is the patched VirtualBox-6.1.14-140239-Linux_amd64.run. To my very surprise starting a VM went without a hitch.[[BR]]
    22It may or may not be a coincidence that this 5.4.X kernel is the same as Xubuntu's ...[[BR]]
    33The VBox.log (uploaded as Slackware.VBox.log.1) shows that VMMR0.r0 is called and that GUI message reads: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x0 x 1920x1173.[[BR]]
    4 In other words the "0x0" is a red herring ...
     4It now looks likely that the VMMR0.r0 being called is the decisive factor and that the "0x0" is a red herring ...

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette