Hello,
Just started trying to use Vbox last night. At some point I had issues because I clicked something I shouldnt have regarding the mouse. I lost any ability to use the mouse in the vm. That led to doing a less that graceful shutdown of the entire host, out of frustration. After that it wouldnt come up so I figured I would just delete the vm, and create a new one in the morning.
So I did, and the VM wont even start with the original .iso to do a new install. I named it something totally different. Same thing... I uninstalled vbox and changed the install path slightly thinking, my god, if this doesnt fix it, I must have completely ruined my host machine. (drama for effect).... Anyway, the logs are attached, I have no idea other than a hard power off what I did wrong. Since we all know hard shutdowns are inevitable, I cant imagine that is the root cause. Not that I want to make a habbit of shutting my vm's down this way of course.
The logs are attached. I have a sneaking suspicion being in support myself that I am not the first one to run into this. If someone can fast track me to the fix, I would really appreciate it! A 44 yr. old trying to setup an Ubuntu based Gmod server for my 14 yr. old boy who is really into it.... have mercy please!
Critical error - Win 8.1 host w/Ubuntu latest guest AMD64
Critical error - Win 8.1 host w/Ubuntu latest guest AMD64
- Attachments
-
- Screenshot of crash
- vbox_crash.png (35.02 KiB) Viewed 571 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Critical error - Win 8.1 host w/Ubuntu latest guest AMD6
I'm afraid you've fallen foul of a known issue with the new v5 release :-
Previous discussion of this issue here:-
viewtopic.php?f=6&t=68975
p.s. Your issue with the mouse is almost certainly because you configured the VM to steal it from the host. Disable USB support in the VM settings, or configure any USB filters so that they can't match an unintended device.
Try reducing the number of CPU cores in the VM settings to 1.VBox.log wrote: 00:00:11.432167 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:11.432169 !!
00:00:11.432169 !! Guru Meditation -3743 (VERR_SUPDRV_TSC_DELTA_MEASUREMENT_FAILED)
00:00:11.432194 !!
00:00:11.432224 !!
00:00:11.432224 !! {mappings, <NULL>}
00:00:11.432225 !!
Previous discussion of this issue here:-
viewtopic.php?f=6&t=68975
p.s. Your issue with the mouse is almost certainly because you configured the VM to steal it from the host. Disable USB support in the VM settings, or configure any USB filters so that they can't match an unintended device.