Page 1 of 1

XENIX TSS U_trap error

Posted: 30. Dec 2013, 01:59
by BXDOBS
I have an Acronis TID file from a working SCO Xenix V System that I loaded in to VMware Player using the P2V process VMware provides ... this created a VMDX file which is supposedly supported by VIRTUALBOX.

At issue:

Xenix loads and runs it's version of X Windows in VMware Player 4.x ... problem is it won't give me a working network connection (haven't tried VM's current versions yet) ... So ... I thought I would give Virtual Box a try first

When I attempt to run this VMDX file in VirtualBox, Xenix gets to the point where it is attempting to switch in to X windows but then goes in to an error loop: Warning U_TRAP invalid TSS 000000000A

There is an incident in the Oracle Tickets suggesting TSS switching has been corrected?

I have tried various changes to the VM configuration but it keeps coming up with the same result

Re: XENIX TSS U_trap error

Posted: 30. Dec 2013, 11:38
by mpack
Yes, VirtualBox supports the VMDK format (there's no such thing as VMDX, as far as I'm aware). However, that's like saying that your PC supports SATA. It doesn't mean that the PC can run whatever software it finds on a SATA drive.

Getting the VM to work is usually a matter of getting the VM recipe as near as possible to its last working state. And it better be right since I assume this Xenix image is ancient and far predates "plug and play". Unfortunately I have no way to know what hardware your Xenix image expects. If you had it working in VMWare then a good start is trying to reproduce that - though having said that, if you couldn't get networking to work in VMWare then you probably can't do it in VirtualBox either: the problem will be what NICs are supported, and the network config.

Re: XENIX TSS U_trap error

Posted: 30. Dec 2013, 12:34
by michaln
If you have a reproducible problem, please create a bug ticket. Don't forget to include all relevant information, starting with VBox.log.

That said, "SCO Xenix V System" is not on the supported guest OS list, and neither is SCO Xenix System V. Given that we probably cannot legally obtain any version of this OS in this age, fixing anything will be difficult.