virtualbox.org

Hi everyone,

I have been using VBOX on my windows box for about 5 years and never had any problem whatsoever. My VBOX was set to check updates weekly and I always installed updates regularly. I did some housekeeping lately and deleted (from the disk, not via the VB interface)old VMs and old virtual disks that I thought were obsolete but I think I've made a mistake because some devices were still attached to machines, and those machines had different snapshots, some including mountpoints on virtual disks I just deleted on the windows host. Anyway, I wasn't aware of that because VBOX was working absolutely fine. It's only when when I ran the last update and upgraded to v 4.3.2.2 that VBOX refused to start any VM and has been crashing every time I attempted to start a guest machine since.

I've attached the startup.log file of an old windows XP machine for reference. I suspect that VBOX is confused now that I have forcibly deleted virtual machines and virtual disks straight from the hard disk ? Is there any way I can force refresh VBOX to acknowledge the machines/disks I have manually deleted ? I am not able to get rid of the virtual disks via the interface either (buttons are greyed out) even though VBOX is apparently aware that the files are not on the host machine anymore.

I tried to download older versions of VBOX, uninstalled (4.3.2.2) and tried again, but no luck. I even tried to go through the upgrading process again but still no luck.


My physical host information :

Manufacturer : GenuineIntel
NumberOfCores : 4
NumberOfLogicalProcessors : 8
ProcessorId : BFEBFBFF000106A5
ProcessorType : 3
Caption : Intel64 Family 6 Model 26 Stepping 5
Description : Intel64 Family 6 Model 26 Stepping 5
InstallDate :
Name : Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz

Caption : Microsoft Windows 7 Home Premium
Description :
InstallDate : 10/05/2010 15:36:28
Name : Microsoft Windows 7 Home Premium |C:\Windows|\Device\Harddisk0\Partition2

Distributed : False
FreePhysicalMemory : 1924852
FreeSpaceInPagingFiles : 6060540
FreeVirtualMemory : 6802676
LastBootUpTime : 20/02/2015 09:29:16
LocalDateTime : 21/02/2015 00:19:55
MaxNumberOfProcesses : 4294967295
MaxProcessMemorySize : 8589934464
NumberOfProcesses : 99
NumberOfUsers : 3
OSType : 18
SizeStoredInPagingFiles : 6281336
TotalSwapSpaceSize :
TotalVirtualMemorySize : 12560816
TotalVisibleMemorySize : 6281336
Version : 6.1.7601
BootDevice : \Device\HarddiskVolume1
BuildNumber : 7601
BuildType : Multiprocessor Free
CodeSet : 1252
CountryCode : 44
CSDVersion : Service Pack 1
DataExecutionPrevention_32BitApplications : True
DataExecutionPrevention_Available : True
DataExecutionPrevention_Drivers : True
DataExecutionPrevention_SupportPolicy : 2
Debug : False
EncryptionLevel : 256
ForegroundApplicationBoost : 2
LargeSystemCache :
Locale : 0809
Manufacturer : Microsoft Corporation
MUILanguages : {en-US}
OperatingSystemSKU : 3
OSArchitecture : 64-bit
OSLanguage : 1033
OSProductSuite : 768
Primary : True
ProductType : 1
ServicePackMajorVersion : 1
ServicePackMinorVersion : 0


My guests are all linux machines, and one windows XP box. None of them can start and they all crash with pretty much the same message in the VboxStartup.log file.

I am completely stuck at this point, any help or suggestion would be highly appreciated.

Thanks very much!

There is no attached file

Ah ok . I tried to attach it again but I had an error message I probably didn't notice the first time: The file is too big, maximum allowed size is 128 KiB.

Here's a pastebin version : http://pastebin.com/7bb3CS6k

Thank you!

Just compress it as zip. That log is not that interesting tho, at least nothing interesting in it. Please attach the zipped VBox.log file.

No problem, here is the file requested. Only 86k so no need to zip it.

Thanks for your help !

I'm having a similar problem since the latest upgrade. My VirtualBox app won't start at all. So log files aren't getting created to send. Tried the same uninstall & back to a previous version. No luck getting it to open. Now it doesn’t work at all. Attached is a screenshot of the error I receive when trying to open VirtualBox. Open for suggestions?
Thanks'

Hello everyone,

No luck with my log file I guess ?

I'll wait for the next upgrade, hoping it will fix the current issue.

Thanks