I have VMWare Server running on Windows 7 64-bit host. I built a CentOS55 vm and installed zimbra mailserver. All went fine. I have my vnic set to Bridged (vmnet0). I have given my zimbra server a static IP address of 192.168.1.55. The server can reach the net/send mail out. The server cannot get mail in. Port 25 is blocked. Initially I blamed by ISP, Comcast for blocking port 25, and after a big mess have my MX pointing to dnsexit which then is configured to forward the mail to my zimbra server on port 26. On the zimbra vm, telneting to localhost port 26 works. On my local lan from my win7 and other non-virtual machines, telneting to port 26 works. From the outside world, telneting to port 26 fails, just as it did when I had it sitting on port 25. I have a linksys WRT54G wireless router. It has port forwarding set up to forward port 26 to 192.168.1.55 (my zimbra vm). The linksys router can ping the host 192.168.1.55. (It doesnt have the tools to test addl ports via a telnet connection.) For testing purposes, Ive disabled all firewalls on my Win7 host.

I have other port forwarding set up in the router to the physical win7 box, and those ports redirect fine. Redirecting to the VM just doesnt work.

I decided to power off the vm, and configure the nic as NAT instead of bridged. Once I did that and rebooted the vm, the vm wouldnt come up. It hung.

I really dont want to tear apart the whole vm and rebuild. Seems silly. Why doesnt port forwarding from the router to the bridged vmnet0 work?

Hi,

after a power failure, we have this issue on our vmware server..

We have installed 7 virtual machines, only 2 of them are now recognized and running.

for the other 5, we get an "configuration file cannot be found" error, and they are shown as

"Unknown (Inaccessible)"

"Unknown 1 (Inaccessible)"

"Unknown 2 (Inaccessible)"

"Unknown 3 (Inaccessible)"

"Unknown 4 (Inaccessible)"

instead of their proper names ...

Any suggestions ?

I've been banging my head against the wall for nearly a week now, trying to get external access to my VMware LAN. Let me start out by explaining what I have.

First, I am running VMware Server 2.0.2 on a Windows Server 2008 box with a USB wireless adapter. Firewall is turned off. I have two guest servers:

DC1 has one virtual NIC (host-only on vmnet1) in a WIndows Server 2008 machine. It is a domain controller with AD integrated DNS. Firewall is turned off. TCP/IP is configured like this:

IP Address: 192.168.91.51

Subnet: 255.255.255.0

GW: 192.168.91.53

DNS: 127.0.0.1

RRAS has two virtual NICs (NIC1 is host-only on vmnet1 and NIC2 is bridged on vmnet0). It is a member server with RRAS installed, configured as a LAN router only. Firewall is turned off. TCP/IP is like this:

NIC1

IP Address: 192.168.91.53

Subnet: 255.255.255.0

GW:

DNS: 192.168.91.51

NIC2

IP Address: 192.168.254.107 (DHCP)

Subnet: 255.255.255.0

GW: 192.168.254.1

DHCP Server: 192.168.254.1

DNS: Provided by ISP

Now for the symptoms:

DC1 can ping both RRAS NICs, but cannot ping anything past it, nor can it ping the gateway (192.168.254.1). RRAS has full communication to the internet and all computers on the 192.168.254.0 network.

Since I've been hacking away at this problem for a while, I'm obviously missing something. The first step to troubleshooting is to verify all the facts (Trust, but verify <-- my favorite Ronald Reagan quote), so feel free to ask anything, even if it seems trivial.

Thanks for your help

Hi,

I want to move a currently working VM from one host to another.

The details are:

1. Both hosts are running Vmware Server 2 their hardware specs are different.

2. I created the VM using VMware Server 2.

3. The VM has 4 snapshots.

I stopped the VM and then copied all its folder contents to the target host.

When I tried to add the VM to the inventory in the target host I recieved the following error:

(The selected virtual machine is not recognized on this system. The cause of this problem may be that the virtual machine's .vmx file is corrupted, or that the virtual machine version is newer than is recognized by the host. You can remove the virtual machine from the inventory if you believe that it is not recoverable.Click the link below to remove the virtual machine from the inventory.Remove Virtual MachineTo help diagnose the issue, you can check the virtual machine files at their last known location)

I read a discussion of the same issue and I found that .vmx and .vmdk files of the VM has a different encoding than the target host, So I changed the encoding in these files to be the same as a working VM in the target machine.

The discuusion URL is: http://communities.vmware.com/message/1137795

But, i still recieve the same error.

Should I do any other thing because of having snapshots? In general in case of snapshots should I delete them all first before moving the VM?

Please help ASAP.

Thanks

I have a recurring problem with VMware Server.

The host server is Windows 2008 R2 x64 and the VMs are stored in a datastore hosting on a separate server running Windows 2008 Standard.

If the host server is rebooted without the VMs having been shutdown, upon the host server rebooting I am unable to start any of the VMs.  I get a message that an error has occurred, and that the file handle for the .vmdk is invalid.

I can browse to the share to which the datastore is mapped, and the permissions are correct, as the VMs work fine before the host server is rebooted.

I have tried deleting the .lck files/folders - didn't work.

I have tried removing/readding the VMs in the inventory - didn't work.

The only thing I've found that works is to create a new folder on the remote server, copy the folders to it, create a new datastore on the host server, add the VMs to the inventory from the new datastore, and then they will start with no problem (after indicating at the behest of VMware Server's query that they were copied).

Any idea why this happens, and if there is a better solution that creating a new datastore each time this happens?

Thank you in advance.

I am trying to setup a test lab on a R410 running vmware server. My goal is to have multiple networks connected via a virtual

router running Win 2008 R2 and RRAS router software. The physical box has a single NIC connected to a linksys router which

is connected to a Comcast Cable modem for Internet access. My ultimate goal is to setup exchange 2010 in two sites or multiple

forests.

In Vmserver, I have three VM's. The first is a router running Win 2008 R2 with RRAS installed. It has three NIC's, one bridged to connect to

the internet, and two host only nics where each is on its own switch, vmnet 1 and vmnet 3. The other two VM's are Win 2008 R2 servers

with each connected to one of the host only NIC's. Without the router software running, host1 can ping the router machine and host2 can ping

the router machine but host1 cannot ping host2 and vice versa.

Once I got the router software running on the Router VM, I am able to ping host1 from host2 and vice versa. I am also able to ping yahoo.com

from host1 and host2. I am also able to run rdp on host1 to connect to host2 and vice versa. I added a static route on the linksys wireless router

so I would be able to rdp into those private hosts from external computers on my home network and that works.

Unfortuantly, I cannot browse yahoo.com nor telnet into port 25 on our external email server at work but I can ftp to ftp.microsoft.com and ping

machines out on the internet. Is there a solution besides adding a bridge NIC to the net from my private network? Why can't I browse?

Thanks,

Sean Coleman

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?

UBUNTU 10.10

Linux Kernel 2.6.35-31-generic-pae

Always used standard vmtools not open-vm-tools.

We have several ubuntu linux servers that are not upgrading properly after the last ESXi updates to the hosts prompted a new tools version. They worked fine with 8.3.7, but now when the installers run I get a GRUB error on reboot and the GUI is all scrambled. Some of the users need the GUI so that is why it is needed. Do you think this is a problem with initrd after tools compiles it?

I built a new server using the 10.10 iso image and did the new tools install [this new server never had the older version of tools on it - so this may be why it works] and it worked with the gui installed. Can anyone give advice as to why existing servers can't upgrade? 

I have attached a photo of the GRUB error on reboot.

I have attached a photo of the GUI all squiggly -- probably because xorg is not working right.

I've tried uninstalling gnome-common, gnome-utils, gdm, ubuntu-desktop and fluxbox. When re-installed it results in the same squiggly gui.

Also during the vmtools install, Xorg complains about not being able to find vmwlegacy_drv.so, even when it is in the /usr/lib/xorg/modules/drivers folder.

I am running out of things to try. Does anyone have suggestions?

I have a Blackberry enterprise server, running in Windows 2003 SP2, running on VMWare Server2. When doing a snapshot backup using AppAssure Replay4 application I am getting the following error in the Windows event viewer:

Thread: 5604

Logger: tevolib.tpalt

Context: PG=VolsWithInterval720Minutes Volume=\\?\Volume{54531876-fe55-11db-8f46-00188b19c44c}\ DriveLetter=G:

Source Location: TransmitPacketsAlternative.cpp:584

Details:

Transmission of snapshot data failed. Check the AppAssure event log on the Replay Core for more details. - The drive cannot find the sector requested.

The last statement says the drive cannot find the sector requested. It is a virtual machine, it has no physical drives. What does this error mean?

During Host Profile configuration I have the following error:

"DNS configuration doesn't match the specification".

I read the followind link http://communities.vmware.com/thread/345272 but it does not correct the problem.

Can someone hav ethe same problem? What can I do?

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

i'm in the process of spec'ing new hardare for a virtualization server for home. decied on ESXi for the OS.

some graphics intensive games will be on windows guests and some on linux guests.

as for a graphics card, when my notebooks connect to any of the guests  will a really good graphics card be able to be used by the guests and thus display well via the the remote access?

Hi all

Situation looks as follows:

- I have destop Dell - Ultra Small Form Factor -  with 8GB RAM and 32bit Windows 7 installed

- on that desktop VMware serwer 2.0.2 is installed

- on that VMware serwer Windows 2008 R2 64bit is installed and configured with 1GB RAM.

My question is:

Is virtual machine able to use about or more than 4GB RAM from installed 8GB on the 32bit Windows 7 host system?

- or should i have 64bit host system to use about 4GB or 5GB on the virtual machine?

Thnaks in advance

--

Artur Dębski

http://blogit.one.pl

http://www.amt.pl

Dear All,

i managed to install Vmware server 2 on centos 5.9, however i am able to connect to the web interface after 10 second it kicks me off and comes with error!

can someone please explain how to fix this?

the server could not complete a request http 0 the server encountered an unexpected condition that prevented it from fulfilling...

I have a VM on a portable drive.  To add the VM to inventory, I had to create a datastore that points to the portable drive.  On bootup of the server, the portable drive is not connected but is plugged into the USB port as needed.  VMWare Server 2 doesn't recognize that datastore unless the drive is plugged in at boot up time.

If, after plugging in the portable drive, I try to execute a remote console shortcut to that VM, I get this error:

"The attempted operation cannot be performed in the current state (Powered Off)".

If I open the admin console page after plugging in the portable drive, the inventory for this VM says "Unknown (Inaccessible)".

If I remove the VM from inventory in the hopes of re-adding it.  When I try to re-add the VM, the Datastore for the portable drive is listed but when I click to open the datastore the Contents column says:

"The Datastore Browser could not successfully retrieve data from the server."

I then  tried simply double-clicking the VMX file for the VM.  There was no file association in Windows so I didn't pursue this further yet.

My next thought was to remove and re-add the datastore, forcing VMWare Server to see the portable drive (I am able to browse the drive in Windows Explorer).  I cannot find any way to remove a Datastore from the list.  When I try to re-add the Datastore, I get an error that it is the same name.  I could possibly add the Datastore using a different name but since there doesn't seem to be a way to delete them once created, I didn't want to try that yet.

So there are four problems/questions that I have:

1.  Is there a way to refresh the inventory list within the web based admin page?

2.  In VMWare Server 1.x, I could simply double-click a VMX file and it would add to inventory.  This didn't work inVMWare Server 2.  There was no file association in Windows.  Is it possible to fix this?

3.  Is there a way to refresh the Datastore contents?

4.  Is there a way to delete a Datastore that is no longer wanted or used?

The only thing that worked was to reboot the server with the portable drive connected.  This is not always a desirable procedure.

Thanks,

Dale

Message was edited by: dalepres

VMware Server 2.0.1 and latest RHEL5 kernel (both host & guest) = RANDOM REBOOTS !

I have VMware Server 2.0.1 running on CentOS 5.3 (x64 kernel-2.6.18-128.2.1.el5).

Lately I started experiencing random reboots of host and had to investigate it a bit.

At first I suspected hardware problems and specificly RAM corruption. 24h memtest86+ and no errors.

I had my guests migrated to another VMware-server 2.0.1 running on FC11 (2.6.29.6-213.fc11.x86_64).

No more host reboots but the guests (CentOS 5.3 x86 2.6.18-128.2.1.el5) still keep random rebooting.

Had a look at the guest logs and found this:

-

Aug 01 11:08:40.120: Worker#1| Caught signal 6 -- tid 5362

Aug 01 11:08:40.120: Worker#1| SIGNAL: eip 0x369b0332f5 esp 0x7fa1e0b01d88 ebp 0x2

Aug 01 11:08:40.120: Worker#1| SIGNAL: eax 0x0 ebx 0x369b132efe ecx 0xffffffffffffffff edx 0x6 esi 0x14f2 edi 0x14ed

Aug 01 11:08:40.120: Worker#1| r8 0x2c55020 r9 0x3 r10 0x8 r11 0x3206 r12 0xa57c9a000 r13 0x10000 r14 0x284f4d0 r15 0x7fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01D88 : 0x9b034b20 0x00000036 0x00000000 0x00000000

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01D98 : 0x00000000 0x00000000 0x00000000 0x00000000

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DA8 : 0x00000000 0x00000000 0x00000000 0x00000000

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DB8 : 0x00003000 0x00000000 0x9b369e80 0x00000036

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DC8 : 0x00010000 0x00000000 0x9b369e80 0x00000036

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DD8 : 0x00010010 0x00000000 0xe0b01f20 0x00007fa1

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DE8 : 0x00000000 0x00000000 0x9b369ee8 0x00000036

Aug 01 11:08:40.120: Worker#1| SIGNAL: stack 7FA1E0B01DF8 : 0x9b077f32 0x00000036 0x00000000 0x00000000

Aug 01 11:08:40.120: Worker#1| Backtrace:

Aug 01 11:08:40.120: Worker#1| Backtrace[0] 00007fa1e0b01830 rip=000000000041521c rbx=0000000000000000 rbp=0000000000415500 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.120: Worker#1| Backtrace[1] 00007fa1e0b01850 rip=0000000000468cf5 rbx=0000000000000080 rbp=0000000000000006 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.120: Worker#1| Backtrace[2] 00007fa1e0b01940 rip=000000369bc0ee90 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[3] 00007fa1e0b01d88 rip=000000369b0332f5 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[4] 00007fa1e0b01d90 rip=000000369b034b20 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[5] 00007fa1e0b01ec0 rip=000000369b075a50 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[6] 00007fa1e0b01f00 rip=000000000047eb93 rbx=0000000000000000 rbp=0000000002c55020 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.120: Worker#1| Backtrace[7] 00007fa1e0b01f70 rip=000000000054cc9b rbx=000000000274ebd0 rbp=000000000274ed50 r12=0000000000000001 r13=000000000000000c r14=0000000000000000 r15=ffffffffffffffff

Aug 01 11:08:40.120: Worker#1| Backtrace[8] 00007fa1e0b01f90 rip=00000000004f165d rbx=000000000274ed80 rbp=000000000274ed50 r12=0000000000000001 r13=000000000000000c r14=0000000000000000 r15=ffffffffffffffff

Aug 01 11:08:40.120: Worker#1| Backtrace[9] 00007fa1e0b01fe0 rip=00000000004f186c rbx=000000000274ed80 rbp=000000000274ed50 r12=0000000000000000 r13=00000000027f4244 r14=0000000000edfca0 r15=0000000000000003

Aug 01 11:08:40.120: Worker#1| Backtrace10 00007fa1e0b02010 rip=000000000048542a rbx=0000000000ee0c08 rbp=0000000000000000 r12=00007fff609f6b50 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.120: Worker#1| Backtrace11 00007fa1e0b02110 rip=000000369bc0686a rbx=0000000000000000 rbp=0000000000000000 r12=00007fff609f6ad0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.120: Worker#1| Backtrace12 00007fa1e0b02220 rip=000000369b0de25d rbx=00007fa1e0b02910 rbp=0000000000000000 r12=00007fff609f6ad0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.120: Worker#1| SymBacktrace[0] 00007fa1e0b01830 rip=000000000041521c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.120: Worker#1| SymBacktrace[1] 00007fa1e0b01850 rip=0000000000468cf5 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.120: Worker#1| SymBacktrace[2] 00007fa1e0b01940 rip=000000369bc0ee90 in function (null) in object /lib64/libpthread.so.0 loaded at 000000369bc00000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[3] 00007fa1e0b01d88 rip=000000369b0332f5 in function gsignal in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[4] 00007fa1e0b01d90 rip=000000369b034b20 in function abort in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[5] 00007fa1e0b01ec0 rip=000000369b075a50 in function (null) in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[6] 00007fa1e0b01f00 rip=000000000047eb93 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[7] 00007fa1e0b01f70 rip=000000000054cc9b in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[8] 00007fa1e0b01f90 rip=00000000004f165d in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace[9] 00007fa1e0b01fe0 rip=00000000004f186c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace10 00007fa1e0b02010 rip=000000000048542a in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.121: Worker#1| SymBacktrace11 00007fa1e0b02110 rip=000000369bc0686a in function (null) in object /lib64/libpthread.so.0 loaded at 000000369bc00000

Aug 01 11:08:40.121: Worker#1| SymBacktrace12 00007fa1e0b02220 rip=000000369b0de25d in function clone in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.121: Worker#1| Unexpected signal: 6.

Aug 01 11:08:40.121: Worker#1| Panic: can't get userlevel lock.

Aug 01 11:08:40.121: Worker#1| Core dump limit is 0 KB.

Aug 01 11:08:40.139: Worker#1| Child process 13550 failed to dump core (status 0x6).

Aug 01 11:08:40.139: Worker#1| Backtrace:

Aug 01 11:08:40.139: Worker#1| Backtrace[0] 00007fa1e0b01350 rip=000000000041521c rbx=0000000000000000 rbp=0000000000415500 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.139: Worker#1| Backtrace[1] 00007fa1e0b01370 rip=00000000004db650 rbx=00007fa1e0b01880 rbp=0000000000000006 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.139: Worker#1| Backtrace[2] 00007fa1e0b01850 rip=0000000000468ea8 rbx=00007fa1e0b01880 rbp=0000000000000006 r12=0000000000000000 r13=00007fa1e0b01940 r14=0000000000000025 r15=0000000000000006

Aug 01 11:08:40.139: Worker#1| Backtrace[3] 00007fa1e0b01940 rip=000000369bc0ee90 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[4] 00007fa1e0b01d88 rip=000000369b0332f5 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[5] 00007fa1e0b01d90 rip=000000369b034b20 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[6] 00007fa1e0b01ec0 rip=000000369b075a50 rbx=000000369b132efe rbp=0000000000000002 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[7] 00007fa1e0b01f00 rip=000000000047eb93 rbx=0000000000000000 rbp=0000000002c55020 r12=0000000a57c9a000 r13=0000000000010000 r14=000000000284f4d0 r15=00007fa1e0b01f20

Aug 01 11:08:40.139: Worker#1| Backtrace[8] 00007fa1e0b01f70 rip=000000000054cc9b rbx=000000000274ebd0 rbp=000000000274ed50 r12=0000000000000001 r13=000000000000000c r14=0000000000000000 r15=ffffffffffffffff

Aug 01 11:08:40.139: Worker#1| Backtrace[9] 00007fa1e0b01f90 rip=00000000004f165d rbx=000000000274ed80 rbp=000000000274ed50 r12=0000000000000001 r13=000000000000000c r14=0000000000000000 r15=ffffffffffffffff

Aug 01 11:08:40.139: Worker#1| Backtrace10 00007fa1e0b01fe0 rip=00000000004f186c rbx=000000000274ed80 rbp=000000000274ed50 r12=0000000000000000 r13=00000000027f4244 r14=0000000000edfca0 r15=0000000000000003

Aug 01 11:08:40.139: Worker#1| Backtrace11 00007fa1e0b02010 rip=000000000048542a rbx=0000000000ee0c08 rbp=0000000000000000 r12=00007fff609f6b50 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.139: Worker#1| Backtrace12 00007fa1e0b02110 rip=000000369bc0686a rbx=0000000000000000 rbp=0000000000000000 r12=00007fff609f6ad0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.139: Worker#1| Backtrace13 00007fa1e0b02220 rip=000000369b0de25d rbx=00007fa1e0b02910 rbp=0000000000000000 r12=00007fff609f6ad0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003

Aug 01 11:08:40.139: Worker#1| SymBacktrace[0] 00007fa1e0b01350 rip=000000000041521c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[1] 00007fa1e0b01370 rip=00000000004db650 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[2] 00007fa1e0b01850 rip=0000000000468ea8 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[3] 00007fa1e0b01940 rip=000000369bc0ee90 in function (null) in object /lib64/libpthread.so.0 loaded at 000000369bc00000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[4] 00007fa1e0b01d88 rip=000000369b0332f5 in function gsignal in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[5] 00007fa1e0b01d90 rip=000000369b034b20 in function abort in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[6] 00007fa1e0b01ec0 rip=000000369b075a50 in function (null) in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[7] 00007fa1e0b01f00 rip=000000000047eb93 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[8] 00007fa1e0b01f70 rip=000000000054cc9b in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace[9] 00007fa1e0b01f90 rip=00000000004f165d in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace10 00007fa1e0b01fe0 rip=00000000004f186c in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace11 00007fa1e0b02010 rip=000000000048542a in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

Aug 01 11:08:40.139: Worker#1| SymBacktrace12 00007fa1e0b02110 rip=000000369bc0686a in function (null) in object /lib64/libpthread.so.0 loaded at 000000369bc00000

Aug 01 11:08:40.139: Worker#1| SymBacktrace13 00007fa1e0b02220 rip=000000369b0de25d in function clone in object /lib64/libc.so.6 loaded at 000000369b000000

Aug 01 11:08:40.139: Worker#1| Msg_Post: Error

Aug 01 11:08:40.139: Worker#1| http://msg.log.error.unrecoverable VMware Server unrecoverable error: (Worker#1)

Aug 01 11:08:40.139: Worker#1| Unexpected signal: 6.

Aug 01 11:08:40.139: Worker#1| http://msg.panic.haveLog A log file is available in "/storage/VirtualMachines/srv01.ctg.ee/vmware.log". http://msg.panic.requestSupport.withLog Please request support and include the contents of the log file. http://msg.panic.requestSupport.vmSupport.windowsOrLinux

Aug 01 11:08:40.139: Worker#1| To collect data to submit to VMware support, select Help &gt; About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.

Aug 01 11:08:40.139: Worker#1| http://msg.panic.response We will respond on the basis of your support entitlement.

Aug 01 11:08:40.221: vmx| VTHREAD watched thread 37 "Worker#1" died

Aug 01 11:08:40.222: vcpu-0| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.320: Worker#13| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.320: Worker#8| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.320: Worker#16| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.321: Worker#3| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.321: Worker#0| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.321: Worker#9| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.321: Worker#2| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#7| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#12| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#15| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#10| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.322: Worker#5| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.322: Worker#14| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.323: Worker#4| VTHREAD watched thread 0 "vmx" died

Aug 01 11:08:40.323: Worker#11| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.324: Worker#6| VTHREAD watched thread 4 "vcpu-0" died

Aug 01 11:08:40.554: mks| VTHREAD watched thread 0 "vmx" died

-

I've looked around and that seems to be quite a common problem here and there?

Hello,

on VMware Server 2.0.2 for Windows i have the following setup:

Host: Windows Server 2008 R2

VM: Windows Server 2008 R2

The VM has a bridged network adapter with its own public IP-Address connected to the internet and a VPN incoming connection is ready on the VM.

And here comes the problem:

The host CAN connect to the VM via VPN PPTP, but from outside a client computer cannot - it fails with a timeout.

In detail:

A client (e.g. Win7) trying to connect via VPN (PPTP) hangs at "Verifying user name password..." and after two minutes, the connections gets closed error 619. On the Host this failed connection is logged as Event ID 20252 "The user connected to port VPN3-127 has been disconnected because the authentication process did not complete within the required amount of time."

Other VPN models, e.g. SSTP work without a problem.

I have tried any setting with total firewall off etc. so from now on I assume a problem with the vmware virtual network adapter. It seems to fail to read the GRE- or PPTP Protocol.

I am unable to start my VM machine due to below error message

"Reason: 19 (No such device).
Cannot open the disk '/vmfs/volumes/4fc925da-08b6f598-348b-002564fd3fa1/ITS-Treasury/ITS-Treasury.vmdk' or one of the snapshot disks it depends on."

In VM settings HDD is showing as 0MB, while it was 60GB before. If I am browsing data store I can see as below. This looks to me that vmdk file is 0MB but a file "----rdm.vmdk" is in its orignal size.

Dose anybody know how to start this VM. or we can recover vmdk from rdm.vmdk file.

Hi,

I have a problem regarding snapshots in a virtual machine.

My server has the bellow  identity:

VMware Infrastructure Web AccessVersion 2.0.0Build 128374

VMware ServerVersion 2.0.1Build 156745

The virtual machine has two disks, one 140GB and one 65GB. My problem resides to the first one that included OS files too.

When I opened the folder of that disk, I found all these:

From a little search I did I found that there are some snapshots in that VM but here:

looks like there is no snapshot...

I tried stopping the machine and by using vmware-vdiskmanager.exe tool to merge all disk files to one (since no snapshots seems to exist) but the result when I used the new file, was a disk more that a year old.

Is there any way to merge all the old snapshots in order to create one disk file in the end?

Here are some more info:

file.vmsd content:

.encoding = "windows-1252"

snapshot.lastUID = "2"

snapshot.numSnapshots = "0"

snapshot.current = "0"

snapshot0.uid = "2"

snapshot0.filename = "COMPASS new sharepoint 2010-Snapshot2.vmsn"

snapshot0.displayName = "VMware Server Undopoint"

snapshot0.description = "Snapshot Description."

snapshot0.createTimeHigh = "315877"

snapshot0.createTimeLow = "-1914644888"

snapshot0.numDisks = "1"

snapshot0.disk0.fileName = "COMPASS new sharepoint 2010-000001.vmdk"

snapshot0.disk0.node = "scsi0:0"

snapshot0.disk1.fileName = "COMPASS new sharepoint 2010_3.vmdk"

snapshot0.disk1.node = "scsi0:1"

snapshot.needConsolidate = "TRUE"

snapshot0.type = "1"

file.vmxf content:

<?xml version="1.0"?>

<Foundry>

<VM>

<VMId type="string">52 0e 7f 58 6d 3e b7 63-e0 64 e0 80 58 2f 38 ad</VMId>

<ClientMetaData>

<clientMetaDataAttributes/>

<HistoryEventList/></ClientMetaData>

<vmxPathName type="string">COMPASS new sharepoint 2010.vmx</vmxPathName></VM></Foundry>

file.vmx contents:

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "7"

floppy0.present = "FALSE"

mks.enable3d = "TRUE"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

nvram = "COMPASS new sharepoint 2010.nvram"

virtualHW.productCompatibility = "hosted"

ft.secondary0.enabled = "TRUE"

tools.upgrade.policy = "useGlobal"

powerType.powerOff = "soft"

powerType.powerOn = "hard"

powerType.suspend = "hard"

powerType.reset = "soft"

displayName = "COMPASS new sharepoint 2010"

extendedConfigFile = "COMPASS new sharepoint 2010.vmxf"

numvcpus = "2"

scsi0.present = "TRUE"

scsi0.sharedBus = "none"

scsi0.virtualDev = "lsisas1068"

memsize = "4096"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "COMPASS new sharepoint 2010-000002.vmdk"

scsi0:0.writeThrough = "TRUE"

ide1:0.present = "FALSE"

ide1:0.fileName = "F:\Sharepoint\Compass\Windows 2008 server R2-x64_<removed_product_id>.iso"

ide1:0.deviceType = "cdrom-image"

ide1:0.allowGuestConnectionControl = "FALSE"

ethernet0.present = "TRUE"

ethernet0.allowGuestConnectionControl = "FALSE"

ethernet0.virtualDev = "e1000"

ethernet0.features = "1"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.networkName = "VMnet3"

ethernet0.addressType = "generated"

usb.present = "TRUE"

ehci.present = "TRUE"

guestOS = "longhorn-64"

uuid.location = "56 4d 10 6b c3 c6 13 02-f4 24 f7 02 9f f7 e0 ff"

uuid.bios = "56 4d 10 6b c3 c6 13 02-f4 24 f7 02 9f f7 e0 ff"

vc.uuid = "52 6c 4e 1f 8a 99 31 ba-30 28 b7 5f fe 1e 91 45"

ethernet0.generatedAddress = "00:0c:29:f7:e0:ff"

scsi0:0.redo = ""

vmotion.checkpointFBSize = "134217728"

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "160"

usb.pciSlotNumber = "32"

ethernet0.pciSlotNumber = "33"

ehci.pciSlotNumber = "34"

vmci0.pciSlotNumber = "35"

scsi0.sasWWID = "50 05 05 64 a6 b3 ee 50"

usb:0.present = "TRUE"

usb:1.present = "TRUE"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "-1611144961"

tools.remindInstall = "TRUE"

usb:1.deviceType = "hub"

usb:0.deviceType = "mouse"

tools.syncTime = "FALSE"

scsi0:1.fileName = "E:\Compass_F\Compass_Backup_Disk.vmdk"

scsi0:1.mode = "persistent"

scsi0:1.present = "TRUE"

scsi0:1.redo = ""

scsi0:1.writeThrough = "TRUE"

Thanks in advance,

Argiris

Message was edited by: a.p. - Removed the Windows product ID from the mapped .iso file name

HI, im trying to set my some hp blade bl460c in a C7000  and i'm struggling with the iSCSI Hardware adapter.

I'm running VSphere ESXi 5.1 update 2 and have no trouble with FC adapter. Yet, the hardware iSCSI adapter won't show up on the host.

I tried different vib install to load the iSCSI driver from the vmware download section, but nothing worked so far. And the vib loaded made the host unreachale by the client... Received error 503, connection refused. Even by ssh... I stuggled as many command stated "Unable to connect to local host". I had to redo the blade profile and remove the iSCSI adapter to successfully log back on the blade and than run the command to remove the vib installed... ouch.

So... I was wondering if anyone successfully made it work! There an iSCSI accelerator in the c7000 and want to take advantage from it!