![]() I have tested on Vmware Workstation, VirtualBox, QEMU with KVM, standalone QEMU with Ubuntu as the guest OS. I'm mostly interested in Linux, but if it also works for other unices that's nice. What's the easiest way of determining what virtualization technology this system may be a guest of? I'd appreciate if proposals mentioned which technologies (including bare hardware) can be conclusively detected and which can be conclusively eliminated. Ideally, it would be something like lshw: an easily-installable (if not preinstalled) command that does the poking around and prints out relevant information. So I have to convey instructions like “copy-paste this command” and not “poke around /proc somewhere”. More precisely, I'm helping someone diagnose the issue, I'm not sitting at the helm. ![]() This isn't a hostile environment: I'm not trying to work against a VM that is trying to disguise itself, I'm diagnosing a flaky server that I know little about. I want to determine what kind of virtualization technology it runs on, if any (VMWare, VirtualBox, KVM, OpenVZ, Xen, ). The only problem is that when the MS-DOS portion of setup completes, I end up with a blinking cursor in a black background and Windows NT setup does not proceed any further.Īs for fixing the CD swapping problem in Windows NT 3.1, good for you.I have command line access to a Linux machine which may or may not be virtualized. But nevertheless, Windows NT 3.51 works well with SCSI support as apposed to IDE which is limited to 504 MB.įor me, as for installing Windows NT 3.51, I had to install MS-DOS 6.22 first, copy the contents of the \I386 folder (from the Windows NT 3.51 CD) and type in WINNT /B to setup Windows NT 3.51 from the hard drive with no CD-ROM support. I'm not good at programming and I believe that I might screw something up in any even if I compile my own revision of PCem. (mainly Aha-154x ones, which is what VirtualBox also emulates and needed by NT 3.1 for the best CDROM support).Īlso, NT 3.51 installs fine here on PCem. I'm interested too in SCSI emulation, I hope you can add it properly ppgrainbow ? What do you think? I got SCSI and MS-DOS support working in VMware Player, VirtualBox and at one time in later releases of QEMU. I'm wondering if it would be possible to add SCSI support for up to 8 SCSI hard disks per controller or not. SCSI hard disks with either BusLogic or LSI option ROMs are a good way to overcome the 504 MB limit found on pre-August 1994 BIOSes in which it couldn't support IDE hard disks above 504 MB without the risk of data corruption. Windows NT would work best if it has SCSI hard disk support. ?Įdit: For some reason, the Qemu/Bochs workaround didn't work still getting a blinking cursor here and I'm thinking that it couldn't even accept a IDE hard disk that had 1,024 or more cylinders on the boot drive.but I could be wrong. If I found any success in getting Windows NT 3.51 working, I'll let you know. While Windows NT 3.51 cannot be natively installed inside PCem, I believe that I will be doing a temporary workaround to install Windows NT 3.51 under Bochs or a old version of Qemu with no networking capabilities and standard VGA support as the current release of PCem has no networking capabilities at this time. With that fixed NT 3.51 mostly works, some issues during installation but that might simply be a problem with my copy. There's also a bug in the IDE emulation (most register writes should affect both drives, not just the one currently selected).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |