Re: Error starting Virtual machines on virtualbox - Yosemite
Posted: 22. Jan 2015, 16:35
It shouldn't make his guests crash although one never knows I suppose.
End user forums for VirtualBox
https://forums.virtualbox.org/
I'm also thinking this, there's not much to test at this point. Do we have a " Known Imcompatible apps" list or something like that?loukingjr wrote:My thoughts are at this point, there is something wrong with the sources you are trying to use to install guests or, some third party app is conflicting with VirtualBox. Maybe someone else knows.
It's not your Mac.LinkRaider wrote:I'm also thinking this, there's not much to test at this point. Do we have a " Known Imcompatible apps" list or something like that?loukingjr wrote:My thoughts are at this point, there is something wrong with the sources you are trying to use to install guests or, some third party app is conflicting with VirtualBox. Maybe someone else knows.
Also, I have my mac for less than 30 days, so if nothing else works I'll just return it.
Thanks for all the help guys, I really appreciate it
Since you had Tuxera and OSXFuse installed I have no idea what you may or may not have done to your Mac with them. You've left out some important info it seems and at this point I don't know what to tell you. A clean install of OSX is an option although I don't know if it's necessary.LinkRaider wrote: Ok so I uninstalled the Tuxera and Fuse (softwares that could cause this behaviour since they also work with the machine disk) but the problem persists.
I don't know what else to check. Is formating the mac an option?
Satisfaction policy mate, if I'm not happy I can return it within 30 daysloukingjr wrote:I wouldn't count on getting a new one since there is probably nothing wrong with your current one.
You could be right to some extent but I've reinstalled my mac (deleted both system partition and user data, started from the scratch with internet recovery) and guess what... same behaviour on both Virtualbox and Fusion. Don't you think it's weird? :ploukingjr wrote:Sounds more like a "I didn't know what I was doing and screwed something up so I want a new one" policy.
No, that's the thing, everything else works like a charm.loukingjr wrote:::smh:: Forget VirtualBox or VMWare Fusion for the moment. Are you having any issues at all running other applications? If not, it's not a hardware problem. There is no "hardware" that VirtualBox uses on Macs that any other program doesn't use. The fact is, there is a 99.9999% chance you are setting up the guests incorrectly or your sources are corrupt.
I see your point but the problem here is that "I've seen other cars, and they don't have a problem on that road. And this is no flat tire, I can't cross the damn road unlike the others". That's my point.loukingjr wrote:An analogy would be, " I bought a new car. I can drive it over dozens of roads with no problem but when I drive down one particular road I get a flat tire. Therefor there is something wrong with my car.
No, that guest doesn't run either. I've also tried those .iso files on a Windows Virtualbox and they all boot up successfully.loukingjr wrote:Does your !E10-Win7 guest run because it seems to be shutdown correctly unlike the one with the guru meditation error.
If it doesn't run correctly how did it shutdown correctly?LinkRaider wrote:No, that guest doesn't run either. I've also tried those .iso files on a Windows Virtualbox and they all boot up successfully.loukingjr wrote:Does your !E10-Win7 guest run because it seems to be shutdown correctly unlike the one with the guru meditation error.
Perhaps it's the driver.I see your point but the problem here is that "I've seen other cars, and they don't have a problem on that road. And this is no flat tire, I can't cross the damn road unlike the others". That's my point.
I'll have to get a new log later, but on VmFusion it just shows a black screen and it stops there. On Virtualbox I honestly don't remember, I'll test it again later.loukingjr wrote:If it doesn't run correctly how did it shutdown correctly?
I hope it is, mate.loukingjr wrote:Perhaps it's the driver.