Hello,

I am not sure I am posting in the correct section but here goes.

We have a few servers that started running out of space on the C drive. After investigating we found that VMWare was still sending .dmp files every 5 minutes to the Default Users folder even though they had been converted to Hyper V long ago.

The servers are Windows Server2003, 64bit, SP2.

The only thing VMWare related item that I can still find on any of these servers is VMWare Tools. That service is disabled and the Tools software fails if I try to uninstall it.

I would like to remove/disable whatever is causing the dmp files to be created.

I am "assuming" it has something to do with the Tools but have not been able to figure much out by just Google searches.

Any help would be greatly appreciated.

Thank you

Has anyone had any sucess creating a Windows 2012 VM on VMWare Server via loading an iso image?  I tryied loading the iso but keep rebooting, reporting "Your PC Ran into a problem and needs to restart....

Hi all

I'm running debian lenny on vmware server 2 and all is working fine with my built kernel 2.6.35-14. I have built a new kernel 3.2.31 with quite the same options and it crashes on boot with an early exception 0d :

BIOS data check successful

Decompression Linux... Parsing ELF... done

Booting the kernel

PANIC: early exception 0d rip 10:ffffffff819b2547 error 0 cd2 0

The same behavior is occuring on vmware workstation but NOT on vmware ESXi...also, note that all is working fine on virtualbox and different physical servers.

after googling a lot, I have tried to pass the following options to kernel, but no change :

nosmep acpi=off

if it helps, I've been able to get different addresses of the exception (the 819b2547 is sometime different), but I don't remeber which parameters changed that.

Does anybody have an idea ?

thanks a lot

best regards

Julien

Hi All,

I am receiving this message on one of my vmware servers, and I am desperate to access this drive again as there are database files I need to access that I don't have a copy of anywhere else.

I have tried running windows recovery, and then loading the scci drivers but no hard drive is detected.

Is there any other way to recover this server ?

thanks in advance

We're running a Windows Server 2012 and VMware Workstation 9.0.2 with 2 shared and 1 unshared VMs.

The shared VMs are on the C: and the other VM is on the D:

When I run "vmrun list" I get "Total running VMs: 1" which points to the unshared VM on D:

I take it vmrun does not see/recognize the shared VMs.

I'm trying to use "vmrun -T ws-shared stop" to shutdown one of the shared VMs but I'm not having any luck.

I've tried a number of different combinations but nothing has worked.  This is the command that I'm trying to work with:

vmrun -T ws-shared -h https://<hostname>:8333/sdk -u username -p password stop "[standard]Server/Server 2008.vmx"

The command fails with "Error: Failed to connect to host or proxy"

Can someone please guide me in the right direction as to the correct format of the command, and if I need to make any additional changes before this works.

Do I need to do anything in regards to the port number/sdk for example?

Thanks

I've recently joined a company and therefore inherited a number of Virtual machines but one in particular is causing me some concern as it randomly blue screens. The kernel memory dump exceeds 400Mb (the maximum that I can make the paging file with the partition space I have available) so I have had to set minidumps instead to get a non truncated report. I have included one mini dump below, and I have also attached the previous minidump, but all of my others are practically identical to these two.

The probable cause in each dump is "memory_corruption". In a physical World I would replace the physical memory and expect that to resolve matters but in a virtual World, where the other virtual servers running on this box are stable, I'm not so sure that memory is the answer.

I was wondering if someone more technically competent than I at diagnosing these dumps, could possible advise me of what the likely cause is and give me something to go on.

This apparently was a physical box before being virtualised if that helps. The BSOD can occur at any time of day or night. Sometimes it goes down twice in a week, sometimes twice in a month. I haven't as yet come up with any pattern or trend that would stimulate the box into a crash.

Further Info:

Windows 2000 Advanced Server with SP4

Physical Memory 4Gb

Virtual memory 6.4Gb ( split as follows : C drive 400Mb, D drive 2Gb, E Drive 4Gb)

Boot.ini

boot loader

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINNT

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect /pae /3gb

Last memory dump (consistent with all others I've collected so far)

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRVc:\symbolshttp://msdl.microsoft.com/download/symbols

Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers

Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible

Kernel base = 0xdd400000 PsLoadedModuleList = 0xdd487c00

Debug session time: Tue Sep  2 06:18:46.948 2008 (GMT+1)

System Uptime: not available

Loading Kernel Symbols

...........................................................................................................

Loading User Symbols

Loading unloaded module list

....

*******************************************************************************

•                                                                             *

•                        Bugcheck Analysis                                    *

•                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {97, 2, 0, dd538d8d}

Probably caused by : memory_corruption ( nt!MiSessionInSwapProcess+103 )

Followup: MachineOwner

-

1: kd&gt; !analyze -v;r;kv;lmtn;.logclose;q

*******************************************************************************

•                                                                             *

•                        Bugcheck Analysis                                    *

•                                                                             *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 00000097, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: dd538d8d, address which referenced memory

Debugging Details:

-

READ_ADDRESS: unable to read from dd487c58

unable to read from dd487588

unable to read from dd48743c

unable to read from dd4790b8

unable to read from dd487450

unable to read from dd487584

unable to read from dd4790bc

unable to read from dd487644

unable to read from dd487bf8

00000097

CURRENT_IRQL:  2

FAULTING_IP:

nt!MiSessionInSwapProcess+103

dd538d8d 8b8b98000000    mov     ecx,dword ptr

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  f0e93cbc -- (.trap 0xfffffffff0e93cbc)

.trap 0xfffffffff0e93cbc

ErrCode = 00000000

eax=00000000 ebx=ffffffff ecx=dd487e84 edx=00000000 esi=dd0654f0 edi=dd487e84

eip=dd538d8d esp=f0e93d30 ebp=f0e93d44 iopl=0         nv up ei pl zr na pe nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

nt!MiSessionInSwapProcess+0x103:

dd538d8d 8b8b98000000    mov     ecx,dword ptr ds:0023:00000097=????????

.trap

Resetting default scope

LAST_CONTROL_TRANSFER:  from dd538d8d to dd46ca94

STACK_TEXT: 

f0e93cbc dd538d8d 00000000 f0e93d3c 00000021 nt!KiTrap0E+0x284

f0e93d44 dd442773 fcf05a00 dd486c40 fcf05a40 nt!MiSessionInSwapProcess+0x103

f0e93d7c dd467a65 fcf05a40 00000000 00000000 nt!MmInSwapProcess+0x3e5

f0e93d90 dd4679bc 00000000 00000000 00000000 nt!KiInSwapProcesses+0x33

f0e93da8 dd458b38 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x6e

f0e93ddc dd46e256 dd46794e 00000000 00000000 nt!PspSystemThreadStartup+0x54

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND:  kb

FOLLOWUP_IP:

nt!MiSessionInSwapProcess+103

dd538d8d 8b8b98000000    mov     ecx,dword ptr

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiSessionInSwapProcess+103

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  403d35f9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiSessionInSwapProcess+103

BUCKET_ID:  0xA_nt!MiSessionInSwapProcess+103

Followup: MachineOwner

-

eax=fd98513c ebx=0000000a ecx=00000000 edx=00000000 esi=dd538d8d edi=00000097

eip=dd46ca94 esp=f0e93ca8 ebp=f0e93cbc iopl=0         nv up ei ng nz na pe nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000286

nt!KiTrap0E+0x284:

dd46ca94 f7457000000200  test    dword ptr ,20000h ss:0010:f0e93d2c=00010246

ChildEBP RetAddr  Args to Child             

f0e93cbc dd538d8d 00000000 f0e93d3c 00000021 nt!KiTrap0E+0x284 (FPO: TrapFrame @ f0e93cbc)

f0e93d44 dd442773 fcf05a00 dd486c40 fcf05a40 nt!MiSessionInSwapProcess+0x103 (FPO: )

f0e93d7c dd467a65 fcf05a40 00000000 00000000 nt!MmInSwapProcess+0x3e5 (FPO: )

f0e93d90 dd4679bc 00000000 00000000 00000000 nt!KiInSwapProcesses+0x33 (FPO: )

f0e93da8 dd458b38 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x6e (FPO: )

f0e93ddc dd46e256 dd46794e 00000000 00000000 nt!PspSystemThreadStartup+0x54 (FPO: )

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

start    end        module name

dd062000 dd076460   hal      hal.dll      Fri Mar 21 02:04:42 2003 (3E7A733A)

dd400000 dd5a3f00   nt       ntkrpamp.exe Wed Feb 25 23:55:37 2004 (403D35F9)

de000000 de1a4000   win32k   win32k.sys   unavailable (FFFFFFFE)

de1a4000 de1b9000   vmx_fb   vmx_fb.dll   unavailable (FFFFFFFE)

de1b9000 de1c6000   RDPDD    RDPDD.dll    unavailable (FFFFFFFE)

f0a00000 f0a0f000   pci      pci.sys      unavailable (FFFFFFFE)

f0a10000 f0a1c000   isapnp   isapnp.sys   unavailable (FFFFFFFE)

f0a20000 f0a30000   cpq32fs2 cpq32fs2.sys ***** Invalid (FD9B60C9)

f0a30000 f0a38700   CLASSPNP CLASSPNP.SYS Wed Jan 15 19:42:51 2003 (3E25B9BB)

f0a50000 f0a5c4c0   VIDEOPRT VIDEOPRT.SYS Wed Jan 15 19:47:20 2003 (3E25BAC8)

f0a60000 f0a6b680   i8042prt i8042prt.sys Wed Apr 16 05:00:59 2003 (3E9CD57B)

f0a70000 f0a7f400   serial   serial.sys   Wed Apr 16 05:19:39 2003 (3E9CD9DB)

f0a80000 f0a8db00   vmx_svga vmx_svga.sys Wed Apr 11 18:53:38 2007 (461D20A2)

f0a90000 f0a9ca80   rasl2tp  rasl2tp.sys  Wed Apr 30 00:05:06 2003 (3EAF0522)

f0aa0000 f0aabc40   raspptp  raspptp.sys  Thu May 15 00:47:00 2003 (3EC2D574)

f0ab0000 f0abea20   parallel parallel.sys Wed Jan 15 19:47:14 2003 (3E25BAC2)

f0ad0000 f0ad9ce0   NDProxy  NDProxy.SYS  Fri Oct 01 00:25:35 1999 (37F3F16F)

f0af0000 f0af8fa0   Npfs     Npfs.SYS     Sun Oct 10 00:58:07 1999 (37FFD68F)

f0b00000 f0b08680   msgpc    msgpc.sys    Wed Jan 15 19:54:25 2003 (3E25BC71)

f0b10000 f0b181a0   netbios  netbios.sys  Tue Oct 12 20:34:19 1999 (38038D3B)

f0b20000 f0b28580   savonaccessfilter savonaccessfilter.sys Mon Sep 10 12:07:39 2007 (46E5257B)

f0bf0000 f0bf9000   Fips     Fips.SYS     unavailable (FFFFFFFE)

f0c80000 f0c86000   PCIIDEX  PCIIDEX.SYS  unavailable (FFFFFFFE)

f0c88000 f0c90000   MountMgr MountMgr.sys unavailable (FFFFFFFE)

f0c90000 f0c97000   symc8xx  symc8xx.sys  ***** Invalid (FD9B60C9)

f0c98000 f0c9e000   sym_hi   sym_hi.sys   ***** Invalid (FD9B60C9)

f0ca0000 f0ca7720   disk     disk.sys     Wed Jan 15 19:43:05 2003 (3E25B9C9)

f0ca8000 f0cad880   nsifiltr nsifiltr.sys Wed Oct 03 18:05:49 2007 (4703CBED)

f0cb0000 f0cb5100   agp440   agp440.sys   Wed Jan 15 19:47:07 2003 (3E25BABB)

f0cd0000 f0cd5ec0   kbdclass kbdclass.sys Thu Feb 20 16:37:30 2003 (3E55044A)

f0ce0000 f0ce5400   mouclass mouclass.sys Thu Feb 20 16:37:45 2003 (3E550459)

f0ce8000 f0ced000   TDTCP    TDTCP.SYS    ***** Invalid (FCFD2F69)

f0cf0000 f0cf6100   parport  parport.sys  Wed Jan 15 19:47:13 2003 (3E25BAC1)

f0d08000 f0d0f000   fdc      fdc.sys      unavailable (FFFFFFFE)

f0d18000 f0d1ec40   cdrom    cdrom.sys    Wed Jan 15 19:43:04 2003 (3E25B9C8)

f0d30000 f0d37280   vmxnet   vmxnet.sys   Sun Sep 30 13:22:32 2007 (46FF9508)

f0d58000 f0d5c400   ptilink  ptilink.sys  Wed Jan 15 19:47:15 2003 (3E25BAC3)

f0d68000 f0d6c0e0   raspti   raspti.sys   Fri Oct 08 21:45:10 1999 (37FE57D6)

f0d80000 f0d84a60   flpydisk flpydisk.sys Wed Jan 15 19:42:52 2003 (3E25B9BC)

f0d90000 f0d96a20   EFS      EFS.SYS      Wed Jan 15 19:46:55 2003 (3E25BAAF)

f0db0000 f0db5240   Msfs     Msfs.SYS     Wed Oct 27 00:21:32 1999 (3816377C)

f0dd0000 f0dd7d00   wanarp   wanarp.sys   Fri Aug 16 13:25:01 2002 (3D5CEF1D)

f0de0000 f0de7000   vmmemctl vmmemctl.sys unavailable (FFFFFFFE)

f0e10000 f0e13000   BOOTVID  BOOTVID.dll  unavailable (FFFFFFFE)

f0e14000 f0e17000   compbatt compbatt.sys ***** Invalid (FD9B66C9)

f0e18000 f0e1b000   PartMgr  PartMgr.sys  unavailable (FFFFFFFE)

f0e1c000 f0e20000   cpqarray cpqarray.sys ***** Invalid (FD9B60C9)

f0e20000 f0e24000   symc810  symc810.sys  ***** Invalid (FD9B60C9)

f0e24000 f0e27c80   cpqcissm cpqcissm.sys Mon May 19 17:19:35 2003 (3EC90417)

f0e28000 f0e2b460   cpqarry2 cpqarry2.sys Mon Nov 05 21:47:33 2001 (3BE708F5)

f0e2c000 f0e2f480   nsirecog nsirecog.sys Wed Oct 03 18:05:49 2007 (4703CBED)

f0f00000 f0f02000   BATTC    BATTC.SYS    unavailable (FFFFFFFE)

f0f02000 f0f04000   intelide intelide.sys ***** Invalid (FD9B65C9)

f0f04000 f0f06000   Diskperf Diskperf.sys ***** Invalid (FD9B68E9)

f0f06000 f0f08000   dmload   dmload.sys   unavailable (FFFFFFFE)

f0f0a000 f0f0b300   kbstuff5 kbstuff5.sys Wed Nov 23 19:44:23 2005 (4384C697)

f0f0c000 f0f0d280   vmmouse  vmmouse.sys  Wed Apr 11 18:54:49 2007 (461D20E9)

f0f12000 f0f13ca0   Fs_Rec   Fs_Rec.SYS   Wed Jan 15 19:53:30 2003 (3E25BC3A)

f0f1a000 f0f1be40   rasacd   rasacd.sys   Sat Sep 25 19:41:23 1999 (37ED1753)

f0fb6000 f0fb8000   ParVdm   ParVdm.SYS   unavailable (FFFFFFFE)

f0fc8000 f0fc9000   WMILIB   WMILIB.SYS   unavailable (FFFFFFFE)

f0fc9000 f0fca000   pciide   pciide.sys   ***** Invalid (FD9B65C9)

f105e000 f105e840   idisw2km idisw2km.sys Wed Nov 23 19:45:10 2005 (4384C6C6)

f1088000 f1088a40   audstub  audstub.sys  Sat Sep 25 19:35:33 1999 (37ED15F5)

f10a1000 f10a1d80   swenum   swenum.sys   Sat Sep 25 19:36:31 1999 (37ED162F)

f10bf000 f10bf9e0   Null     Null.SYS     Sat Sep 25 19:34:58 1999 (37ED15D2)

f10c3000 f10c3ee0   Beep     Beep.SYS     Wed Oct 20 23:18:59 1999 (380E3FD3)

f10c8000 f10c8f80   mnmdd    mnmdd.SYS    Sat Sep 25 19:37:40 1999 (37ED1674)

f3faf000 f3fb3000   prepdrv  prepdrv.sys  unavailable (FFFFFFFE)

f409b000 f40b1000   RDPWD    RDPWD.SYS    ***** Invalid (FCFD2F69)

f4101000 f4111000   ipsec    ipsec.sys    ***** Invalid (E2AF6008)

f41e1000 f41e4000   spud     spud.sys     unavailable (FFFFFFFE)

f4c69000 f4c8c000   Fastfat  Fastfat.SYS  unavailable (FFFFFFFE)

f4e94000 f4e9d000   termdd   termdd.sys   ***** Invalid (FD9B68E9)

f509c000 f50d7000   srv      srv.sys      ***** Invalid (E13824C8)

f533f000 f534e000   Cdfs     Cdfs.SYS     unavailable (FFFFFFFE)

f5537000 f5555000   afd      afd.sys      ***** Invalid (FD710149)

f56bd000 f56ce000   dump_symmpi dump_symmpi.sys ***** Invalid (FD71D609)

f56f6000 f575aca0   mrxsmb   mrxsmb.sys   Thu Jan 20 07:25:21 2005 (41EF5CE1)

f576d000 f5796900   rdbss    rdbss.sys    Fri Dec 03 03:37:11 2004 (41AFDF67)

f5797000 f57aff00   savonaccesscontrol savonaccesscontrol.sys Mon Sep 10 12:08:16 2007 (46E525A0)

f57b0000 f57d91a0   netbt    netbt.sys    Thu May 22 02:51:10 2003 (3ECC2D0E)

f57da000 f58281a0   tcpip    tcpip.sys    Thu May 12 11:24:58 2005 (42832EFA)

f5cb1000 f5cdb3a0   update   update.sys   Wed Apr 16 05:22:01 2003 (3E9CDA69)

f5cdc000 f5cf7b40   ks       ks.sys       Wed Apr 16 05:02:11 2003 (3E9CD5C3)

f5d0a000 f5d2d060   rdpdr    rdpdr.sys    Fri Mar 21 21:43:14 2003 (3E7B8772)

f5d56000 f5d6cba0   ndiswan  ndiswan.sys  Wed Apr 30 00:05:01 2003 (3EAF051D)

f5d7d000 f5d80580   vga      vga.sys      Sat Sep 25 19:37:40 1999 (37ED1674)

f5db9000 f5dbd000   dump_scsiport dump_scsiport.sys unavailable (FFFFFFFE)

f5f4e000 f5f51e60   TDI      TDI.SYS      Wed Jan 15 19:56:26 2003 (3E25BCEA)

f5f5e000 f5f602e0   ndistapi ndistapi.sys Wed Jan 15 19:54:15 2003 (3E25BC67)

f5f6a000 f5f6d640   serenum  serenum.sys  Wed Jan 15 19:47:01 2003 (3E25BAB5)

f5f7e000 f5f805a0   CmBatt   CmBatt.sys   Wed Jan 15 19:44:29 2003 (3E25BA1D)

f5fbe000 f5fd1b20   CPQPHP   CPQPHP.SYS   Mon Jan 06 23:44:27 2003 (3E1A14DB)

f5fd2000 f5fe7640   Mup      Mup.sys      Wed Jan 15 19:54:01 2003 (3E25BC59)

f5fe8000 f6011aa0   NDIS     NDIS.sys     Wed Apr 30 00:05:01 2003 (3EAF051D)

f6012000 f60945a0   Ntfs     Ntfs.sys     Fri May 09 20:46:45 2003 (3EBC05A5)

f6095000 f60a67c0   KSecDD   KSecDD.sys   Sun Sep 21 01:32:19 2003 (3F6CF193)

f60a7000 f60b91c0   Dfs      Dfs.sys      Wed Feb 12 02:19:06 2003 (3E49AF1A)

f60ba000 f60d4c00   dblhook  dblhook.sys  Wed Oct 03 18:05:50 2007 (4703CBEE)

f60d5000 f60e6180   drvmcdb  drvmcdb.sys  Thu Feb 08 22:01:47 2001 (3A83174B)

f60e7000 f60f8000   symmpi   symmpi.sys   Mon Jun 14 16:28:44 2004 (40CDC42C)

f60f8000 f610e000   adpu160m adpu160m.sys ***** Invalid (FD9B60C9)

f610e000 f6124000   atapi    atapi.sys    ***** Invalid (FD9B68E9)

f6124000 f6137000   SCSIPORT SCSIPORT.SYS unavailable (FFFFFFFE)

f6137000 f6159000   dmio     dmio.sys     unavailable (FFFFFFFE)

f6159000 f6176000   ftdisk   ftdisk.sys   unavailable (FFFFFFFE)

f6176000 f619e000   ACPI     ACPI.sys     ***** Invalid (FD9B68E9)

Unloaded modules:

f5225000 f5267000   cpqasm.sys

    Timestamp: unavailable (00000000)

    Checksum:  00000000

f0b30000 f0b39000   redbook.sys

    Timestamp: unavailable (00000000)

    Checksum:  00000000

f0da0000 f0da5000   Cdaudio.SYS

    Timestamp: unavailable (00000000)

    Checksum:  00000000

f5d85000 f5d88000   Sfloppy.SYS

    Timestamp: unavailable (00000000)

    Checksum:  00000000

Closing open log file c:\debuglog.txt

Any assistance that anybody could give me in diagnosing the fault or possible remedies, would be much appreciated.

Cheers

I have a Windows Server 2003 as host, with VMware Server 2.0 (build 122956), with a Windows XP (SP3) installed as a virtual machine. I'm trying to shut down the image from the host, but I'm having no luck..

The list command works fine:

D:\VirtualMachines&gt;"c:\program files\VMware\VMwareServer\vmrun.exe" -T server -h https://mymachine.domain.com:8333/sdk -u &lt;MyUsername&gt; -p &lt;MyPassword&gt; list

Total running VMs: 1

FTP_main/Windows XP Professional.vmx

But when I try to shut down that machine:

D:\VirtualMachines&gt;"c:\program files\VMware\VMwareServer\vmrun.exe" -T server -h https://mymachine.domain.com:8333/sdk -u &lt;MyUsername&gt; -p &lt;MyPassword&gt; stop "[dstore] FTP_main/Windows XP Professional.vmx" soft

Error: The virtual machine is not powered on: FTP_main/Windows XP Professional.vmx

It

is powered on, and I don't have a clue as to what is wrong here..

Anybody have any tips here?

This one is driving me nuts, I have a virtual machine that randomly suspends itself. I checked the power options inside the VM, it's not set to any power plans (it should stay on).

I checked the logs on the host and there's no specific events that could've caused this, and the only thing I can see is within the vmx's log that the VMTools initiated the suspend call. I thought this was isolated to this particular VM, but the problem has spread to the other VMs right now, to a lesser frequency.

Environment:

Host: Windows 2008 Enterprise x64, VMWare Server 2, running 4 total Virtual Machine, Quad Core Xeon 2.8ghz, 16GB RAM

Guest: Windows 2003 Enterprise x86 SP2, using 2 proc threads, 2GB RAM, virtualized from physical machine by VMware vCenter.

Log from the vmx:

Mar 13 20:32:25.277: vmx| scsi0:0: Command WRITE(10) took 1.563 seconds (ok)

Mar 13 20:35:13.132: vmx| TOOLS sending 'OS_Suspend' (5) state change request

Mar 13 20:35:14.031: vcpu-0| TOOLS state change 5 returned status 1

Mar 13 20:35:14.036: vcpu-0| CPT current = 0, requesting 1

Mar 13 20:35:14.036: vcpu-0| Sync monModules(1).

Mar 13 20:35:14.036: vcpu-0| Done Sync monModules(1).

Mar 13 20:35:14.036: vcpu-1| Sync monModules(1).

Mar 13 20:35:14.036: vcpu-1| Done Sync monModules(1).

Mar 13 20:35:14.036: vmx| CPT: monitor ACKing mode 1

Mar 13 20:35:14.106: vmx| CPT current = 1, requesting 2

Mar 13 20:35:14.106: vmx| CPT: monitor ACKing mode 2

Mar 13 20:35:14.106: vmx| CPT current = 2, requesting 3

Mar 13 20:35:14.141: vcpu-0| Cpt monModules(3).

Mar 13 20:35:14.146: vcpu-0| Done Cpt monModules(3).

Mar 13 20:35:14.181: vcpu-1| Cpt monModules(3).

Mar 13 20:35:14.181: vcpu-1| Done Cpt monModules(3).

Mar 13 20:35:14.181: vmx| CPT: monitor ACKing mode 3

Mar 13 20:35:14.181: vmx| DUMPER: Modifying checkpoint file .\SBDIVAPP01.vmss

Mar 13 20:35:14.181: vmx| Checkpointed in VMware Server, 2.0.0 build-122956, build-122956, Windows Host

Mar 13 20:35:14.191: vmx| BusMemSample: checkpoint 3 initPercent 5 touched 52428

Mar 13 20:35:14.191: vmx| MM: Renamed D:\Virtual Machines\SBDIVAPP01\SBDIVAPP01.vmem to .\SBDIVAPP01.vmem

Mar 13 20:35:14.436: vmx| GuestMsg: Channel 0, Cannot unpost because the previous post is already completed

Mar 13 20:35:14.436: vmx| GuestRpc: Channel 0 reinitialized.

Mar 13 20:35:14.436: vmx| GuestMsg: Channel 1, Cannot unpost because the previous post is already completed

Mar 13 20:35:14.436: vmx| GuestRpc: Channel 1 reinitialized.

Mar 13 20:35:18.091: vmx| Stopping VCPU threads...

Mar 13 20:35:18.171: mks| SOCKET 3 (1624) recv error 10054: An existing connection was forcibly closed by the remote host

Mar 13 20:35:18.171: mks| SOCKET 3 (1624) destroying VNC backend on socket error: 1

Mar 13 20:35:18.176: mks| MKS switching absolute mouse off

Mar 13 20:35:19.096: mks| MKSHostOps_Exit3D: 1, 0

Mar 13 20:35:19.096: mks| Async MKS thread is exiting

Mar 13 20:35:19.096: vmx| USB: Disconnecting device 0x200000010e0f0002

Mar 13 20:35:19.096: vmx| USB: Disconnecting device 0x400000010e0f0003

Mar 13 20:35:19.116: vmx| MKS local poweroff

Mar 13 20:35:19.121: vmx| AIOWIN32C: asyncOps=929142 syncOps=0 bufSize=300Kb fixedOps=25681 sgOps=809264 sgOn=1

Mar 13 20:35:19.121: aioCompletion| AIO thread processed 929142 completions

Mar 13 20:35:19.121: vmx| AIOWIN32: asyncOps=0 syncOps=0 bufSize=0Kb delayed=0 fixed=0 sgOp=0 sgOn=1

Mar 13 20:35:19.121: vmx| WORKER: asyncOps=126192 maxActiveOps=1 maxPending=0 maxCompleted=0

Mar 13 20:35:19.641: vmx| Transitioned vmx/execState/val to suspended

Mar 13 20:35:19.966: vmx| vmdbPipe_Streams: Couldn't read

Mar 13 20:35:19.966: vmx| VMX idle exit

Mar 13 20:35:19.966: vmx| Flushing VMX VMDB connections

Mar 13 20:35:19.966: vmx| IPC_exit: disconnecting all threads

Mar 13 20:35:19.966: vmx| VMX exit (0).

Any help would be appreciated. Thanks.

A few days ago I ran into the following problem:

when try to logon to my vmware-server at https://myhost.com:8333 I only get a blank page but not the usual and expected login-window

I tried with firefox3 and recent opera under linux and IE7 under windows. This is not a certificate-problem, cause all certificates are installed and this never was a problem before. I tried to restart vmware-mgmt but it didnt help. I even rebooted the whole host-machine (a linux-server) but no effect.

I can connect to the vmware-server using the vmware virtual infrastructure client and all VM's are running fine. Its just that I cant use the webinterface, which I really like to use, cause its the easiest way to manage our VM's on the run.

any suggestions?

thnx a lot,

peter

I'm trying to expand a SCSI VMDK on VMware Server 2 build 122956 running on Windows Server 2008 x64 that does not have any snapshots. When I shut down the VM, go to edit Hard Disk 1 (SCSI 0:0) and select Increase Capacity, add space and then hit OK I get the following error:

"Reconfigure Virtual Machine" failed to complete

Operation failed becuase file already exists

The guest is also Windows Server 2008 x64 and I have not been able to find any posts here or elsewhere indicating this error. Any help is much appreciated.

I am having trouble with getting accurate hardware monitoring with ESXi 5.1 on an HP (ProLiant DL380p Gen8) server. The build installed is 799733 (HP version, with HP Tools installed)

I am using this server as an example, however we have other servers that don't appear to be showing correct hardware information either. We use N-Able for our RMM software, and I noticed that it detected 5 power supplies for this server (4, 5, and 6 showed normal while 1 and 2 showed a failure). Also, all of the fans were showing a failed status for health state as well. I called N-Able and they looked into it and basically told me that the UI was displaying the information given by VMware, and I would need to contact VMware to see why it wasn't giving out the correct health information.

When I vSphere directly to the Hyper Visor I can see that N-Able may be correct. Under Power it shows the following information:

In N-Able it detected power supply 1-2, 4,5, & 6. 1 & 2 show failed, the rest show that they are fine. There are not 5 power supplies in this server. Also, N-Able detected 6 fans and shows the following for all of them.

N-Able pulls Fan and Power Supply status directly from the ESXi via

https://<insert_IP_address_of_ESXi_server_here>/mob/?moid=ha-host&doPath=runtime.healthSystemRuntime.systemHealthInfo.numericSensorInfo

Hi!,

   I'm having a problem with one of my virtual machines on VMWARE Server 2.

Suddenly, after a server crash, the machine didn't boot up correctly. Apparently something went wrong with the hard disk. I tried to remove and add again the hard disk, however, when I tried to add it it says:

"The selected file is not a valid virtual disk file. Please choose a different name"

Attached there are vmx, vmxf and vmdk files.

Any hint about this?

Hi all

Can anybody can help me with Windows 2012 64bit installation on the VMware ServerVersion 2.0.2Build 203138?

I'm trying to install Windows 2012 from ISO image called: 9200.16384.WIN8_RTM.120725-1247_X64FRE_SERVER_EVAL_EN-US-HRM_SSS_X64FREE_EN-US_DV5.ISO downloaded from MS

Installation begins but Windows 2012 hangs after few seconds with something like blue screen and

information: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

I searched web for solution but it is hard to find proper solution in this case.

Thanks in advance

--

Artur Dębski

http://blogit.one.pl

http://www.amt.pl

Hi friends ;

Host : windows 7

Guest : Linux 5.5

I am using virtual machine version 9 (brigged n/w)
I want to connect my vmware machine from putty without LAN connection.
I strongly believe it is possible. I dont know how can i do that ?
Always i am facing 'network unreachable'
Please help me ..

I am login as Admin, but cannot find the specific policy preventing Windows installer from installing VMware2.

The following is the pop up message received: “The system administrator has set policies to prevent this installation”

I did not have problem installing Anti-Virus. There is no restriction set from GPO Admin Template for Windows Components\Windows Installer.

Any suggestion will be much appreciated,

-Andy

Hi,

I have a problem with VMware server 2.0 running on Windows 2003: Guests do not start when VMware server starts. Instead vmauthd error is logged in event log and hostd.log.

I already checked the permissions on relevant VMware directories and re-install VMware server, but the problem persists.

Symantec Endpoint Protection is running on the same machine.

Thanks for any help! 

Since an unexpected reboot of the Linux machine (Ubuntu 8.10), the windows XP Professional that was installed in the vmware server 2 machine stopped working. Now everytimei turn it on, a blue screen appears, with the message "BAD_POOL_CALLER", and it keeps restarting itself. I am unable to start in safe mode, because the same blue screen appears...

Does anybody know the cause, or have any solution to repair the windows machine? I attached a snapshot of the error.

Thank you very much

I have a serial port on my CentOS5.2 VM. It uses a file (instead of a named pipe or a physical device). I use it to get the console output.

Problem is, every time the VM starts, I get the following query:

msg.serial.file.open:Serial port output file "/space/vm/CentOS5/console" already exists.
Do you want to replace it with any newly created content, or append new content to the end of the file?

Is there a way to make 'append' the automatic choice?

I have seen lots of threads regarding this, but no recent ones.  This problem hit me a few months ago.  Only solution was to rebuild the host from scratch and re-install latest VMWare server 2.0 build. Am running Win2k8 X64 Std as the host, latest build of VMWare Server 2.0 122956 - 10/29/08.  Following the updates from the most recent patch Tuesday on my host system, none of the virtual machines now get past 95% on startup as indicated on the VMWare Infrastructure Web Access interface.  I am not positive that it is a Windows patch that is causing this, but very probable, I suppose.  However, if the virtual machine has already been created, it will actually finsihing startup in the background, and I can log into it remotely using SSH or RDP, as it may be.  But I cannot pull open a console on these VM's, which means I cannot build any new ones!  As a workaround Is there any way I can launch a console manually with the vmware-vmrc.exe executable? Anyone else having this problem?  Recent threads show problem to be on WIndows x64 hosts.  I am running on XP x64 as well and am not having this problem. 

FYI, I uninstalled the last dozen Windows updates and the problem remains.

OK

This has got to be the most simple task and I obviously am a stupid person for not being able to find this in any of the help manuals.  I have Ubuntu 8.10 64bit and running vmware server 2.0 with a host OS win XP.  I posted a help on here to ask why, every time I start vmware I have to delete my vm and datastore, then remake them both.  One answer I got back was maybe the hard disk that the vm was kept on is not starting or mounting before vmware is, therefore it does not know it exists.  This I can understand, it's almost obvious. 

So all I need to do is to restart vmware server and it should find my mounted disk with my vm on yes?

For the life of me I cannot find how to do this, I've read loads....obviously all in the wrong place, I can't find a command that simply restarts vmware server 2.0 in linux!  I can find loads of vmnet....vm*** processes running but I don't want to end them as I don't know how to start them unless I reboot, then I'm back to square one.

So what is the command to restart vmware?   somthing like vmware -restart?

Si