Comments on: Re-visiting VM/386

By: neozeed

neozeed — Sat, 01 Jul 2023 22:41:02 +0000

In reply to Derek Peschel. Cool, thanks!

By: Derek Peschel

Derek Peschel — Sat, 01 Jul 2023 22:26:13 +0000

Microsystems Journal also reviewed VM/386 in July 1988:
http://bitsavers.org/magazines/Microsystems_Journal/v04n07.pdf
Page 60 of the PDF, page 58 printed on the page.

By: neozeed

neozeed — Thu, 22 Jun 2023 22:34:08 +0000

In reply to Mark.

I use a bunch of versions. And yes 0.9 is a great go-to version.

version 8.0 can’t even load it.

qemu-system-i386.exe -M isapc -vga std -hda vm386.vmdk -m 8 -cpu 486

By: Mark

Mark — Thu, 22 Jun 2023 21:52:09 +0000

In reply to neozeed. What was your QEMU command line and version? Presumably you're still not using 0.9? :)

By: JQW

JQW — Wed, 14 Jun 2023 21:23:18 +0000

I remember playing with something like this (I forget what) back in about 1990, and having success, but I couldn’t get it to run two instances of the same networked terminal app, as that was what this software had been acquired for.

It didn’t work as the terminal service wasn’t coded to handle two simultaneous sessions from the same PC network address.

By: neozeed

neozeed — Wed, 14 Jun 2023 07:17:19 +0000

I suspect it’s something in the main BIOS

By: raijinkai

raijinkai — Wed, 14 Jun 2023 00:37:55 +0000

In reply to raijinkai. ED: I still wonder what is preventing it to work in QEMU...

By: raijinkai

raijinkai — Wed, 14 Jun 2023 00:35:49 +0000

I would say VM/386 was already what we call now “hypervisor” in all the sense of the word. If only VM/386 had a data exchange API, it would have been the ESXi of the last 80’s/90’s…
Also, the way it works… Is pretty similar how Windows/386 does. Device drivers/video grabbers, hardware abstractions, the use of Intel VM86 extensions…