Hi

I have several dell servers running VMware server 2.0.2 on Windows server 2008 R2

On each of these servers I have three or four guests, some guests are running windows server 2003 and others running windows server 2008.

We remote administer the Dell physical host servers using terminal services.

Frequently when we log into the host servers we get the following issue

1 – The terminal server session will wait for up to 60 seconds with the message “Please wait for the user profile service”

2 – While the terminal server session to the host has the message, all network connectivity to the guest machines on the host is lost.

3 – When the terminal server session finally logs on to the hosts, network connectivity to the guests resumes.

There are no events or errors in the logs to indicate where the problem may lay.

We have many physical servers that reside in the same domain, both server 2003 and server 2008, but none of them ever experience any issues with terminal services. Only VMware host servers behave this way, and all of them behave the same.

Any suggestions please?

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

Hi, I am working with a problem vmdk file. The good news is, no snapshots or other complications. The bad news is, I've taken this as far as I know to take it.

I copied the vm to another machine and behavior is exactly the same in both places. Can't start it. Can't add the vmdk to a new machine either. I have seen a few posts where folks know how to snip out the bad bits... but that was not a Windows box. Can it be done here as well?

I reckon this is the relevant bit of the log, but I am happy to post any additional information that may be useful. I will also attach a zip of the log. Thank you in advance for any suggestions.

Feb 27 15:50:29.475: vmx| DISK: OPEN scsi0:0 'D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk' persistent R[]
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Grain #542052 @69393792 is pointed to by multiple GTEs
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DG): GT[1376][7] = 69393792 / 69328256
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][7] = 69328256
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (XG): GT[1376][12] = 69325123 / 69328896
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][12] = 69328896
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (XG): GT[1376][28] = 69330635 / 69330944
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][28] = 69330944
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (XG): GT[1376][30] = 69326915 / 69331200
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][30] = 69331200
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Grain #549100 @70295936 is pointed to by multiple GTEs
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DG): GT[1376][127] = 70295936 / 70492544
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][127] = 70492544
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Grain #1449 @196608 is pointed to by multiple GTEs
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1376][255] = 196608 / 0
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1376][383] = 196608 / 0
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1376][511] = 196608 / 0
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1377][127] = 196608 / 0
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1377][255] = 196608 / 0
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1377][383] = 196608 / 0
Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1377][511] = 196608 / 0
Feb 27 15:50:29.882: vmx| DISKLIB-SPUTIL: ===== Extent dump (D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk) =====

I had a vmware machine sitting on a physical disk that died.

The drive was sent for data recovery and the following files are toast (not getting them back):

564da9de-2ed4-2b8a-43ac-65475c778139.vmem

Ubuntu-000001-s001.vmdk

Ubuntu-000001-s002.vmdk

Ubuntu-000001-s004.vmdk

Ubuntu-000001-s007.vmdk

Ubuntu-000001-s034.vmdk

The following are recoverable:

564daa0f-73eb-a52d-5d58-0680385a1372.vmem

nvram

Ubuntu-000001-s003.vmdk

Ubuntu-000001-s005.vmdk

Ubuntu-000001-s006.vmdk

Ubuntu-000001-s008.vmdk

etc., up to:

Ubuntu-000001-s051.vmdk

but missing 01, 02, 04, 07, 34 as above.

I also have:

Ubuntu-f001.vmdk

Ubuntu-f002.vmdk

Ubuntu-f003.vmdk

etc., all the way to:

Ubuntu-f051.vmdk

And:

Ubuntu-000001.vmdk

Ubuntu-f001.vmdk

Ubuntu-f002.vmdk

Ubuntu-f003.vmdk

etc to:

Ubuntu-f051.vmdk

And:

ubuntu-Snapshot3.vmem

ubuntu-Snapshot3.vmsn

Ubuntu.vmdk

Ubuntu.vmsd

Ubuntu.vmx

vmware-0.log

vmware-1.log

vmware-2.log

vmware.log

On a scale of 1 to 10, how screwed am I?

Hi!

I am using vmware since about one year on my quite slow machine - worked great for small systems.

Via Nehemiah 1GHz, 1GB RAM, Debian Etch with selfcompiled kernel 2.6.26.5.

vmware server 1.0.4 run great on 2.6.24.X (I think), later the moduls didn't compile altough actual vmware-any-any-patches.

today I upgrade to vmware server 2.0 and loved it, because it compiled without problems (except vsock, but I think I dont need it) and without any patches. great.

but, my machines are not working. I have no idea why this happens - here is a logfile, perhaps anybody is able to help me.

The machine tries to start, modules are loaded correctly without errors, no special logs in dmesg is reported ...

As I have (as small homeuser) no support I am not venturing sending the file anywhere which was created with vm-support.

Thanks.

>>>Cyber

Hallo,

need HELP.

i had 3 virtual machines (1xW2k3 DC and 2xW2k3 as an virtual Cluster) with Virtual Server 1.05 on my Laptop (XP SP2) created.

USB functions great.

Then our IT installs Vista SP1 on my Laptop. OK....no problem i thought...what a great optimism.

On the new installed Laptop i install the new Vmware Server 1.07 and import the old with Virtual Server 1.05 created virtual machines.

But after connecting an USB-Drive i wasn´t able to connect the device in the virtual machine...it was greyed out.

After severel trys to reanimate it i decide to install VMware Server 2.0. But the same Problem. In the Remote Console i can see what type of USB-Drive is connected like "Sandisk USB-Massstorage", but the connect Button is greyed out.

The problem i see is, that on the hostsystem the "VMmware USB-Device"-Driver is not installed and the guest-Systems think that he is installed.

All attempts were in vain to install this driver manually on the Laptop (host-system).

Can anyone help me?

Thanks Juergen

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> !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>"c:\program files\VMware\VMwareServer\vmrun.exe" -T server -h https://mymachine.domain.com:8333/sdk -u <MyUsername> -p <MyPassword> list

Total running VMs: 1

FTP_main/Windows XP Professional.vmx

But when I try to shut down that machine:

D:\VirtualMachines>"c:\program files\VMware\VMwareServer\vmrun.exe" -T server -h https://mymachine.domain.com:8333/sdk -u <MyUsername> -p <MyPassword> 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?

Hello. This might sound trivial, but obviously I'm missing something here... So here's the setup :

I have a Windows 2008 server (Web Edition) ; this server has a network card that's got a public IP address working OK.

I have VMWare 2.0 installed on that server.

Then I have a VM running a Windows 2003 SBS setup. The network card in the VM is using VMWare's NAT. For convenience I have setup Window 2003 to use a manual IP address rather than a DHCP-obtained one, but that makes no difference with regards to the issue.

The problem :

- within the VM, I can ping outside (like ping www.google.com works allright), DNS requests are resolved Ok (as in ping www.google.com works ) ; querying a DNS on the Internet using nslookup works Ok as well.

- I can not browse outside !? with IE

- I have tried telnetting known working servers on various ports (25, 80, 21, 110...) with no success at all

FWIW, I can also rdp into the Windows 2003 client from anywhere on the Internet, having forwarded the appropriate port in VMWare's NAT configuration.

So far, this sounds like a firewall issue. The thing is, the firewall in the Windows 2003 client is disabled and I tried with the Windows 2008 firewall disabled as well. No luck.

Ideas welcome...

Z.

I see plenty of links talking about how to migrate VMWare VMs to ProxMox, but I haven't been able to find even one in the other direction!

Can anyone provide instructions for migrating a ProxMox VM to VMWare Server?

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

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.

G'day,

I'm running VMServer 2.0.1 on Ubuntu 9.0.4 (Jaunty) hosting CentOS 4.7 guest VMs.

I am continually seeing the following message when powering on a guest VM:

The network bridge on device vmnet0 is temporarily down because the bridged Ethernet interface is down. The virtual machine may not be able to communicate with the host or with other machines on your network.

The work-around I've discovered is to restart the vmware services, i.e.

$ sudo /etc/init.d/vmware stop

Stopping VMware autostart virtual machines:

  Virtual machines                                                    done

Stopping VMware management services:

VMware Virtual Infrastructure Web Access

  VMware Server Host Agent                                            done

Stopping VMware services:

  VMware Authentication Daemon                                        done

  Virtual machine communication interface                             done

  Virtual machine monitor                                             done

  Bridged networking on /dev/vmnet0                                   done

  Host network detection                                              done

  DHCP server on /dev/vmnet1                                          done

  Host-only networking on /dev/vmnet1                                 done

  DHCP server on /dev/vmnet8                                          done

  NAT service on /dev/vmnet8                                          done

  Host-only networking on /dev/vmnet8                                 done

  Virtual ethernet                                                    done

$ sudo /etc/init.d/vmware start

Starting VMware services:

  Virtual machine monitor                                             done

  Virtual machine communication interface                             done

  Virtual ethernet                                                    done

  Bridged networking on /dev/vmnet0                                   done

  Host-only networking on /dev/vmnet1 (background)                    done

  DHCP server on /dev/vmnet1                                          done

  Host-only networking on /dev/vmnet8 (background)                    done

  DHCP server on /dev/vmnet8                                          done

  NAT service on /dev/vmnet8                                          done

  VMware Server Authentication Daemon (background)                    done

  Shared Memory Available                                             done

Starting VMware management services:

  VMware Server Host Agent (background)                               done

  VMware Virtual Infrastructure Web Access

Starting VMware autostart virtual machines:

Virtual machines                                                    done

Output from ifconfig and ps -ef |grep vmnet is given below.

Why isn't vmnet0 available after booting, and how can I make it so?

Thanks,

Chris.

$ ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:1e:0b:35:d5:12 

inet addr:10.1.1.2  Bcast:10.255.255.255  Mask:255.0.0.0

inet6 addr: fe80::21e:bff:fe35:d512/64 Scope:Link

UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

RX packets:1354 errors:0 dropped:0 overruns:0 frame:0

TX packets:1798 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:100

RX bytes:383251 (383.2 KB)  TX bytes:1126131 (1.1 MB)

Memory:f0500000-f0520000

lo        Link encap:Local Loopback 

inet addr:127.0.0.1  Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING  MTU:16436  Metric:1

RX packets:6225 errors:0 dropped:0 overruns:0 frame:0

TX packets:6225 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:4962948 (4.9 MB)  TX bytes:4962948 (4.9 MB)

pan0      Link encap:Ethernet  HWaddr 96:e2:2c:be:eb:c6 

BROADCAST MULTICAST  MTU:1500  Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmnet1    Link encap:Ethernet  HWaddr 00:50:56:c0:00:01 

inet addr:172.16.181.1  Bcast:172.16.181.255  Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link

UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:26 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmnet8    Link encap:Ethernet  HWaddr 00:50:56:c0:00:08 

inet addr:192.168.60.1  Bcast:192.168.60.255  Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:27 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

$ ps -ef |grep vmnet

root      2885     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid -n 0 -i eth0

root      2900     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet1.pid /dev/vmnet1 vmnet1

root      2911     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1

root      2927     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet8.pid /dev/vmnet8 vmnet8

root      2943     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8

root      2948     1  0 11:45 ?        00:00:00 /usr/bin/vmnet-natd -d /var/run/vmnet-natd-8.pid -m /var/run/vmnet-natd-8.mac -c /etc/vmware/vmnet8/nat/nat.conf

I'm stuck since 2 days trying to have my Graphic card working in a Vmware host.

Specifications:

- Vvmware ESXi 5.0.0 running on Windows

- Ubuntu 10.04 running on host

- Graphic card: AMD Radeon 6900 Series

- Everything in 64 bits

Useful output :

   #lspci -v

    03:00.0 VGA compatible controller: ATI Technologies Inc Cayman PRO [AMD Radeon 6900 Series]

    Subsystem: PC Partner Limited Device 186b

    Flags: bus master, fast devsel, latency 64, IRQ 18

    Memory at c0000000 (64-bit, prefetchable) [size=256M]

    Memory at b2420000 (64-bit, non-prefetchable) [size=128K]

    I/O ports at 4400 [size=256]

    Capabilities: [50] Power Management version 3

    Capabilities: [58] Express Endpoint, MSI 00

    Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

    Capabilities: [100] Vendor Specific Information <?>

    Capabilities: [150] Advanced Error Reporting <?>

    Kernel driver in use: fglrx_pci

    Kernel modules: fglrx

I'm starting my ubuntu in text mode.

I try to have OpenCL running in my VM. I tried a lot of various tutorials with ati-stream and so on and nothing works.

Then I followed [This][1]

After I did it I got this message at startup:

       dmesg|grep radeon

         [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.6  root=UUID=1b5bd568-6b7f-41c0-be1c-d69ae4f7e438 ro text splash  video=radeon:modeset=1

    [    0.000000]  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.6  root=UUID=1b5bd568-6b7f-41c0-be1c-d69ae4f7e438 ro text splash  video=radeon:modeset=1

    [    2.670567] [drm] radeon kernel modesetting enabled.

    [    2.671623] radeon 0000:03:00.0: enabling device (0000 -> 0003)

    [    2.672877] radeon 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18

    [    2.679567] radeon 0000:03:00.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)

    [    2.680456] radeon 0000:03:00.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)

    [    2.681299] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM

    [    2.682179] radeon 0000:03:00.0: Fatal error during GPU init

    [    2.683291] [drm] radeon: finishing device.

    [    2.693101] radeon 0000:03:00.0: PCI INT A disabled

    [    2.696322] radeon: probe of 0000:03:00.0 failed with error -22

So, I know that the passthrough is working since I can see my graphic card in my host but I can't make it work right.

Can anyone help me? Ask me if you need more information!

  [1]: http://www.backtrack-linux.org/forums/showthread.php?t=40213&page=2

When ever I ping something on the local LAN (or WAN), the replies are redirects from the HOST IP, then 4 duplicates of the reply packet from the correct IP. If I ping the host IP, they reply just fine. I am pretty sure something is wrong with the SBS nic and VMware bridge protocol.

The Host is SBS2008 64bit (i know its not supported, but it works at another site), Guest: CentOS 5.4 32bit.

Sample:

SBS: 192.168.1.10 (1 NIC, win firewall off)

CentOS: 192.168.1.9 (bridged)

Some other PC: 192.168.1.11

root@svr2:~ $ ping 192.168.1.10 (SBS)

PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.

64 bytes from 192.168.1.10: icmp_seq=1 ttl=128 time=0.169 ms

64 bytes from 192.168.1.10: icmp_seq=2 ttl=128 time=0.273 ms

64 bytes from 192.168.1.10: icmp_seq=3 ttl=128 time=0.323 ms

root@svr2:~ $ ping 192.168.1.11 (some pc)

PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data.

From 192.168.1.10: icmp_seq=1 Redirect Network(New nexthop: 192.168.1.11)

64 bytes from 192.168.1.11: icmp_seq=1 ttl=64 time=0.880 ms

64 bytes from 192.168.1.11: icmp_seq=1 ttl=63 time=0.951 ms (DUP!)

64 bytes from 192.168.1.11: icmp_seq=1 ttl=64 time=1.46 ms (DUP!)

64 bytes from 192.168.1.11: icmp_seq=1 ttl=63 time=1.46 ms (DUP!)

From 192.168.1.10: icmp_seq=2 Redirect Network(New nexthop: 192.168.1.11)

64 bytes from 192.168.1.11: icmp_seq=2 ttl=64 time=1.02 ms

64 bytes from 192.168.1.11: icmp_seq=2 ttl=63 time=1.13 ms (DUP!)

64 bytes from 192.168.1.11: icmp_seq=2 ttl=64 time=1.51 ms (DUP!)

64 bytes from 192.168.1.11: icmp_seq=2 ttl=63 time=1.51 ms (DUP!)

From 192.168.1.10: icmp_seq=3 Redirect Network(New nexthop: 192.168.1.11)

64 bytes from 192.168.1.11: icmp_seq=3 ttl=64 time=0.997 ms

64 bytes from 192.168.1.11: icmp_seq=3 ttl=63 time=1.09 ms (DUP!)

64 bytes from 192.168.1.11: icmp_seq=3 ttl=64 time=1.45 ms (DUP!)

64 bytes from 192.168.1.11: icmp_seq=3 ttl=63 time=1.45 ms (DUP!)

--- 192.168.1.11 ping statistics ---

3 packets transmitted, 3 received, +9 duplicates, 0% packet loss, time 3109ms

rtt min/avg/max/mdev = 0.849/1.187/1.445/0.220 ms

9 DUPLICATES!!! - What is that about?

Hi everybody

This post is not to send a question, but an answer !

Host OS : Windows XP SP3

I was using VMWare server 2.0 successfully for a while, when my company's laptop has to endure a rebuild.

Since this reformat, I was unable to start VMWare Host agent  , getting the sybilyn error :

VMWare Host agent fail to start 0x40000015 0x781346b4

Even after several uninstall/reinstall, datastores.xml check and so on ...

Finalyy, the trick to make this service running was simple :

My laptop is protected with Mcafee and Mcafee firewall was enable.

The workaround is to disable Mcafee firewall.

VMWare Host agent is then able to run.

I guess a more secure way is to add special permissions for VMWare services, in order of being able to have Mcafee firewall running AND VMware host service able to run normally ...

Hope this message can help some VMWare guests ...

Regards

Jean-Luc

Everyone has their favorite list of performance tweaks for the old 1.0 Server product.  MemTrimRate, pshare, etc.

Has anyone applied these tweaks to the 2.0 product?  Do they still help with performance?  Do they even still exist as tweaks?

I posted this question back in the RC2 forums and nobody ever responded.  Is nobody interested in improving VM performance under 2.0?

Not only that, but it seems vmware-mount has also vanished from VMware Server 2. The reason I'm looking for these is that I'm trying to port a backup script I wrote for VMware Server 2 wich stops, shrinks, copies and then starts a VM. Does anyone know if the new WMware Server 2 has any command line tools which can stop and start a VM, and shrink a VM?

Thanks

Did I miss something?  I used to down a VM and then mount its virtual disk in order to do a direct backup instead of a .vmdk backup.  That doesn't seem to be possible with VMware Server 2?  I even found and installed the Virtual Disk Development Kit, which got me vmware-mount back, but I get the following error:

Unable to mount the virtual disk. The disk may be in use by a virtual

machine, may not have enough volumes or mounted under another drive

letter. If not, verify that the file is a valid virtual disk file.

It definitely is not running (vmrun list shows 0 vm's running).  Interestingly, vmware-mount /p does show that the virtual disk has 1 volume.  Is this because VMware Server 2 upgrades the virtual hardware?  Do we have to change the command line similar to how vmware run was changed compared to the old vmware-cmd (using the storage notation instead of local drive/path)?