I need to work as well with OpenStep and OS2 Warp 4, so I believe it is the same problem, as the boot floppies are needed somehow.
Any input is welcome.For OS/2 WARP v4, the boot floppy images are on the CD in a disk image format that VMware Fusion can handle (although IIRC, when I installed it I had to change their file extensions to .img to get VMware Fusion to give me the opportunity to open them).
OS/2 WARP v4 will install and run successfully in Fusion, but you should note a few things:
The base video drivers won't make full use of your Mac's display -- the best you'll get is 16 colour VGA. The SciTech SNAP graphics drivers will fix this, however SciTech stopped selling these drivers a year or so ago. Fortunately, when I e-mailed them about my lost key a few months back, they just sent me a new one with no questions asked.
You won't be able to install any fixpack after about FixPak12 or 13, as they'll cause the system to abend at boot time. Likewise, anything newer than OS/2 WARP v4 (such as OS/2 WARP Server for e-Business, the Merlin Convienence Packs, or the Aurora Convenience Packs (MCP/ACP)) won't be able to boot after the first stage of the install (these kernels don't get along with VMware at all).
After creating the VM (but before installing) you'll want to edit your VMX file and change the "guestOS" parameter to "os2experimental" (with the double quotes)
Software that relies on IBM's Feature Installer can be a real headache to install. I still haven't been able to get the 32-bit TCP/IP stack update to install from within Fusion (Feature Installer sucked even when it was brand new)
I've never been able to get any sound working in my OS/2 VM. I'm guessing that the open source ALSA drivers would fix this issue, however they require at least the FixPak 15 kernel or newer to function, and these kernels won't work with VMware at all (the OS will simply abend at boot time)
I couldn't get the e1000 ethernet drivers to properly work with VMware Fusion's emulated e1000 adapter, so I had to change the "ethernet0.virtualDev" parameter in the VMX file to "vlance" to get any sort of networking running. This will be a bit of a headache, as without any networking it will be very difficult to get all of the rest of the above-named updates onto your VM (as well as updating the web browser to Firefox, as WARP v4 came with IBM's WebExplorer and Netscape 4.04). The best way I found around this was to get a copy of mkisofs for the Mac, putting everything I wanted to send to my OS/2 VM into a sub-directory on my Mac's file system, and creating a CD disk image of the directory which I could mount under VMware to copy drivers and such over (remembering to include the latest version of InfoZIP for OS/2 so that archives could be extracted).
It can be quite a bit of work, and there will be some annoyances (such as a lack of VMware Tools, unless you can find someone who had the old OS/2 version of VMware who can send them to you (which I couldn't :P)), but once you get it working it should be fairly smooth sailing. The biggest two hiccoughs I have remaining for mine are the lack of audio, and the inability to run anything newer than about FP12 or 13 (I forget which), or anything that requires FP15 or newer to run.
I hope this helps!