_ZAB_'s Posts

Have you solved the issue?
Any news here? The bug start to appear on 10.0.7 and it is the last version for 2003 server host. It worked just fine on previous versions.
An option WinNT4 works. Wonder why Other/Other64 is not working. It suppose to be used in this case.
It was solved by changing mem.hotadd option to FALSE in vmx file. Why on earth do you patch kernel on the fly to implement some questionable feature and not even test it?
I tested these guests: Windows 2003 Enterprise Edition 5.2 build 3790 Service Pack 2 installed. Windows 2003 R2 Enterprise Edition (can't see build number now) also with Service Pack 2 install... See more...
I tested these guests: Windows 2003 Enterprise Edition 5.2 build 3790 Service Pack 2 installed. Windows 2003 R2 Enterprise Edition (can't see build number now) also with Service Pack 2 installed. Enterprise edition or standard edition doesn't mean much because I tried to run it with /nopae switch and even /maxmem=2048 switch. It just crashes if a VM is set to more than 4GB even if kernel does not map all the ram. It worth noting that safe mode works just fine. VMware Tools setup crash on Win 2003 but installs fine on R2 version.
The host is Windows 7 x64 32 bit version of Win2003 guest hangs during boot if more than 4GB of RAM selected (even if PAE is off), kernel debug through serial port shows it break in ntkrpamp.exe... See more...
The host is Windows 7 x64 32 bit version of Win2003 guest hangs during boot if more than 4GB of RAM selected (even if PAE is off), kernel debug through serial port shows it break in ntkrpamp.exe (ie NT kernel). 32 bit version of Win2003 R2 guest boots but is very unstable (corrupt files and hangs spontaneously) 32 bit version of Win2008 guest works fine with either PAE on or off. Tested on VMware Player version 12.1 and 7.1.3 But even if you select less than 4GB of RAM, the setup of latest VMware Tools 10.0.5 crash Win2003 during the HGFS driver install phase. It looks like you do not even test 2003 guests.
Have you already opened an issue in your internal bug tracker?
This script: touch a touch b chmod -w a mv b a -f Works fine in Unix folder, but failed in hgfs shared folder ( eg /mnt/hgfs/... ) with this error: mv: cannot move `b' to `a': Permission den... See more...
This script: touch a touch b chmod -w a mv b a -f Works fine in Unix folder, but failed in hgfs shared folder ( eg /mnt/hgfs/... ) with this error: mv: cannot move `b' to `a': Permission denied This is a simpler way to reproduce an issue discussed here http://communities.vmware.com/thread/193589 Do something, it is an obvious bug.
Ok. It is 2013 already. The question is how to force hgfs to ignore read-only attribute during move. Or ignore this attribute always.
This bug is already half a year old. There is no player that can open vmx created in 5.x player and did not suffer from this bug. Please can you provide any info when this bug will be fixed or as... See more...
This bug is already half a year old. There is no player that can open vmx created in 5.x player and did not suffer from this bug. Please can you provide any info when this bug will be fixed or ask Steve for a patch? This issue really spoiling our live.
Same problem here. VMware Player 5.0.1 build-894247 Guest system Ubuntu 12.04 can't find a bugtracker here