Opened 8 years ago
Last modified 8 years ago
#16254 new defect
VxWorks guest broken on v5.X
| Reported by: | pcabral | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.10 |
| Keywords: | vxworks | Cc: | |
| Guest type: | other | Host type: | Mac OS X |
Description
Upgraded from VirtualBox v4.3.40 to v5.1.10 on OS X host and I am no longer able to run my VxWorks simulators. The problem seems to be related to the network interface, when I disable the network interface the virtual machine behaves differently (hangs versus crashing), otherwise the virtual machine crashes. I’ve attached log files for each of the versions of VirtualBox, just in case it helps in debugging why one is working and the other is not.
P.S. There are no issues when running the VxWorks simulators on VirtualBox v5.1.10 on both Windows and Linux hosts.
Attachments (1)
Change History (5)
by , 8 years ago
| Attachment: | VxWorks-Logs.zip added |
|---|
comment:2 by , 8 years ago
Just to help the search engines and future searchers, the Guru Meditation in the log is:
Guru Meditation -5390 (VERR_IEM_ASPECT_NOT_IMPLEMENTED)
comment:3 by , 8 years ago
As a possible workaround, try select an older CPU profile for the VM, like the "Intel Xeon X5482 3.20GHz" one:
VBoxManage modifyvm VXWORKS --cpu-profile "Intel Xeon X5482 3.20GHz"
comment:4 by , 8 years ago
@bird
The documentation does not mention anything besides [--cpu-profile "host|Intel 80[86|286|386]"].
The only mention of "Intel Xeon X5482 3.20GHz" that I can see is in '/src/VBox/VMM/VMMR3/cpus/Intel_Xeon_X5482_3_20GHz.h'. Do I have it correctly that any of the files in that folder are also potential candidates for the 'VBoxManage modifyvm --cpu-profile' command? Because it could be really helpful compared to using the 'VBoxManage modifyvm [--cpuidset <leaf> <eax> <ebx> <ecx> <edx>]' command.
PS1. That's some low-level stuff in there. And I just learned that there ever was a 80186!
Contains guest logs for working and non-working instances.