00:00:00.062210 usbLibDevStrDrEntryGet: DeviceIoControl 1 fail winEr (31)
00:00:01.124794 VDInit finished
00:00:01.130773 Loading settings file "C:\Users\Kevin_000\VirtualBox VMs\Linux Mint 15\Linux Mint 15.vbox" with version "1.14-windows"
00:00:20.096920 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:00:20.560349 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:15:21.855327 USBPROXY usbLibDevStrDrEntryGet: DeviceIoControl 1 fail winEr (31)
00:34:08.449922 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Medium 'C:\Users\Kevin_000\VirtualBox VMs\Linux Mint 15\Linux Mint 15.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:34:13.484548 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={fafa4e17-1ee2-4905-a10e-fe7c18bf5554} aComponent={VirtualBox} aText={The object is not ready}, preserve=false
It looks like some kind of I/O device issue (mouse?).
Host specs:
Windows 8.1 Professional
Intel i7-4770
32GB RAM
Nvidia GTX 660
My guest setup:
12GB RAM allocated
25GB virtual disc
24MB video
3D Acceleration enabled
Very annoying because I need this to work so I can work.
I figure I should post more details since I haven't had a response yet.
One of the interesting/frustrating things is that whenever I try to install a 64-bit .iso, it tells me that VB is running on x86 architecture, even though Windows 8 is 64-bit. I've attached a screenshot showing Linux Mint 15 MATE giving me that error when attempting to boot the .iso in compatibility mode. Is this due to the Windows 8 desktop being an app/VM itself?
With the 32-bit version, I get a warning/error about some setting that should be changed in the BIOS. I've attached that screenshot as well.
And, I've attached the full log of the latest crash. Apparently I posted the wrong log info originally.
I do have Hyper-V installed on my machine, but there are no VMs running.
Also with hyper-v installed it's most likely taken over hardware virtualization in which case you cannot run 64 bit guests in VBox and for 32 bit case would fallback to software virtualization.
Also with hyper-v installed it's most likely taken over hardware virtualization in which case you cannot run 64 bit guests in VBox and for 32 bit case would fallback to software virtualization.
Is there a way around this, short of uninstalling Hyper-V?
Also with hyper-v installed it's most likely taken over hardware virtualization in which case you cannot run 64 bit guests in VBox and for 32 bit case would fallback to software virtualization.
Is there a way around this, short of uninstalling Hyper-V?
Try it. Verify if your VM starts with hardware virtualization. You should see a line "VMX enabled" or "SVM enabled". If you don't, the VM isn't using hardware virtualization.
No, we cannot do anything about it. You have to talk to Microsoft to change the behavior or hyper-v, if it is the case. Hardware virtualization was not designed by intel and amd to be shared, so once a hypervisor such as hyper-v takes it, no other hypervisor can use hardware virtualization on that CPU until hyper-v lets go of it.