VMware Communities
Gioxannes
Contributor
Contributor
Jump to solution

Coredump starting VMplayer 2.0 on Windows XP, please Help!

I have a problem starting a VM which I have copied fromone machine to another. The previous host machines where Mandriva Linux, Windows Vista and Windows XP - sp1, but on the machine I am trying it now it fails (Windows XP - sp2).

The message box displays:

MEM_ALLOC C:/ob/bora-45731/bora/lib/policy/policyNetQuarantine.c:2611

The log file contains:

Jun 19 13:32:51.748: player| Log for VMware Player pid=4028 version=2.0.0 build=build-45731 option=Release

Jun 19 13:32:51.748: player| Hostname=GCTPCD0113.network.lan

Jun 19 13:32:51.748: player| VMware Player: VMware virtual machine player

Jun 19 13:32:51.748: player| Command line: "D:\Program Files\VMware\VMware Player\vmplayer.exe" "-G" "G:\fnds\users\J-Schadee\Vincent\Vincent.vmx"

Jun 19 13:32:51.951: player| HostDeviceInfo_FindHostDisks: CreateFile
.\PhysicalDrive0 failed: Access is denied

Jun 19 13:32:52.107: player| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

Jun 19 13:32:52.107: player| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.

Jun 19 13:32:52.872: player| Foundry Init: setting up global state (0 threads)

Jun 19 13:32:52.872: player| Foundry Init: version 2, hostType 1, hostName (null), hostPort 0, options 0x203

Jun 19 13:32:52.904: player| MEM_ALLOC C:/ob/bora-45731/bora/lib/policy/policyNetQuarantine.c:2611

Jun 19 13:32:52.904: player| Backtrace:

Jun 19 13:32:52.904: player| -


Backtrace using dbghelp.dll----

Jun 19 13:32:52.919: player| Module path: D:\Program Files\VMware\VMware Player\vmwarebase.DLL

and much more...

Does anybody has any experience with this error?

Thanks!

0 Kudos
1 Solution

Accepted Solutions
KevinG
Immortal
Immortal
Jump to solution

If the following directory does not exist, create it and you should be now able to run VMware Player.

\Documents And Settings\All Users\Application Data\VMware\VMware Player

View solution in original post

0 Kudos
14 Replies
RDPetruska
Leadership
Leadership
Jump to solution

Please post the contents of "Vincent.vmx"

0 Kudos
Gioxannes
Contributor
Contributor
Jump to solution

Hi,

Here it is:

(Tried changing memsize to 128 from 244, did not help, MemAllowAutoScaleDown to True, did not help)

#!/usr/bin/vmware

config.version = "8"

virtualHW.version = "4"

memsize = "128"

MemAllowAutoScaleDown = "TRUE"

MemTrimRate = "-1"

displayName = "Vincent"

guestOS = "winxppro"

uuid.location = "56 4d 23 14 04 25 f7 2b-ec 4e 59 c1 14 24 03 49"

uuid.bios = "56 4d 23 14 04 25 f7 2b-ec 4e 59 c1 14 24 03 49"

tools.remindInstall = "TRUE"

sound.present = "TRUE"

sound.virtualDev = "sb16"

sound.filename = "-1"

sound.autodetect = "TRUE"

usb.present = "TRUE"

ethernet0.present = "TRUE"

ethernet0.addressType = "generated"

ethernet0.connectionType = "bridged"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Vincent.vmdk"

ide0:0.present = "TRUE"

ide0:0.autodetect = "TRUE"

ide0:0.filename = "auto detect"

ide0:0.deviceType = "atapi-cdrom"

scsi0.present = "TRUE"

scsi0.virtualDev = "buslogic"

scsi0:0.redo = ""

ethernet0.generatedAddress = "00:0c:29:24:03:49"

sound.deviceNr = "-1"

sound.device = "/dev/dsp"

ethernet0.generatedAddressOffset = "0"

usb.autoConnect.device0 = ""

checkpoint.vmState = ""

floppy0.fileName = "A:"

extendedConfigFile = "Vincent.vmxf"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"

isolation.tools.hgfs.disable = "FALSE"

sharedFolder.option = "alwaysEnabled"

0 Kudos
RDPetruska
Leadership
Leadership
Jump to solution

Try deleting the lines

sound.deviceNr="-1"

and

sound.device = "/dev/dsp"

Also, did you copy this guest from one host PC to another?

0 Kudos
Gioxannes
Contributor
Contributor
Jump to solution

I tried, but it did not help.

I have the idea that it has something to do with the fact that the vmplayer tries to create some memory file on a location where it has no writing rights. Is that possible? It is a diffent machine.

Which location would it be?

0 Kudos
RDPetruska
Leadership
Leadership
Jump to solution

Almost all files are written/created/etc. in the same folder. Where is your G: drive? How is it connected to this host?

0 Kudos
KevinG
Immortal
Immortal
Jump to solution

MEM_ALLOC C:/ob/bora-45731/bora/lib/policy/policyNetQuarantine.c:2611

It's not failing because of sound in the .vmx file. For some odd reason it's failing to allocate memory in policyNetQuarantine.

Was this a ACE VM?

0 Kudos
Gioxannes
Contributor
Contributor
Jump to solution

The G: drive is on a remote file server, but I tried as well having all the files on the local machine itself on the 😧 drive without success (same error).

And (to answer Kevin)

It is not a ACE VM, but one created with VMconverter.

0 Kudos
KevinG
Immortal
Immortal
Jump to solution

See if you can go to the directory ...\Documents And Settings\All Users\Application Data\VMware\VMware Player and if so, do you have permissions to write to this directory?

Gioxannes
Contributor
Contributor
Jump to solution

Well, it is a little bit strange. The VMware directory exists, but does not contain a VMplayer directory.

It does contain "VMware Workstation", a "vnckeymap" and a "VMware Virtual Machine Importer" folders.

I am not able to create one either, so I will ask the system administrator to change this.

Is it possible that in the meantime another directory can be used for these purposes? Can I change a setting somewhere?

Thanks for your help.

0 Kudos
Gioxannes
Contributor
Contributor
Jump to solution

Just as some extra information: if the 'all users' directory is open, then you can access the Vmachine of other users as well, who might have worked on a Vmachine with more rights, so there is a security issue here, right?

Message was edited by:

Gioxannes

0 Kudos
KevinG
Immortal
Immortal
Jump to solution

If the following directory does not exist, create it and you should be now able to run VMware Player.

\Documents And Settings\All Users\Application Data\VMware\VMware Player

0 Kudos
KevinG
Immortal
Immortal
Jump to solution

Just as some extra information: if the 'all users'

directory is open, then you can access the Vmachine

of other users as well, who might have worked on a

Vmachine with more rights, so there is a security

issue here, right?

Message was edited by:

Gioxannes

There is no security issue, since this directory is used to store global application data, just like all the other applications you have in C:\Documents and Settings\All Users\Application Data\

Gioxannes
Contributor
Contributor
Jump to solution

Creating the directory by the administrator and granting rights solved the problem.

Yes, I am happy again! Everybody thanks for the contributions. Smiley Happy

0 Kudos
KevinG
Immortal
Immortal
Jump to solution

Glad to hear that it is working Smiley Happy

0 Kudos