Early VMware Betas on a Pentium II: When Windows NT Ran Inside SuSE

Fri, 03 Apr 2009 00:00:00 +0000

Some technical memories do not fade because they were elegant. They stay because they felt impossible at the time.

For me, one of those moments happened on a trusty Intel Pentium II at 350 MHz: early VMware beta builds on SuSE Linux, with Windows NT running inside a window. Today this sounds normal enough that younger admins shrug. Back then it felt like seeing tomorrow leak through a crack in the wall.

This is not a benchmark article. This is a field note from the era when virtualization moved from “weird demo trick” to “serious operational tool,” one late-night experiment at a time.

Before virtualization felt practical

In the 90s and very early 2000s, common service strategy for small teams was straightforward:

one service, one box, if possible
maybe two services per box if you trusted your luck
“testing” often meant touching production carefully and hoping rollback was simple

Hardware was expensive relative to team budgets, and machine diversity created endless compatibility work. If you needed a Windows-specific utility and your core ops stack was Linux, you either kept a separate Windows machine around or you dual-booted and lost rhythm every time.

Dual-boot is not just inconvenience. It is context-switch tax on engineering.

The first time NT booted inside Linux

The first successful NT boot inside that SuSE host is still vivid:

CPU fan louder than it should be
CRT humming
disk LED flickering in hard, irregular bursts
my own disbelief sitting somewhere between curiosity and panic

I remember thinking, “This should not work this smoothly on this hardware.”

Was it fast? Not by modern standards. Was it usable? Surprisingly yes for admin tasks, compatibility checks, and software validation that previously required physical machine juggling.

The emotional impact mattered. You could feel a new operations model arriving:

isolate legacy dependencies
test risky changes safely
snapshot-like rollback mindset
consolidate lightly loaded services

A new infrastructure model suddenly had a shape.

Why this mattered to Linux-first geeks

For Linux operators in that 1995-2010 transition, virtualization solved very specific pain:

keep Linux as host control plane
run Windows-only dependencies without dedicating separate hardware
reduce “special snowflake server” count
rehearse migrations without touching production first

This was not ideology. It was practical engineering under budget pressure.

The machine constraints made us better operators

Running early virtualization on a Pentium II/350 forced discipline:

memory was finite enough to hurt
disk throughput was visibly limited
poor guest tuning punished host responsiveness immediately

You learned resource budgeting viscerally:

host must remain healthy first
guest allocation must reflect actual workload
disk layout and swap behavior decide stability
“just add RAM” is not always available

These constraints built habits that still pay off on modern hosts.

Early host setup principles that worked

On these older Linux hosts, stability came from a few rules:

keep host services minimal
reserve memory for host operations explicitly
use predictable storage paths for VM images
separate experimental guests from critical data volumes
monitor load and I/O wait, not just CPU percentage

A conceptual host prep checklist looked like:

[ ] host kernel and modules known-stable for your VMware beta build
[ ] enough free RAM after host baseline services start
[ ] dedicated VM image directory with free-space headroom
[ ] swap configured, but not treated as performance strategy
[ ] console access path tested before heavy experimentation

None of this is glamorous. All of it prevents lockups and bad nights.

The NT guest use cases that justified the effort

In our environment, Windows NT guests were not vanity installs. They handled concrete compatibility needs:

testing line-of-business tools that had no Linux equivalent
validating file/print behavior before mixed-network cutovers
running legacy admin utilities during migration projects
reproducing customer-side issues in a controlled sandbox

This meant less dependence on rare physical machines and fewer risky “test in production” moments.

Performance truth: no miracles, but enough value

Let us be honest about the period hardware:

boot times were not instant
disk-heavy operations could stall
GUI smoothness depended on careful expectation management

Yet the value proposition still won because the alternative was worse:

more hardware to maintain
slower testing loops
higher migration risk

In operations, “fast enough with isolation” often beats “native speed with fragile process.”

Snapshot mindset before snapshots were routine

Even with primitive feature sets, virtualization changes how we think about change risk:

make copy/backup before risky config change
test patch path in guest clone first when feasible
treat guest image as recoverable artifact, not sacred snowflake

This was the beginning of infrastructure reproducibility culture for many small teams.

You can draw a straight line from these habits to modern immutable infrastructure ideas.

Incident story: the host freeze that taught priority order

One weekend we overcommitted memory to a guest while also running heavy host-side file operations. Result:

host responsiveness collapsed
guest became unusable
remote admin path lagged dangerously

We recovered without data loss, but it changed policy immediately:

host reserve memory threshold documented and enforced
guest profile templates by workload class
heavy guest jobs scheduled off peak
emergency console procedure printed and tested

Virtualization did not remove operations discipline. It demanded better discipline.

Why early VMware felt like “cool as hell”

The phrase is accurate. Seeing NT inside SuSE on that Pentium II was cool as hell.

But the deeper excitement was not novelty. It was leverage:

one host, multiple controlled contexts
faster validation cycles
safer migration experiments
better utilization of constrained hardware

It felt like getting extra machines without buying extra machines.

For small teams, that is strategic.

From experiment to policy

By the late 2000s, what began as experimentation became policy in many shops:

new service proposals evaluated for virtual deployment first
legacy service retention handled via contained guest strategy
test/staging environments built as guest clones where possible
consolidation planned with explicit failure-domain limits

The “limit” part matters. Over-consolidation creates giant blast radii. We learned to balance efficiency and fault isolation deliberately.

Linux host craftsmanship still mattered

Virtualization did not excuse sloppy host administration. It amplified host importance.

Host failures now impacted multiple services, so we tightened:

patch discipline with maintenance windows
storage reliability checks and backups
monitoring for host + guest layers
documented restart ordering

A clean host made virtualization feel magical. A messy host made virtualization feel cursed.

The migration connection

Virtualization became a bridge tool in service migrations:

run legacy app in guest while rewriting surrounding systems
test domain/auth changes against realistic guest snapshots
stage cutovers with rollback confidence

This reduced pressure for immediate rewrites and gave teams time to modernize interfaces safely.

In that sense, virtualization and migration strategy are the same conversation.

Economic impact for small teams

In budget-constrained environments, early virtualization offered:

hardware consolidation
lower power/space overhead
faster provisioning for test scenarios
reduced dependency on old physical hardware

It was not “free.” It was cheaper than the alternative while improving flexibility.

That is a rare combination.

Lessons that remain true in 2009

Writing this in 2009, with virtualization now far less exotic, the lessons from that Pentium II era remain useful:

constrain resource overcommit with explicit policy
protect host health before guest convenience
treat VM images as operational artifacts
document recovery paths for host and guests
use virtualization to reduce migration risk, not to hide poor architecture

The tools got better. The principles did not change.

A practical starter checklist

If you are adopting virtualization in a small Linux shop now:

define host resource reserve policy
classify guest workloads by criticality
put VM storage on monitored, backed-up volumes
script basic guest lifecycle tasks
test host failure and guest recovery path quarterly
keep one plain-text architecture map updated

Do this and virtualization becomes boringly useful, which is exactly what operations should aim for.

A note on nostalgia versus engineering value

It is easy to romanticize that era, but the useful takeaway is not nostalgia. The useful takeaway is method: use constraints to sharpen design, use isolation to reduce risk, and use repeatable host hygiene to make experimental technology production-safe.

If virtualization teaches nothing else, it teaches this: clever demos are optional, operational clarity is mandatory.

Closing memory

I still remember that Pentium II tower: beige case, 350 MHz label, fan noise, and the first moment NT desktop appeared inside a Linux window.

It looked like a trick.
It became a method.

And for many of us who lived through the 90s-to-internet transition, that method made the next decade possible.

Vmware on TurboVision