windows xp black elegant edition virtual

(3) VirtualBox memorized that it was previously being displayed in a 2.5k window (2560x1440). If this solves your problem, it is different from the problem of user morphx. Your 4k display needs nearly 32 MB for a single frame.

(2) You've provided 32 MB of Video Memory. (1) VirtualBox thinks it is running on a 2k display (1920x1080, full HD) on the host. GDBus.Error:: Unable to uninhibit: Invalid cookie (5) 00:01:02.693068 GUI: UIMachineViewFullscreen::adjustGuestScreenSize: Desired hint 2560x1440 for guest-screen #0 differs from the one in IDisplay, adjustment is required.Ġ0:01:02.693090 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2560x1440Ġ0:01:02.693098 VMMDev: SetVideoModeHint: Got a video mode hint at 0Ġ0:01:02.702734 QDBus inhibition call error for service : .Quark._g_2dio_2derror_2dquark.Code36.

(3) 00:00:00.816954 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 2560x1296 (1) 00:00:00.671573 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometr圜alculated: Screen 0 work area is actually resized to: 0x18 x 1920x1047 Your VBox.log file shows some interesting details regarding display resolutions (selected lines): You don't still have a VBox.log file from 6.1.44 by chance? )Įdit: I can mention that I have rather high resolution, 3840x2160 pixels, if that could have anything to do with the problem. Regarding the assumption that VB 6.1.44 shows the exact same behavior (not only the user-(in-)visible part )), I'll take a look at the manageable source diff later.

Windows xp black elegant edition virtual