[Solved] Virtual machine does not work after updating

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Piccinano
Posts: 4
Joined: 19. May 2017, 17:02

[Solved] Virtual machine does not work after updating

Post by Piccinano »

Hi,
i use VirtualBox v5.0.26-108824 in Windows 10 x64 with a XP Virtual Machine x32 and it work normaly.

Recently i updated to VirtualBox v5.1.22-115126-but it does not work any more the XP Virtual Machine.
Why this happen? How can i solve the problem?

Thanks.
Regards.

This are the log error file.

VBoxSVC.log

Code: Select all

VirtualBox COM Server 5.1.22 r115126 win.amd64 (Apr 28 2017 16:35:24) release log
00:00:00.003985 main     Log opened 2017-05-19T14:48:38.382466200Z
00:00:00.003985 main     Build Type: release
00:00:00.003985 main     OS Product: Windows 10
00:00:00.003985 main     OS Release: 10.0.14393
00:00:00.003985 main     OS Service Pack: 
00:00:00.035515 main     DMI Product Name: 550-122nl
00:00:00.040022 main     DMI Product Version: 1.04
00:00:00.040022 main     Host RAM: 8127MB (7.9GB) total, 5399MB (5.2GB) available
00:00:00.040022 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.040022 main     Process ID: 9672
00:00:00.040022 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.041503          VirtualBox: object creation starts
00:00:00.042005          Home directory: 'C:\Users\Peppe\.VirtualBox'
00:00:00.042005          Installed Drivers:
00:00:00.047519            C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 5.1.22.15126)
00:00:00.047519            C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.1.22.15126)
00:00:00.047519            C:\WINDOWS\System32\drivers\VBoxNetAdp6.sys (Version: 5.1.22.15126)
00:00:00.048021            C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.1.22.15126)
00:00:00.048021          Loading settings file "C:\Users\Peppe\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:00.137607          HostDnsMonitor: old information
00:00:00.137607            no server entries
00:00:00.137607            no domain set
00:00:00.137607            no search string entries
00:00:00.137607          HostDnsMonitor: new information
00:00:00.137607            server 1: 8.8.8.8
00:00:00.137607            server 2: 8.8.4.4
00:00:00.137607            domain: homenet.telecomitalia.it
00:00:00.137607            no search string entries
00:00:00.137607          HostDnsMonitorProxy::notify
00:00:00.170233          SUPR0QueryVTCaps -> VERR_VMX_MSR_ALL_VMX_DISABLED
00:00:00.170735          VD: VDInit finished
00:00:00.171236          Loading settings file "C:\Users\Peppe\VirtualBox VMs\Windows XP\Windows XP.vbox" with version "1.15-windows"
00:00:00.171737          VirtualBox: object created
00:00:06.385349          ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={edba9d10-45d8-b440-1712-46ac0c9bc4c5} aComponent={ExtPackManagerWrap} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false aResultDetail=0
00:00:06.579300          ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={b2547866-a0a1-4391-8b86-6952d82efaa0} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:02:41.127497 main     VirtualBox: object deletion starts
00:02:41.127497 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'F:\Windows XP.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:02:41.130005 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:02:41.130005 main     VirtualBox: object deleted
selectorwindow.log

Code: Select all

VirtualBox GUI VM Selector Window 5.1.22 r115126 win.amd64 (Apr 28 2017 16:35:24) release log
00:00:00.268911 Log opened 2017-05-19T14:48:38.560747800Z
00:00:00.268911 Build Type: release
00:00:00.268911 OS Product: Windows 10
00:00:00.268911 OS Release: 10.0.14393
00:00:00.268911 OS Service Pack: 
00:00:00.274936 DMI Product Name: 550-122nl
00:00:00.276933 DMI Product Version: 1.04
00:00:00.276933 Host RAM: 8127MB (7.9GB) total, 5389MB (5.2GB) available
00:00:00.276933 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:00.276933 Process ID: 6160
00:00:00.276933 Package type: WINDOWS_64BITS_GENERIC
00:00:00.276933 Qt version: 5.6.2
00:00:00.283449 GUI: UIMediumEnumerator: Medium-enumeration started...
00:00:00.354145 GUI: UIMediumEnumerator: Medium-enumeration finished!
Last edited by mpack on 22. May 2017, 12:32, edited 2 times in total.
Reason: Enclosed the information in [code] tag for better readability
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Virtual machine does not work after updating

Post by mpack »

To diagnose VM problems we need the VM log. The logs you provided are not relevant.

With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.
Piccinano
Posts: 4
Joined: 19. May 2017, 17:02

Re: Virtual machine does not work after updating

Post by Piccinano »

Thanks to reply.
I attach the VBox.log.
Attachments
VBox.log.rar
(40.32 KiB) Downloaded 44 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Virtual machine does not work after updating

Post by mpack »

Try fixing this
VBox.log wrote: 00:00:01.425203 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes
and then lets see where we are.


Separate problem - you have at least one non-fatal hardening issue:
VBox.log wrote: 00:00:07.918006 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=1024 \Device\HarddiskVolume3\Program Files (x86)\ScrollNavigator\ScrollNavigator64.dll
00:00:07.918071 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ScrollNavigator\ScrollNavigator64.dll' (C:\Program Files (x86)\ScrollNavigator\ScrollNavigator64.dll): rcNt=0xc0000190
I also notice that the WindowsXP.vdi file is outside the VM folder, in fact its is the root folder of what is probably an external drive. This is not usually a good setup.
Piccinano
Posts: 4
Joined: 19. May 2017, 17:02

Re: Virtual machine does not work after updating

Post by Piccinano »

mpack wrote:Try fixing this
VBox.log wrote: 00:00:01.425203 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes
and then lets see where we are.
I will enable the VT-x in the BIOS.

A question: The VirtualBox version 5.0.26-108824 does not use VT-x ? This version opens the virtual machine normaly.
mpack wrote:Separate problem - you have at least one non-fatal hardening issue:
VBox.log wrote: 00:00:07.918006 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=1024 \Device\HarddiskVolume3\Program Files (x86)\ScrollNavigator\ScrollNavigator64.dll
00:00:07.918071 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ScrollNavigator\ScrollNavigator64.dll' (C:\Program Files (x86)\ScrollNavigator\ScrollNavigator64.dll): rcNt=0xc0000190
I do not understand this issue. What does it mean?
mpack wrote:I also notice that the WindowsXP.vdi file is outside the VM folder, in fact its is the root folder of what is probably an external drive. This is not usually a good setup.
Yes, the WindowsXP.vdi is a USB drive as i move it in another PC.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Virtual machine does not work after updating

Post by mpack »

Piccinano wrote: A question: The VirtualBox version 5.0.26-108824 does not use VT-x ? This version opens the virtual machine normaly.
Your VM is configured to use VT-x, and indeed this is usually the best option. Telling VirtualBox to use a feature which isn't available is a problem in some versions sometimes. Let's find out if that is the case here.
Piccinano wrote:
mpack wrote:Separate problem - you have at least one non-fatal hardening issue:
I do not understand this issue. What does it mean?
It means that you have software on your host which is trying to inject an unsigned DLL into the VirtualBox execution space. For you this is not fatal, but you may want to check out the culprits (ScrollNavigator) anyway, and find out why it behaves this way. Also see FAQ: Diagnosing VirtualBox Hardening Issues.
Piccinano
Posts: 4
Joined: 19. May 2017, 17:02

Re: Virtual machine does not work after updating

Post by Piccinano »

Hi mpak,
i enabled VT-x in the BIOS and now all is OK.
Thanks.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: [Solved] Virtual machine does not work after updating

Post by mpack »

Thanks for reporting back.
Post Reply