Page 1 of 1

guru meditation, any ideas?

Posted: 22. Apr 2014, 17:30
by PrinceofSpace
Howdy folks. I've used virtualbox with great success on my HP 6470b. I had to do some config, but it was easy.

Now I'm using an HP9470b, and the VM crashes booting from the same winPE that works fine on the 6470b. It loads from the winpe image, hits the splash screen, shows the graphic, then crashes. Your PC needs to restart. Guru meditation.

I've done all of the normal troubleshooting that worked on the 6470b, such as confirming the bios settings, etc, etc. I've looked at the logs and googled the errors and I still am not getting anywhere.

My vbox.log file was too big, I had to split it into two files in order to attach it.

Does anyone have any ideas?

Re: guru meditation, any ideas?

Posted: 22. Apr 2014, 17:33
by loukingjr
next time you can just compress the log file.

Re: guru meditation, any ideas?

Posted: 22. Apr 2014, 18:38
by noteirak
Change your guest type to Windows 8 or 8.1

Re: guru meditation, any ideas?

Posted: 22. Apr 2014, 19:28
by PrinceofSpace
noteirak wrote:Change your guest type to Windows 8 or 8.1
Ah of course, we upgraded SCCM2012 to R2 and that included winPE being upgradd to the 8 version.

When I set the VM to windows 8, it gets past the last error, but now it gives a frowny face and says bad_system_config_info.

So thanks, you solved my problem, but I've hit another. Even though it's not virtualbox related, feel free to offer suggestions if you have them on this next issue :)

Re: guru meditation, any ideas?

Posted: 22. Apr 2014, 19:34
by PrinceofSpace
PrinceofSpace wrote:
noteirak wrote:Change your guest type to Windows 8 or 8.1
Ah of course, we upgraded SCCM2012 to R2 and that included winPE being upgradd to the 8 version.

When I set the VM to windows 8, it gets past the last error, but now it gives a frowny face and says bad_system_config_info.

So thanks, you solved my problem, but I've hit another. Even though it's not virtualbox related, feel free to offer suggestions if you have them on this next issue :)
Aha, oops, I turned the RAM down to 512 during troubleshooting on the first issue. Now I'm all set.

Thanks again for the help.