VMware Communities
HubertM
Contributor
Contributor
Jump to solution

dying XPpro VM

Hi there,

first I must state I'am (brand)new on my MacBook 2GHz/512Mb.

For several obvious resons I want to run Windows applications.

Wrote myself in the Fusion family community, downloaded the beta version and GO ! at least that what I thought.

Got Fusion installed, at first the early version 32652.dmg.

After the recommendation mail about the data loss defect installed the latest (33141.dmg) version.

Then got the Windows XP Pro cd in the drive, created a New Virtual Machine, WXPpro/disk:8GB/1 proc/mem:256MB, and installed WXPpro.

The installation goes well, it's slow, everything else responding on the mac is also slow, but hence it's only 512MB I've got.

I managed to get the VMware tools installed in the VM.

Then tried to get windows update to install some of the several hundred patches.

And now it still in the process of installing update 1 of 3.

Screen is frozen, mouse is not responding, the time (right lower corner) is 45 min. ago, so not getting updated. I can't close Fusion, everything else is responding slow on the mac.

I can start the activity monitor, both cpu's are doing almost nothing !! inactive is around 98%.

Bottomline question, why is my VM starting of good and along the way dying in my arms.

Hints tips clues are welcome.

BTW awsome demo @VMworld by Jenny & Regis, the only time there was so much clapping and cheering in the room.

Regards,

Hubert

Reply
0 Kudos
1 Solution

Accepted Solutions
bgertzfield
Commander
Commander
Jump to solution

Micah mentioned the other thread. You should add:

sched.mem.pshare.enable = "FALSE"

to your .vmx file to work around a separate bug. Turn this off when you upgrade to the next beta, as the bug has been fixed.

I'll request that this be added to the release notes.

View solution in original post

Reply
0 Kudos
4 Replies
admin
Immortal
Immortal
Jump to solution

I wouldn't expect the performance of a 256MB VM on a 512MB OS X host to ever be great, but the problem is likely being exacerbated by a known bug. See the "Memory usage" thread in this forum.

HubertM
Contributor
Contributor
Jump to solution

thanks Micah,

got the message, need to go shopping for @t least 1GB of memory.

edited the .vmx file, tuned down the memsize = "256" to "128"

everything is much more responsive, even the WinXPpro VM !!

wired mem on ~326MB, active ~119MB and free ~6MB.

the win update process is now running at patch 32 of 64 and counting... yeah !

BR,

Hubert

Reply
0 Kudos
bgertzfield
Commander
Commander
Jump to solution

Micah mentioned the other thread. You should add:

sched.mem.pshare.enable = "FALSE"

to your .vmx file to work around a separate bug. Turn this off when you upgrade to the next beta, as the bug has been fixed.

I'll request that this be added to the release notes.

Reply
0 Kudos
HubertM
Contributor
Contributor
Jump to solution

yeah this really does the trick.

real good response now.

thanks Ben,

now going for the application install.

Reply
0 Kudos