on a HP DL360 with RHAS3Updt9 and VMware server 1.0.3 installed, a VM W2K is used to establish a VPN (cisco) with a usb e-token (aladdin) authentification. The E-token seem be correctly saw but the VPN connexion abort.

My Problem : When I active USB in VM (VM/Removable Devices/USB Device/aks E-token Pro (0600) Port 1), vm log file show many error :

...

Aug 17 15:07:15: vcpu-0| MKS switching absolute mouse on

Aug 17 15:07:24: vmx| Msg_Hint: msg.usb.generic.stopDevice (not shown)

Aug 17 15:07:24: vmx| USB: Connecting device 0xe002000205290600

Aug 17 15:07:24: vmx| USB: Found device \[name:AKS\ eToken\ Pro\ 0600 vid:0529 pid:0600 path:2/0]

Aug 17 15:07:24: vmx| USB: Adding autoconnect pattern \[path:2/0 autoclean:1] in slot 0

Aug 17 15:07:24: vmx| USB: Found device \[name:AKS\ eToken\ Pro\ 0600 vid:0529 pid:0600 port:1 path:2/0]

Aug 17 15:07:24: vmx| USB: Device \[name:AKS\ eToken\ Pro\ 0600 vid:0529 pid:0600 port:1 path:2/0] should already be connected

Aug 17 15:07:24: vmx| VMXVmdbLoadUsbDevices: New set of 1 USB devices

Aug 17 15:07:24: vmx| UHCI: setup data size 56 does not match wLength 255

Aug 17 15:07:24: vmx| UHCI: setup data size 56 does not match wLength 255

Aug 17 15:07:24: vmx| UHCI: setup data size 56 does not match wLength 255

Aug 17 15:07:24: vmx| UHCI: setup data size 56 does not match wLength 255

Aug 17 15:07:24: vmx| UHCI: setup data size 56 does not match wLength 255

Aug 17 15:07:26: vmx| UHCI: setup data size 56 does not match wLength 139

Aug 17 15:07:26: vmx| UHCI: setup data size 56 does not match wLength 139

....

Aug 17 15:08:46: vmx| UHCI: setup data size 56 does not match wLength 139

Aug 17 15:08:47: vmx| UHCI: setup data size 56 does not match wLength 139

Aug 17 15:08:47: vmx| UHCI: setup data size 56 does not match wLength 139

Aug 17 15:10:47: mks| MKS set guest selection request with invalid state 2

Aug 17 15:31:29: mks| MKS set guest selection request with invalid state 2

Aug 17 15:31:52: mks| MKS set guest selection request with invalid state 2

Thanks for your help

Hello,

I have a RHEL4 WS guest running on a RHEL4 WS host (vm server).

The host has two e1000 interfaces up at 1000 FULL and bonded, the guest is bridged to this bonded interface via eth0 and vmxnet.

The issue occurs when I try to scp a 5GB file from a remote host, the guest network speed continually drops until after about 1GB is copied then the host system cpu load starts to shoot up until all my guest images and the host lock up and are unusable until I kill the scp session from the remote host, and everything returns back to normal.

Switch and interfaces are auto/auto, I have tried the pcnet32 and vmnics entries in modprobe.conf, removed all ipv6 configs, and this continues to happen.

I can copy large files to the host machine fine via the guest's bonded interface, so it appears to be something wrong in the guest image.

Looking at ifconfig on the guest machine shows minor errors on the interface:

eth0      Link encap:Ethernet  HWaddr 00:0C:29:36:A7:89 

          inet addr:192.168.99.245  Bcast:192.168.99.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

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

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

          collisions:0 txqueuelen:1000

          RX bytes:2289427914 (2.1 GiB)  TX bytes:39905716 (38.0 MiB)

          Interrupt:177 Base address:0x1424

Really not sure what the issue is here, no clues is dmesg, or messages, searched the forums, KB and google and I am stumped.   I really need to big able to copy large DB dumps to this image and I cannot...

Thanks for any ideas/assistance!

Hello,

after upgrading from VMWare Server 1.0.3 to 1.0.4 on Debian Etch I had serious errors in VMWare guests.

The Guests are running Debian Etch too.  They have one SCSI disk image with BusLogic adapter.

On boot I get strange errors:

sdb: READ CAPACITY failed

sd: current:  sense key: illegal request 

Additional sense: Invalid command operation code

sd: 0:0:1:0  scsi: device offlined - not ready after recovery

sd 0:0:1:0  SCSI error: return code 0x00030000

sdc: spinning up disk ....

And there it hangs for a while.

Strange is, that there is only one scsi disk configured. Why the kernel is suddenly "seeing" sdb and sdc I don't know. After downgrading to 1.0.3  everything works fine again, the kernel is correctly seeing only sda again.

Below is a sample vmx file

Regards,

haary

#!/usr/bin/vmware

config.version = "8"

virtualHW.version = "4"

scsi0.present = "TRUE"

memsize = "364"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "print.vmdk"

scsi0:0.writeThrough = "TRUE"

ide1:0.present = "TRUE"

ide1:0.fileName = "/var/VM/grml.iso"

ide1:0.deviceType = "cdrom-image"

floppy0.fileName = "/dev/fd0"

Ethernet0.present = "TRUE"

displayName = "print"

guestOS = "otherlinux"

priority.grabbed = "normal"

priority.ungrabbed = "normal"

powerType.powerOff = "hard"

powerType.powerOn = "hard"

powerType.suspend = "hard"

powerType.reset = "hard"

floppy0.present = "FALSE"

scsi0:0.redo = ""

ethernet0.addressType = "generated"

uuid.location = "56 4d 39 b1 86 e1 a4 97-d3 6f 25 9f 8b d7 e2 6f"

uuid.bios = "56 4d 39 b1 86 e1 a4 97-d3 6f 25 9f 8b d7 e2 6f"

ethernet0.generatedAddress = "00:0c:29:d7:e2:6f"

ethernet0.generatedAddressOffset = "0"

autostart = "poweron"

autostop = "softpoweroff"

ide1:0.startConnected = "TRUE"

tools.syncTime = "TRUE"

Hi,

I'm running vmware server 1.0.3 build-44356 (on Debian GNU/Linux, i386) and try to follow the -rc versions of the linux kernel and noticed the following messages in 2.6.23-rcX:

 RTNL: assertion failed at net/core/dev.c (2595)                 [<c0106a5a>] show_trace_log_lvl+0x1a/0x30                      [<c0107622>] show_trace+0x12/0x20                              [<c0107645>] dump_stack+0x15/0x20                              [<c0394592>] __dev_set_promiscuity+0xc2/0xd0                   [<c039492b>] dev_set_promiscuity+0x1b/0x40                     [<f91cb3db>] VNetBridgeStartPromisc+0x2b/0x50 [vmnet]          [<f91cb5fa>] VNetBridgePortsChanged+0x2a/0x40 [vmnet]          [<f91c9ae5>] VNetHubPortsChanged+0x65/0xd0 [vmnet]             [<f91c86aa>] VNetConnect+0x7a/0xb0 [vmnet]                     [<f91c929d>] VNetFileOpOpen+0xbd/0x170 [vmnet]                 [<c016b437>] chrdev_open+0x87/0x1a0                            [<c0167519>] __dentry_open+0x99/0x190                          [<c01676b5>] nameidata_to_filp+0x35/0x40                       [<c0167709>] do_filp_open+0x49/0x60                            [<c0167765>] do_sys_open+0x45/0x80                             [<c01677dc>] sys_open+0x1c/0x20                                [<c0105946>] sysenter_past_esp+0x6b/0xb5                       =======================                                      

This is also the case with 2.6.23.1 and vmware-any-any-update114 (Thanks, Petr!). While this message does nothing else bad (with 2.6.23.1, under -rc9 and with -any-any-update113, IIRC) networking of the guest stopped working), I wonder if this is something to look at. Maybe some vmware-guru wants to comment? Please see http://lkml.org/lkml/2007/9/2/125 for a comment from the netdev folks.

More details and my .config: http://nerdbynature.de/bits/2.6.23.1

Thanks,

Christian.

formatting fixes, thanks cshelton!

I'm getting error massage: Application failure.hr = 0x8004010b: Failed to initialize virtual machine. when I try to start VMware Server.

I'm running Win XP Pro on Toshiba Tecra and I don't have preference.ini file in C:\Documents and Settings\username\Application Data\VMware, this folder is empty, so I can't rename it like it was said in some previous discussion. I'm trying to find it with search but it does not exists.

What can I do? I had the same version of VMware Server instaled on my desktop computer whith XP Pro and there it worked just fine.

Thank you for answering.

We have exact the same problem as described in http://communities.vmware.com/thread/38988

Two network interfaces:

vmnet0: bond0.800

vmnet2: bond0.100

/dev/vmnet: open called by PID 21646 (vmnet-bridge)

/dev/vmnet: hub 0 does not exist, allocating memory.

/dev/vmnet: port on hub 0 successfully opened

bridge-bond0.80: peer interface bond0.80 not found, will wait for it to come up

bridge-bond0.80: attached

/dev/vmnet: open called by PID 21650 (vmnet-bridge)

/dev/vmnet: hub 2 does not exist, allocating memory.

/dev/vmnet: port on hub 2 successfully opened

bridge-bond0.10: peer interface bond0.10 not found, will wait for it to come up

bridge-bond0.10: attached

I've changed the example code in the previous thread to:

#include "vnet.h"

#include <stdint.h>

#include <sys/types.h>

#include <fcntl.h>

#include <net/if.h>

#include <linux/sockios.h>

#include <asm/ioctl.h>

int main(void) {

  u_int32_t flags = IFF_UP | IFF_PROMISC;

  char name[32] = "bond0.100";

  int fd = open("/dev/vmnet2", O_RDWR);

  ioctl(fd, SIOCSPEER2, name);

  ioctl(fd, SIOCSIFFLAGS, &flags);

  while (1) pause();

}

/code

Is there some other solution for this problem?

Hi,

in vmware server 1.0.3 on Win XP, when I start my virtual machine I have the following error message :

Virtual machine config file is invalid.

How can I investigate this problem ? Any log file some where ?

Many thanks.

Hello!

I'm working with VMWare Server 1.0.4, and I successfully created some virtual servers for our infrastructure.

I was asked to virtualize a file server: it has to be based on Windows 2003 Server and to manage about 3-400Gb of data. It won't use a SAN or NAS... my question is: which is the best solution to manage disk space? A single virtual disk? A raw partition?

Thanks!

Installed Ubuntu server & VMware server now I'm at the linux promt, I tried typing in "vmware-console", vmware, xconsole, etc. to no avail. How do I run the vmware console so I can create vm's?

When I create a new virtual machine, it allocates space on my hard drive which is now reserved for VMware server, guest operating system, application and data - right?  Suppose, for some reason (e.g. incorrect setup, sizing, etc.) I decide that this virtual machine can't be used, and I want to set up another virtual machine (correctly this time).  I'd want to remove the first virtual machine, thus freeing the allocated space.

Is this possible?  If so, how is this done?  If not, does this mean that the only solution would be to uninstall vmware server entirely, and start from scratch?

Thanks.

Mike

Recently set up an Endian VM and have it acting as my firewall/router for my home network.  I'm curious if anyone has ever tried to get VMware Tools installed on it?  It appears to be some flavor of Red Hat (uses RPMs).  I'm going to try to find some kernel headers, then finding gcc, make, etc. shouldn't be too difficult.

Or has this been tried and is not possible?

Thanks

Dear All,

I have researched this problem extensively before posting and have already attempted a few suggested solutions and have had to restore to the backup I made just before making the various attempts.

I am running VMware-server-1.0.6-91891 on CentOS 4.5 x86_64. It is not practical for me to upgrade to the latest version of vmware server 1 at this time due to this server running a large number of VMs all of which are in production. I am hoping there is a workaround that will resolve the issue.

I am attempting to revert a VM to snapshot that is running Windows Server 2003 Standard. The snapshot was taken some time ago the VM does currently boot. It is rather critical I be able to revert to this snapshot so any advice would be appreciated.

The errors that show up in /var/log/vmware-serverd.log when I attempt to revert are:

Apr 23 01:57:21: app| SP: Retrieved username: root

Apr 23 01:57:21: app| Error when reading from snhelper: Error:4:Unable to open snapshot file

Apr 23 01:57:21: app| VMHSVMCbVmxChkptState failed: ret = VMDB failure

Apr 23 01:57:21: app| VM suddenly changed state: poweredOff.

Apr 23 01:57:23: app| VmsdRegister: Config file has changed: /mnt/drives3-5/vms/SAI/Windows Server 2003 Standard Edition.vmx

Apr 23 01:57:23: app| VM suddenly changed state: poweredOff.

here are the contens of my .vmx file:

#!/usr/bin/vmware

config.version = "8"

virtualHW.version = "4"

numvcpus = "1"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "1024"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Windows Server 2003 Standard Edition-000001.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "/mnt/drives3-5/vms/mssql2005_disc2.iso"

ide1:0.deviceType = "cdrom-image"

floppy0.fileName = "/dev/fd0"

Ethernet0.present = "TRUE"

displayName = "SAI"

guestOS = "winnetstandard"

autostart = "poweron"

priority.grabbed = "normal"

priority.ungrabbed = "normal"

floppy0.startConnected = "FALSE"

workingDir = "."

scsi0:0.redo = ""

ethernet0.addressType = "generated"

uuid.location = "56 4d d0 b3 5b 78 08 ef-7e 7a 54 a8 3d df 3a 3c"

uuid.bios = "56 4d d0 b3 5b 78 08 ef-7e 7a 54 a8 3d df 3a 3c"

ethernet0.generatedAddress = "00:0c:29:df:3a:3c"

ethernet0.generatedAddressOffset = "0"

Ethernet0.connectionType = "custom"

Ethernet0.vnet = "/dev/vmnet2"

ide1:0.startConnected = "TRUE"

tools.syncTime = "FALSE"

Here are the contents of Windows Server 2003 Standard Edition.vmdk:

1. Disk DescriptorFile

version=1

CID=32d47620

parentCID=ffffffff

createType="twoGbMaxExtentSparse"

1. Extent description

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s001.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s002.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s003.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s004.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s005.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s006.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s007.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s008.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s009.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s010.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s011.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s012.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s013.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s014.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s015.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s016.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s017.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s018.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s019.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s020.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s021.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s022.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s023.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s024.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s025.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s026.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s027.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s028.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s029.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s030.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s031.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s032.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s033.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s034.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s035.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s036.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s037.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s038.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s039.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-s040.vmdk"

RW 81920 SPARSE "Windows Server 2003 Standard Edition-s041.vmdk"

1. The Disk Data Base

#DDB

ddb.toolsVersion = "6534"

ddb.adapterType = "lsilogic"

ddb.geometry.sectors = "63"

ddb.geometry.heads = "255"

ddb.geometry.cylinders = "10443"

ddb.virtualHWVersion = "4"

Here are the contents of Windows Server 2003 Standard Edition-000001.vmdk:

1. Disk DescriptorFile

version=1

CID=eeb5f8f8

parentCID=32d47620

createType="twoGbMaxExtentSparse"

parentFileNameHint="Windows Server 2003 Standard Edition.vmdk"

1. Extent description

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s001.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s002.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s003.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s004.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s005.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s006.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s007.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s008.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s009.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s010.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s011.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s012.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s013.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s014.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s015.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s016.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s017.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s018.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s019.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s020.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s021.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s022.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s023.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s024.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s025.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s026.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s027.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s028.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s029.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s030.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s031.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s032.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s033.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s034.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s035.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s036.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s037.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s038.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s039.vmdk"

RW 4192256 SPARSE "Windows Server 2003 Standard Edition-000001-s040.vmdk"

RW 81920 SPARSE "Windows Server 2003 Standard Edition-000001-s041.vmdk"

1. The Disk Data Base

#DDB

ddb.toolsVersion = "6534"

Here is a listing of files in the directory:

-rwxrwxrwx  1 root root       8664 Apr 23 01:56 nvram

-rwxrwxrwx  1 root root     401648 Apr 23 00:33 vmware-0.log

-rwxrwxrwx  1 root root      41508 Jan 17 04:17 vmware-1.log

-rwxrwxrwx  1 root root     198917 Dec  6 01:25 vmware-2.log

-rwxrwxrwx  1 root root      34603 Apr 23 01:56 vmware.log

-rwxrwxrwx  1 root root  146145280 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s001.vmdk

-rwxrwxrwx  1 root root  453115904 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s002.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s003.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s004.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s005.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s006.vmdk

-rwxrwxrwx  1 root root  168296448 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s007.vmdk

-rwxrwxrwx  1 root root  535494656 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s008.vmdk

-rwxrwxrwx  1 root root  541196288 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s009.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s010.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s011.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s012.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s013.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s014.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s015.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s016.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s017.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s018.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s019.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s020.vmdk

-rwxrwxrwx  1 root root     655360 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s021.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s022.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s023.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s024.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s025.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s026.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s027.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s028.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s029.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s030.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s031.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s032.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s033.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s034.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s035.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s036.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s037.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s038.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s039.vmdk

-rwxrwxrwx  1 root root     327680 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s040.vmdk

-rwxrwxrwx  1 root root      65536 Apr 23 01:56 Windows Server 2003 Standard Edition-000001-s041.vmdk

-rwxrwxrwx  1 root root       3269 Apr 23 01:55 Windows Server 2003 Standard Edition-000001.vmdk

-rwxrwxrwx  1 root root 2143158272 Sep  2  2008 Windows Server 2003 Standard Edition-s001.vmdk

-rwxrwxrwx  1 root root 1099366400 Sep  2  2008 Windows Server 2003 Standard Edition-s002.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s003.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s004.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s005.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s006.vmdk

-rwxrwxrwx  1 root root  225902592 Sep  2  2008 Windows Server 2003 Standard Edition-s007.vmdk

-rwxrwxrwx  1 root root 1602748416 Sep  2  2008 Windows Server 2003 Standard Edition-s008.vmdk

-rwxrwxrwx  1 root root  250150912 Sep  2  2008 Windows Server 2003 Standard Edition-s009.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s010.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s011.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s012.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s013.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s014.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s015.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s016.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s017.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s018.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s019.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s020.vmdk

-rwxrwxrwx  1 root root    1114112 Sep  2  2008 Windows Server 2003 Standard Edition-s021.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s022.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s023.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s024.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s025.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s026.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s027.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s028.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s029.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s030.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s031.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s032.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s033.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s034.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s035.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s036.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s037.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s038.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s039.vmdk

-rwxrwxrwx  1 root root     327680 Sep  2  2008 Windows Server 2003 Standard Edition-s040.vmdk

-rwxrwxrwx  1 root root     131072 Sep  2  2008 Windows Server 2003 Standard Edition-s041.vmdk

-rwxrwxrwx  1 root root 1073741824 Sep  2  2008 Windows Server 2003 Standard Edition-Snapshot1.vmem

-rwxrwxrwx  1 root root   17899508 Sep  2  2008 Windows Server 2003 Standard Edition-Snapshot1.vmsn

-rwxrwxrwx  1 root root       3064 Aug  9  2008 Windows Server 2003 Standard Edition.vmdk

-rwxrwxrwx  1 root root        503 Sep  2  2008 Windows Server 2003 Standard Edition.vmsd

-rwxrwxrwx  1 root root        991 Apr 23 01:54 Windows Server 2003 Standard Edition.vmx

I have checked file permissions, I have attempted to change the filename in the .vmx file to the prior file and various other actions described in other threads with no positive results.

I am hoping someone has an idea of how this can be corrected so I can revert to this snapshot.

I have reverted other VMs on this same server to their snapshots but not for a few months.

This VM is configured with bridged networking.

Note that the vmware.log file in the VM's directory is not updated when attempting to revert to this snapshot.

Additional entries in vmware-serverd.log that may be of interest from the first attempt at this snapshot reversion:

Apr 23 00:33:30: app| VMServerd IPC closed the connection with thread /mnt/drive

s3-5/vms/SAI/Windows Server 2003 Standard Edition.vmx (0x8301c40)

Apr 23 00:33:30: app| Lost connection to /mnt/drives3-5/vms/SAI/Windows Server 2

003 Standard Edition.vmx (/mnt/drives3-5/vms/SAI/Windows Server 2003 Standard Ed

ition.vmx) unexpectedly.

Apr 23 00:33:30: app| cleanup: cleaned up 1 objects

Apr 23 00:33:30: app| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF

Apr 23 00:33:30: app| VM suddenly changed state: poweredOff.

Apr 23 00:33:30: app| Removing from running vm list: /mnt/drives3-5/vms/SAI/Wind

ows Server 2003 Standard Edition.vmx

Apr 23 00:33:31: app| VM suddenly changed state: poweredOff.

Apr 23 00:33:31: app| VM suddenly changed state: poweredOff.

Apr 23 00:33:31: app| VM suddenly changed state: poweredOff.

Apr 23 01:05:33: app| Adding to list of running vms: /mnt/drives3-5/vms/SAI/Wind

ows Server 2003 Standard Edition.vmx

Apr 23 01:05:33: app| Attempting to launch vmx : /mnt/drives3-5/vms/SAI/Windows

Server 2003 Standard Edition.vmx

Apr 23 01:05:34: app| New connection on socket server-vmxvmdb from host localhos

t (ip address: local) , user: root

Apr 23 01:05:34: app| Connection from : /mnt/drives3-5/vms/SAI/Windows Server 20

03 Standard Edition.vmx

Apr 23 01:05:34: app| Setting up autoDetect info.

Apr 23 01:05:34: app| VMServerdConnect: connecting to /mnt/drives3-5/vms/SAI/Win

dows Server 2003 Standard Edition.vmx

Apr 23 01:05:36: app| Connected to /mnt/drives3-5/vms/SAI/Windows Server 2003 St

andard Edition.vmx

Apr 23 01:05:36: app| cleanup: cleaned up 1 objects

Apr 23 01:05:36: app| VM suddenly changed state: poweredOn.

Apr 23 01:06:06: app| VmsdRegister: Config file has changed: /mnt/drives3-5/vms/

SAI/Windows Server 2003 Standard Edition.vmx

Apr 23 01:07:21: app| SP: Retrieved username: root

Apr 23 01:07:22: app| VMServerd IPC closed the connection with thread /mnt/drive

s3-5/vms/SAI/Windows Server 2003 Standard Edition.vmx (0x8301c40)

Apr 23 01:07:22: app| Lost connection to /mnt/drives3-5/vms/SAI/Windows Server 2

003 Standard Edition.vmx (/mnt/drives3-5/vms/SAI/Windows Server 2003 Standard Ed

ition.vmx) unexpectedly.

Apr 23 01:07:22: app| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF

Apr 23 01:07:22: app| VM suddenly changed state: poweredOff.

Apr 23 01:07:22: app| VMDB OP FAIL:

Apr 23 01:07:22: app| Backtrace:

Apr 23 01:07:22: app| Backtrace[0] 0xffffc738 eip 0x807a5de

Apr 23 01:07:22: app| Backtrace[1] 0xffffca78 eip 0x812385e

Apr 23 01:07:22: app| Backtrace[2] 0xffffce08 eip 0x81d5a00

Apr 23 01:07:22: app| Backtrace[3] 0xffffce18 eip 0x81cbe16

Apr 23 01:07:22: app| Backtrace[4] 0xffffcfb8 eip 0x8122dca

Apr 23 01:07:22: app| Backtrace[5] 0xffffd018 eip 0x813a729

Apr 23 01:07:22: app| Backtrace[6] 0xffffd038 eip 0x80e3137

Apr 23 01:07:22: app| Backtrace[7] 0xffffdca8 eip 0x80e343e

Apr 23 01:07:22: app| Backtrace[8] 0xffffdce8 eip 0x80e27f8

Apr 23 01:07:22: app| Backtrace[9] 0xffffdd08 eip 0x80e28c8

Apr 23 01:07:22: app| Backtrace[10] 0xffffdd38 eip 0x80791d4

Apr 23 01:07:22: app| Backtrace[11] 0xffffdd58 eip 0x8078455

Apr 23 01:07:22: app| Backtrace[12] 0xffffddb8 eip 0x502de3

Apr 23 01:07:22: app| Backtrace[13] 00000000 eip 0x8078271

Apr 23 01:07:22: app| Vmdb_Unset failed: /vm/#5b90bd8dd2db8ac5/vmx/chkptState/re

q/#14b/ (Pipe connection has been broken)

Apr 23 01:07:22: app| Removing from running vm list: /mnt/drives3-5/vms/SAI/Wind

ows Server 2003 Standard Edition.vmx

Apr 23 01:07:23: app| VM suddenly changed state: poweredOff.

Apr 23 01:07:23: app| VM suddenly changed state: poweredOff.

Apr 23 01:07:23: app| VM suddenly changed state: poweredOff.

Apr 23 01:07:23: app| SP: Retrieved username: root

Apr 23 01:07:23: app| Error when reading from snhelper: Error:4:Unable to open s

napshot file

Apr 23 01:07:23: app| VMHSVMCbVmxChkptState failed: ret = VMDB failure

Apr 23 01:07:23: app| VM suddenly changed state: poweredOff.

Apr 23 01:07:23: app| cleanup: cleaned up 1 objects

Apr 23 01:07:33: app| VM suddenly changed state: poweredOff.

Thanks in advance

Dear All,

        I want to install vmware server console to do Oracle RAC practice, So kindly let me know from where can I get the exe file to install it.

       FYI , I installed Vmware server version2.0.2 but it's ( Web access infrastructure )  , and I don't want this version , I need the other one which it's an application not the web based.

Regards

Hi,

I am running VMWare on a pc with Zone Alarm Installed.  Everything works correctly when Zone Alarm is disabled.  However, when I enable Zone Alarm on my host PC the Virtual Machine is no longer able to access the internet.  Does anyone know what settings/changes I need to make in Zone Alarm?  On the Virtual Machine?

Thanks advance for your help!!!

I'm trying to install Server 1.02 under Vista x64. Unfortunately after a while the install suddenly starts "rolling back action" ending up with

Installation Wizard Completed

The wizard was interrupted before the VMware Server components could be completely installed.

I guessed some manual cleanup was in order, so I removed \program files(x86)\vmware & checked for vmware registry entries under HKLM\Software (inc. wow64node) but this obviously wasn't good enough.

What else should I check / is there a vmware "cleaner" around?

Please help!

I need to connect to remote networks through VPN. But I can't get a guest to work, with CheckPoint SecureClient VPN-1.

Host:      Windows 2003 Server

Guest1:  XP SP2 with Nortel VPN client, works great

Guest2:  XP SP2 with AT&T VPN client, works great

Guest3:  XP SP2 with CheckPoint SecureClient VPN-1 R55, VPN can't communicate with the host. Rest functions, like Internet works fine. I have searched the forum and couldn't find an answer. Please help!

On another PC with XP SP2 in the same subnet, I installed the same CheckPoint client and it works just fine.

i'm wondering if anyone has found an upper limit to the number of vms that you can run on the free vmware server on Windows.  Currently we are unable to fully utilize a quad dual core  server with 32 GB of RAM.  Yes I realize we should be running ESX, but need to have same type of VMware environment between test and prod.  Seems like the 20 machine mark, that they generally don't seem very responsive.  We've tried tweaking settings for memory etc, but it seems to not have any effect.  On startup ....the vms are all speedy. But after 15-20 minutes...seems like all the VMs are generally unresponsive or very slow.

thoughts????

I have a brand new HP "Intel Xeon 64 bit" server running windows 2003 32 bit OS. Can I use the free version of VMware server to run a 64bit guest OS of Windows 2003 server?

Thanks in advance for your help

Alan

Hello all,

I configured a vpn connection from a host Windows 2003 server  to a RRAS server. I try to bridge this vpn connection with Virtual Network Editor but it does not appear in the list. In the Vpn properties, VMware bridge procol is select but it isn't possible to affect a vmnet number.

Is it a limitation of vmware server ?

Any help is welcome,

Thanks

Yves

I am running 1.0.4 on Ubuntu 7.10 64-bit and have experienced an odd little problem two or three times in the last week.

vmnet0 is bridged onto my internal LAN, vmnet2 is bridged onto my DMZ Network.

What happens is, all of the machines suddenly lose internet access - each host is configured with two Ethernet Devices, one bridging to vmnet0, one to vmnet2.

When this happens, the host still has access to both Networks, so it's not a physical NIC thing - if I stop my VMs and restart vmware, everything goes back to normal.

This problem only affects the DMZ connected network (vmnet2), not the Internal LAN one (vmnet0)

Where do I start troubleshooting this one?