PXE boot critical error

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
CnElis
Posts: 1
Joined: 6. Mar 2014, 12:06

PXE boot critical error

Post by CnElis »

Hello !

I use max osx 10.9 macbook air

Can anybody help a little. I try to run pxe boot on virtualbox. Everything goes well and it loads up but then it chrashes before i get to setup. It tells me critical error (error code 0x000000C4).
I downloaded the extencion pac and i set up the virtualmachine to windows 7 64bit. Under boot order i used network and network adapter attached to :bridged adapter. Adapter type pcnet-fast III (am79c973). If more info needed then ask.
I don't think there is something wrong with server side cause without virtualbox on emty machine it works well (i have not tried on mac computer).
Attachments
VBox.png
VBox.png (11.03 KiB) Viewed 2397 times
gaiDNelson
Posts: 1
Joined: 5. May 2014, 20:53

Re: PXE boot critical error

Post by gaiDNelson »

CnEllis --- did you ever get resolution with this issue. I'm experiencing the same.
rpmurray
Volunteer
Posts: 918
Joined: 3. Mar 2009, 00:29
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 7, Mac OS X (various flavors)
Location: Between Heaven and Hell

Re: PXE boot critical error

Post by rpmurray »

I don't know if it will help, but on another topic the following was suggested to fix the error message:

Code: Select all

VBoxManage setextradata [vmname] VBoxInternal/CPUM/CMPXCHG16B 1
replacing [vmname] with the name of your VM (use double-quotes around it if there are spaces in the name)

or, if that doesn't work then this:

Code: Select all

VBoxManage setextradata global VBoxInternal/CPUM/CMPXCHG16B 1
You should issue the command while the VM is shut down.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: PXE boot critical error

Post by socratis »

rpmurray wrote:You should issue the command while the VM is shut down.
Just a small correction. You should issue the command while the VM and VirtualBox is shut down. At some point (4.3.x I believe) the VMs info is cached from the VBoxSvc process and it stays in memory, so any changes (from the command line) made to the VM while VBox is up and running will not get "registered".
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply