Hello,

>Here is the log - Tobias also provided a log already, see 
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902897#15 


thanks you both!
Can somebody please open an upstream ticket and link it here?
https://www.virtualbox.org/wiki/Bugtracker


I tried to debug the issue, but I have no clue, specially because code
changes in this release are not affecting that VMM area.
 

thanks

Gianfranco 
VirtualBox VM 5.2.14_Debian r122571 linux.amd64 (Jul  2 2018 17:50:29) release 
log
00:00:00.983105 Log opened 2018-07-03T08:34:32.706029000Z
00:00:00.983106 Build Type: release
00:00:00.983109 OS Product: Linux
00:00:00.983110 OS Release: 4.14.32-voc
00:00:00.983110 OS Version: #1 SMP Fri Apr 6 12:36:37 CEST 2018
00:00:00.983127 DMI Product Name: HP ZBook 15 G2
00:00:00.983132 DMI Product Version: A3008CD10003
00:00:00.983169 Host RAM: 7896MB (7.7GB) total, 3941MB (3.8GB) available
00:00:00.983173 Executable: /usr/lib/virtualbox/VirtualBox
00:00:00.983174 Process ID: 23905
00:00:00.983174 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.987436 Installed Extension Packs:
00:00:00.987451  Oracle VM VirtualBox Extension Pack (Version: 5.2.14 r123301; 
VRDE Module: VBoxVRDP)
00:00:00.987459  VNC (Version: 5.2.14 r122571; VRDE Module: VBoxVNC)
00:00:00.989502 Console: Machine state changed to 'Starting'
00:00:00.989614 Qt version: 5.10.1
00:00:00.989621 X11 Window Manager code: 3
00:00:00.997829 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:00.998302 X Server details: vendor: The X.Org Foundation, release: 
12000000, protocol version: 11.0, display string: :0
00:00:00.998309 Using XKB for keycode to scan code conversion
00:00:00.999889 SUP: RTLdrGetBits failed for VMMR0.r0 
(/usr/lib/virtualbox/VMMR0.r0). rc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED
00:00:00.999919 PDMLdr: pdmR3LoadR0U: pszName="VMMR0.r0" 
rc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED szErr="RTLdrGetBits failed"
00:00:00.999941 VMSetError: 
/build/virtualbox-5ojW2E/virtualbox-5.2.14-dfsg/src/VBox/VMM/VMMR3/PDMLdr.cpp(731)
 int pdmR3LoadR0U(PUVM, const char*, const char*, const char*); 
rc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED
00:00:00.999944 VMSetError: Failed to load R0 module 
/usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed
00:00:00.999954 VMSetError: 
/build/virtualbox-5ojW2E/virtualbox-5.2.14-dfsg/src/VBox/VMM/VMMR3/VM.cpp(598) 
int vmR3CreateU(PUVM, uint32_t, PFNCFGMCONSTRUCTOR, void*); 
rc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED
00:00:00.999956 VMSetError: Failed to load VMMR0.r0
00:00:01.000033 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) 
aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} 
aText={Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits 
failed (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
00:00:01.000040 Failed to load VMMR0.r0 
(VERR_LDRELF_RELOCATION_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:00:01.001021 Console: Machine state changed to 'PoweredOff'
00:00:01.007998 GUI: 
UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 
0 work area is actually resized to: 0x0 x 3200x1732
00:00:01.008350 Power up failed (vrc=VERR_LDRELF_RELOCATION_NOT_SUPPORTED, 
rc=NS_ERROR_FAILURE (0X80004005))
00:00:01.509022 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest 
size-hint for screen 0 to 3180x1585
00:00:01.509084 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) 
aIID={76eed314-3c72-4bbb-95cf-5eb4947a4041} aComponent={DisplayWrap} aText={The 
console is not powered up}, preserve=false aResultDetail=0
00:00:01.509155 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest 
size-hint for screen 1 to 640x480
00:00:01.509175 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) 
aIID={76eed314-3c72-4bbb-95cf-5eb4947a4041} aComponent={DisplayWrap} aText={The 
console is not powered up}, preserve=false aResultDetail=0
00:00:01.509225 GUI: Aborting startup due to power up progress issue detected...
 
 
Volker
 
On Dienstag, 3. Juli 2018 10:54:27 CEST you wrote:
> 
> >I am affected by this bug too!
> >
> >
> >On Tue, 03 Jul 2018 10:08:05 +0200 Christian Marillat <maril...@free.fr> 
> >wrote:
> >
> > Hi,
> >
> 
> 
> and nobody is providing logs?
> 
> G.
> 

Reply via email to