I've tried the investigating locks on the files, and I can remove them, and start powering on the VM again, but then it hangs again. I've tried a couple reboots. Attached is the log for the VM. Can anyone help?

good morning

a linux virtual machine hosted in vshere 4.1 not start and in the event i view this error

Message on linux: There is no more space for
virtual disk
You .vmdk
might be able to continue this session by freeing
disk space on the relevant volume, and clicking
Retry. Click Cancel to terminate this session.

this machine is started when i have deleted every snapshot

now i have seen that the space used for virtual machine is at 50%

what can have caused this problem ?

thanks Alberto

Hello,

I  have a trouble with one VM on vSphere ESXi 5. It's a Windows Server 2008 R2 which is  Domain controller. I have a couple of Windows 2008 VMs, and all of them  work fine, except Domain Controller. First of all I had a Windows Server  2008 R2 Core which worked fine one week without issue. After, it starts shuting down each hour, I have decided to remove it and installed a new VM, but now with  a GUI. As usual, I was happy just one week. Now that DC is shuting down every hour.

I read all logs located in that VM's folder and on ESXi host and I don't see anything. No errors, no warnings.

I  moved that VM from one host to another and nothing changed. I installed  new DC on all hosts, but still the same. I made a HA/DRS cluster and  still the same. If a VM works as a DC, it keeps going off every hour after one week of stable work.

Power Management settings switched from Balansed to High Performance doesn't solve the problem.

If anybody has an idea where to dig better, I will appreciate it a lot

Thanks.

I'm running VMware vSphere 4 Essentials on three almost identically configured hosts with a mix of guests including Windows 2003 and 2008 as well as CentOS 5 and 6.

Recently I installed Update 3 on one of the hosts. The updated host runs Windows and CentOS 5 (kernel 2.6.18-308.13.1.el5 i686) VMs fine, but two CentOS 6 VMs (kernel 2.6.32-279.5.2.el6.x86_64) I tried refuse to come up. They display the GRUB menu just fine, but the kernel panics immediately with "early exception 0d". After moving the VM back to the host without update 3 it comes up fine again.

Any ideas how to fix or even start debugging this?

Btw, all my CentOS 6 VMs are 64 bit. Windows and CentOS 5 VMs come in both 32 and 64 bit flavours. Both 32 and 64 bit Windows VMs run fine on the updated host. So far I haven't tried a 64 bit CentOS 5 VM.

Greetings.

I am having a hard time adding NAS NFS storage in esxi 4.1 using vsphere client. Vmkernel is created under networking.

In the client I get the following error:

Operation failed, diagnostics report: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.

/var/log/messages :

00:40 Hostd: [2012-12-17 18:00:40.016 FFC34E90 verbose 'FSVolumeProvider' opID=EFF3D27B-000000D9] AddNasVolume called
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.016 FFC34E90 verbose 'FSVolumeProvider' opID=EFF3D27B-000000D9] LookupVmfs: Cannot find VMFS volume with id <unset>, path, <unset>, or name nfs-test
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.016 FFC34E90 verbose 'FSVolumeProvider' opID=EFF3D27B-000000D9] LookupNasByName: Cannot find NasVolume with volume name nfs-test
Dec 17 18:00:40 vmkernel: 0:00:14:57.630 cpu1:5187)NFS: 149: Command: (mount) Server: (10.8.4.105) IP: (10.8.4.105) Path: (/raid0/data/_NAS_NFS_Exports_/VM) Label: (nfs-test) Options: (None)
Dec 17 18:00:40 vmkernel: 0:00:14:57.631 cpu0:4104)WARNING: NFS: 213: Got error 13 from mount call
Dec 17 18:00:40 vmkernel: 0:00:14:57.631 cpu1:5187)WARNING: NFS: 959: MOUNT failed with MOUNT status 13 (Permission denied) trying to mount Server (10.8.4.105) Path (/raid0/data/_NAS_NFS_Exports_/VM)
Dec 17 18:00:40 vmkernel: 0:00:14:57.631 cpu1:5187)NFS: 171: NFS mount 10.8.4.105:/raid0/data/_NAS_NFS_Exports_/VM status: The mount request was denied by the NFS server. Check that the export exists and tha
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.153 FFC34E90 error 'FSVolumeProvider' opID=EFF3D27B-000000D9] VmkCtl mount or ProcessNas failed: Unable to complete Sysinfo operation.  Please see the VMkernel log
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.174 FFC34E90 info 'App' opID=EFF3D27B-000000D9] AdapterServer caught exception: 5f990310
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.174 FFC34E90 info 'TaskManager' opID=EFF3D27B-000000D9] Task Completed : haTask-ha-host-vim.host.DatastoreSystem.createNasDatastore-57 Status error
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.174 FFC34E90 info 'Vmomi' opID=EFF3D27B-000000D9] Activation [N5Vmomi10ActivationE:0x5f942020] : Invoke done [createNasDatastore] on [vim.host.DatastoreSystem:ha-d
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.174 FFC34E90 verbose 'Vmomi' opID=EFF3D27B-000000D9] Arg spec:
Dec 17 18:00:40 Hostd: (vim.host.NasVolume.Specification) {
Dec 17 18:00:40 Hostd:    dynamicType = <unset>,
Dec 17 18:00:40 Hostd:    remoteHost = "10.8.4.105",
Dec 17 18:00:40 Hostd:    remotePath = "/raid0/data/_NAS_NFS_Exports_/VM",
Dec 17 18:00:40 Hostd:    localPath = "nfs-test",
Dec 17 18:00:40 Hostd:    accessMode = "readWrite",
Dec 17 18:00:40 Hostd:    type = "nfs",
Dec 17 18:00:40 Hostd:    userName = <unset>,
Dec 17 18:00:40 Hostd:    password = <unset>,
Dec 17 18:00:40 Hostd: }
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.175 FFC34E90 info 'Vmomi' opID=EFF3D27B-000000D9] Throw vim.fault.PlatformConfigFault
Dec 17 18:00:40 Hostd: [2012-12-17 18:00:40.175 FFC34E90 info 'Vmomi' opID=EFF3D27B-000000D9] Result:
Dec 17 18:00:40 Hostd: (vim.fault.PlatformConfigFault) {
Dec 17 18:00:40 Hostd:    dynamicType = <unset>,
Dec 17 18:00:40 Hostd:    faultCause = (vmodl.MethodFault) null,
Dec 17 18:00:40 Hostd:    faultMessage = (vmodl.LocalizableMessage) [
Dec 17 18:00:40 Hostd:       (vmodl.LocalizableMessage) {
Dec 17 18:00:40 Hostd:          dynamicType = <unset>,
Dec 17 18:00:40 Hostd:          key = "com.vmware.esx.hostctl.default",
Dec 17 18:00:40 Hostd:          arg = (vmodl.KeyAnyValue) [
Dec 17 18:00:40 Hostd:             (vmodl.KeyAnyValue) {
Dec 17 18:00:40 Hostd:                dynamicType = <unset>,
Dec 17 18:00:40 Hostd:                key = "reason",
Dec 17 18:00:40 Hostd:                value = "Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.",
Dec 17 18:00:40 Hostd:             }
Dec 17 18:00:40 Hostd:          ],
Dec 17 18:00:40 Hostd:          message = <unset>,
Dec 17 18:00:40 Hostd:       }
Dec 17 18:00:40 Hostd:    ],
Dec 17 18:00:40 Hostd:    text = "",
Dec 17 18:00:40 Hostd:    msg = ""
Dec 17 18:00:40 Hostd: }
Dec 17 18:00:41 Hostd: [2012-12-17 18:00:41.338 5FAC2B90 verbose 'Proxysvc Req00018'] New proxy client TCP(local=127.0.0.1:50982, peer=127.0.0.1:80)
Dec 17 18:00:41 Hostd: [2012-12-17 18:00:41.341 5FA81B90 info 'Vmomi'] Activation [N5Vmomi10ActivationE:0x5f96d288] : Invoke done [waitForUpdates] on [vmodl.query.PropertyCollector:ha-property-collector]
Dec 17 18:00:41 Hostd: [2012-12-17 18:00:41.341 5FA81B90 verbose 'Vmomi'] Arg version:
Dec 17 18:00:41 Hostd: "2"
Dec 17 18:00:41 Hostd: [2012-12-17 18:00:41.341 5FA81B90 info 'Vmomi'] Throw vmodl.fault.RequestCanceled
Dec 17 18:00:41 Hostd: [2012-12-17 18:00:41.341 5FA81B90 info 'Vmomi'] Result:
Dec 17 18:00:41 Hostd: (vmodl.fault.RequestCanceled) {
Dec 17 18:00:41 Hostd:    dynamicType = <unset>,
Dec 17 18:00:41 Hostd:    faultCause = (vmodl.MethodFault) null,
Dec 17 18:00:41 Hostd:    msg = "",
Dec 17 18:00:41 Hostd: }
Dec 17 18:00:41 Hostd: [2012-12-17 18:00:41.342 5FAC2B90 error 'App'] Failed to read header on stream TCP(local=127.0.0.1:55837, peer=127.0.0.1:0): N7Vmacore15SystemExceptionE(Connection reset by peer)

Hello,

We are running EXSi 4.0.0 (294855) on a Dell PowerEdge 2800 with a PERC 4e/Di RAID Controller and three SCSI drives in a RAID 5 configuration.

We experienced a power anomaly where the power flashed on and off several times in rapid succession, but due to failed batteries in the UPS, the server was exposed to power anomaly.

After the event the server rebooted but the datastore was not available and as a result the virtual machines do not start.

------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------

In the vSphere Client, after selecting the ESXi server, then the Configuration tab and then Storage, I see the datastore with one strange item:

datastore1

Local MegaRAID Disk (mpx.vmhba1:C0:T0:L0):3  *

62.75 GB

206.00 MB

vmfs3

2/24/2013 11:01:37 AM

* = Strange item # 1:  I see Local MegaRAID Disk (mpx.vmhba1:C0:T0:L0):3 when I expect to see Local MegaRAID Disk (naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx):3 where xxx… is some actual identifier

------------------------------------------------------------------------------------------------------------

When I click on datastore1 for additional detail it shows the following with two items seeming strange:

Location:  /vmfs/volumes/4cdfecd0-af285957-4667-0011435a3247

Path Selection

Fixed (VMware)

Paths

Total: 1

Broken: 0

Disabled: 0

Properties

Volume Label:  datastore1

Datastore Name:  datastore1

Formating

File System:  VNFS 3.33

Block Size:  1 MB

Extents

Local MegaRAID Disk (mpx.vmhba1:C0:T0:L0):3  0.00B  **

Total Formatted Capacity  62.75 GB

** = Strange item # 2:  I see Local MegaRAID Disk (mpx.vmhba1:C0:T0:L0):3  0.00B when I expect to see Local MegaRAID Disk (naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx):3  62.75 GB where xxx… is some actual identifier and the capacity is 0.00 B.  There are two strange things in this item:  1) The identifier seems wrong and, 2) the capacity is 0.00B.

------------------------------------------------------------------------------------------------------------

In the vSphere Client, after selecting the ESXi server, then the Configuration tab and then Storage Adapters, I see PowerEdge Expandable RAID Controller 4e/Di among other items.  Just under that I see vmhba1  SCSI.  When I click on vmhba1  SCSI 1 for additional detail it shows the following [Devices] with two items seeming strange:

Local MegaRAID Disk (mpx.vmhba1:C0:T0:L0)  ***

mpx.vmhba1:C0:T0:L0  ***

vmhba1:C0:T0:L0  ****

0

Disk

Parallel SCSI

67.73 GB

NMP

*** = Strange item # 3:  I see Local MegaRAID Disk (mpx.vmhba1:C0:T0:L0) when I expect to see Local MegaRAID Disk (naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) where xxx… is some actual identifier

**** = Strange item # 4:  I see mpx.vmhba1:C0:T0:L0 when I expect to see naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx where xxx… is some actual identifier

------------------------------------------------------------------------------------------------------------

When [Paths] is selected (from above location), I see what looks normal but with a twist:

vmhba1:C0:T0:L0

[BLANK]

0

Active (I/O)

If I right click and select copy path to clipboard then past it into notepad, I get slightly different result with one item seeming strange:

unknown.vmhba1-unknown.0:0-mpx.vmhba1:C0:T0:L0  *****

***** = Strange item # 5:  I see unknown.vmhba1-unknown.0:0-mpx.vmhba1:C0:T0:L0 when I expect to see unknown.vmhba1-unknown.0:0-naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx where xxx… is some actual identifier

------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------

As can be seen, a consistent theme seems to exist.  In places where one item is expected, another is present.  Specifically, in those instances where naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx is expected where xxx… is some actual identifier, mpx.vmhba1:C0:T0:L0 is present.

------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------

The complete log files and this problem description are available at:  www.varvayanis.com/vmware_problem_2-24-2013

What I expect is a significant clue, the /var/log/vmware/hostd.log log contains some interesting information.  Below are the top 71 lines from that log with the first thing I notice as possibly strange beginning at line 56 and additional errors that get my attention are on lines 58,60,66,67 and 69.  Many more “Looking up object with name = "ha-view-mgr-impl" failed.” errors occur throughout the log, but that is past the volume setup stuff below:

1)     Log for VMware ESX, pid=4960, version=4.0.0, build=build-294855, option=Release, section=1

2)     [2013-02-24 07:07:08.218 1FE74DB0 info 'App'] Current working directory: /var/log/vmware

3)     [2013-02-24 07:07:08.219 1FE74DB0 verbose 'ThreadPool'] Thread info: Min Io, Max Io, Min Task, Max Task, Max Thread, Keepalive, thread kill, max fds: 2, 200, 2, 12, 42, 8, 600, 2048

4)     [2013-02-24 07:07:08.219 1FE74DB0 info 'Handle checker'] Setting system limit of 2048

5)     [2013-02-24 07:07:08.219 1FE74DB0 info 'Handle checker'] Set system limit to 2048

6)     [2013-02-24 07:07:08.221 1FE74DB0 verbose 'App'] Executable directory: /etc/init.d

7)     [2013-02-24 07:07:08.221 1FE74DB0 verbose 'App'] Plugin base directory: /lib/

8)     [2013-02-24 07:07:08.221 1FE74DB0 info 'App'] Trying blklistsvc

9)     [2013-02-24 07:07:08.221 1FE74DB0 verbose 'App'] Plugin 0 statically linked

10) [2013-02-24 07:07:08.222 1FE74DB0 info 'BlklistsvcPlugin'] Block List Service Plugin initialized

11) [2013-02-24 07:07:08.222 1FE74DB0 info 'App'] Trying cimsvc

12) [2013-02-24 07:07:08.222 1FE74DB0 verbose 'App'] Plugin 1 statically linked

13) [2013-02-24 07:07:08.222 1FE74DB0 verbose 'Cimsvc'] Initializing cimsvc plugin

14) [2013-02-24 07:07:08.227 1FE74DB0 verbose 'Cimsvc'] Created CimManagerImpl

15) [2013-02-24 07:07:08.227 1FE74DB0 info 'App'] Trying directorysvc

16) [2013-02-24 07:07:08.227 1FE74DB0 verbose 'App'] Plugin 2 statically linked

17) [2013-02-24 07:07:08.227 1FE74DB0 verbose 'DirectorysvcPlugin'] Directory service initialized

18) [2013-02-24 07:07:08.228 1FE74DB0 verbose 'DirectorysvcPlugin'] Command: Esxtop created

19) [2013-02-24 07:07:08.235 1FE74DB0 verbose 'DirectorysvcPlugin'] Service added: Esxtop:

20) [2013-02-24 07:07:08.235 1FE74DB0 info 'DirectorysvcPlugin'] Plugin initialized

21) [2013-02-24 07:07:08.235 1FE74DB0 info 'App'] Trying hostsvc

22) [2013-02-24 07:07:08.235 1FE74DB0 verbose 'App'] Plugin 3 statically linked

23) [2013-02-24 07:07:08.235 1FE74DB0 verbose 'HostsvcPlugin'] CreateHostsvcFactory: mockup mode is false

24) [2013-02-24 07:07:08.236 1FE74DB0 info 'HostsvcPlugin'] Storage data synchronization policy set to invalidate_change

25) [2013-02-24 07:07:08.236 1FE74DB0 info 'Vmfs2UpgradeModeLock'] [Init] undoAttempts(15), timeoutMsec(2000)

26) [2013-02-24 07:07:08.237 1FE74DB0 verbose 'FSVolumeProvider'] FSVolumeVmkImplProvider::Start() called

27) [2013-02-24 07:07:08.237 1FE74DB0 error 'FSVolumeProvider'] FSVolumeVmkImplProvider::Start() called

28) [2013-02-24 07:07:08.237 1FE74DB0 verbose 'HostsvcPlugin'] Initializing resource pool tree

29) [2013-02-24 07:07:08.237 1FE74DB0 info 'HostsvcPlugin'] Resource pool configuration: /etc/vmware/hostd/pools.xml

30) [2013-02-24 07:07:08.238 1FE74DB0 verbose 'HostsvcPlugin'] Looking up VMkernel resource group 'host/user'

31) [2013-02-24 07:07:08.239 1FE74DB0 verbose 'HostsvcPlugin'] Initializing vms in resource pool tree

32) [2013-02-24 07:07:08.240 1FE74DB0 verbose 'NetworkProvider'] Fetch all physical NICs....

33) [2013-02-24 07:07:09.331 1FE74DB0 verbose 'NetworkProvider'] Fetched physical NIC: vmnic0.

34) [2013-02-24 07:07:09.397 1FE74DB0 verbose 'NetworkProvider'] Fetched physical NIC: vmnic1.

35) [2013-02-24 07:07:09.397 1FE74DB0 verbose 'NetworkProvider'] Loading DVS information

36) [2013-02-24 07:07:09.397 1FE74DB0 verbose 'NetworkProvider'] DvsVmkProvider::Refresh called

37) [2013-02-24 07:07:09.398 1FE74DB0 warning 'NetworkProvider'] Failed to load DVS portgroup information : no element found.

38) [2013-02-24 07:07:09.398 1FE74DB0 verbose 'NetworkProvider'] Fetch all virtual switches....

39) [2013-02-24 07:07:09.725 1FE74DB0 verbose 'NetworkProvider'] Successfully fetched virtual switch: vSwitch0.

40) [2013-02-24 07:07:09.726 1FE74DB0 verbose 'NetworkProvider'] RefreshVmkernelNic: called

41) [2013-02-24 07:07:09.748 1FE74DB0 verbose 'NetworkProvider'] InstallNics: Fetch all VmKernel NICs....

42) [2013-02-24 07:07:09.770 1FE74DB0 verbose 'NetworkProvider'] InstallNics: Successfully fetched VmKernel NIC vmk0 on Management Network.

43) [2013-02-24 07:07:09.771 1FE74DB0 verbose 'NetworkProvider'] RefreshConsoleNic: Fetch all Console NICs....

44) [2013-02-24 07:07:09.792 1FE74DB0 verbose 'NetworkProvider'] All vnics refreshed, found 0 disabled.

45) [2013-02-24 07:07:09.792 1FE74DB0 verbose 'NetworkProvider'] Obtaining DNS Configuration....

46) [2013-02-24 07:07:09.795 1FE74DB0 verbose 'NetworkProvider'] Dns Configuration: Network::DnsConfig { GetHostname(): localhost, GetPreferredHostname():, GetDomain(): varvayanis.com, [0] 147.78.249.200, [1] 148.78.249.201, [0] varvayanis.com, GetSearchDomainString(): varvayanis.com, GetName(): DnsConfigImpl} }

47) [2013-02-24 07:07:09.795 1FE74DB0 verbose 'NetworkProvider'] Obtaining Route Configuration....

48) [2013-02-24 07:07:09.796 1FE74DB0 info 'NetworkProvider'] SetIPv6Capability: IPv6 is disabled

49) [2013-02-24 07:07:09.796 1FE74DB0 info 'HostsvcPlugin'] Datastore auto-refresh is disabled.

50) [2013-02-24 07:07:09.796 1FE74DB0 info 'Hostsvc::DatastoreSystem'] Datastore alias configuration file is /etc/vmware/hostd/datastores.xml

51) [2013-02-24 07:07:09.797 1FE74DB0 verbose 'Hostsvc::DatastoreSystem'] ReconcileVMFSDatastores called: refresh = true, rescan = false

52) [2013-02-24 07:07:09.797 1FE74DB0 verbose 'FSVolumeProvider'] RefreshVMFSVolumes called

53) [2013-02-24 07:07:09.882 1FE74DB0 verbose 'FSVolumeProvider'] RefreshVMFSVolumes: refreshed volume, id 4cdfecd0-af285957-4667-0011435a3247, name datastore1

54) [2013-02-24 07:07:09.882 1FE74DB0 verbose 'FSVolumeProvider'] RefreshOneVmfsVolume on /vmfs/volumes/4cdfecd0-af285957-4667-0011435a3247

55) [2013-02-24 07:07:09.885 1FE74DB0 info 'Hostsvc::Datastore'] Refresh: VMFS Datastore name was changed from '4cdfecd0-af285957-4667-0011435a3247' to 'datastore1'.

56) [2013-02-24 07:07:09.885 1FE74DB0 verbose 'App'] Looking up object with name = "ha-vmsvc" failed.

57) [2013-02-24 07:07:09.886 1FE74DB0 verbose 'DatastoreBrowser'] 4cdfecd0-af285957-4667-0011435a3247-datastorebrowser::IntializeCOSDirectory: COS path: /vmimages/

58) [2013-02-24 07:07:09.886 1FE74DB0 verbose 'App'] Looking up object with name = "ha-view-mgr-impl" failed.

59) [2013-02-24 07:07:09.886 1FE74DB0 verbose 'DatastoreBrowser'] 4cdfecd0-af285957-4667-0011435a3247-datastorebrowser::Constructor

60) [2013-02-24 07:07:09.886 1FE74DB0 verbose 'App'] Looking up object with name = "ha-view-mgr-impl" failed.

61) [2013-02-24 07:07:09.886 1FE74DB0 verbose 'Hostsvc::DatastoreSystem'] DiscoverNewDatastores: datastore1 created.

62) [2013-02-24 07:07:09.886 1FE74DB0 verbose 'Hostsvc::DatastoreSystem'] ReconcileVMFSDatastores: Done discovering new filesystem volumes.

63) [2013-02-24 07:07:09.886 1FE74DB0 verbose 'Hostsvc::DatastoreSystem'] ReconcileNASDatastores: Discovering new filesystem volumes.

64) [2013-02-24 07:07:09.886 1FE74DB0 verbose 'FSVolumeProvider'] RefreshNASVolumes called

65) [2013-02-24 07:07:09.909 1FE74DB0 verbose 'Hostsvc::DatastoreSystem'] ReconcileNASDatastores: Done discovering new filesystem volumes.

66) [2013-02-24 07:07:22.642 1FE74DB0 verbose 'App'] Looking up object with name = "ha-view-mgr-impl" failed.

67) [2013-02-24 07:07:22.642 1FE74DB0 verbose 'App'] Looking up object with name = "ha-vmsvc" failed.

68) [2013-02-24 07:07:22.643 1FE74DB0 verbose 'DatastoreBrowser'] ha-host-datastorebrowser::IntializeCOSDirectory: COS path: /vmimages/

69) [2013-02-24 07:07:22.643 1FE74DB0 verbose 'App'] Looking up object with name = "ha-view-mgr-impl" failed.

70) [2013-02-24 07:07:22.643 1FE74DB0 verbose 'DatastoreBrowser'] ha-host-datastorebrowser::Constructor

71) [2013-02-24 07:07:22.643 1FE74DB0 info 'Hostsvc::AutoStartManager'] VM autostart configuration: /etc/vmware/hostd/vmAutoStart.xml

------------------------------------------------------------------------------------------------------------

The complete log files and this problem description are available at:  www.varvayanis.com/vmware_problem_2-24-2013

What I expect is also a clue, the /var/log/Messages.log log contains some interesting information.  Below are 115 lines starting at line 1439 from that log with the first item that got my attention at line 1479 and additional items that got my attention are on lines 1481, 1526, 1528, 1532 and 1533:

1439)                        Feb 24 07:06:50 vmkernel: 0:00:00:38.869 cpu2:4551)ata_piix loaded successfully.

1440)                        Feb 24 07:06:50 vmkernel:

1441)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.717 cpu2:4554)Loading module megaraid2 ...

1442)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.717 cpu2:4554)Elf: 2320: <megaraid2> symbols tagged as <GPL>

1443)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)module heap : Initial heap size : 8388608, max heap size: 20971520

1444)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)module heap megaraid2: creation succeeded. id = 0x4100b2000000

1445)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: driver megaraid2 is looking for devices

1446)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:02.0

1447)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Announcing 0000:00:02.0

1448)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:03.0

1449)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Announcing 0000:00:03.0

1450)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:04.0

1451)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Announcing 0000:00:04.0

1452)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:05.0

1453)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Announcing 0000:00:05.0

1454)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:06.0

1455)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Announcing 0000:00:06.0

1456)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:1d.0

1457)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:1d.1

1458)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:1d.2

1459)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:1d.7

1460)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:00:1f.1

1461)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Trying 0000:02:0e.0

1462)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.739 cpu2:4554)PCI: Announcing 0000:02:0e.0

1463)                        Feb 24 07:06:52 vmkernel: <5>megaraid: found 0x1028:0x  0013:bus 2:0:00:00:40.739 cpu2:4554)slot 14:func 0

1464)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.740 cpu2:4554)<5>scsi2:Found MegaRAID controller at 0x4100b2a02000, IRQ:153

1465)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.740 cpu2:4554)IDT: 939: 0x99 <megaraid> sharable (entropy source), flags 0x10

1466)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.740 cpu2:4554)VMK_VECTOR: 143: Added handler for shared vector 153, flags 0x10

1467)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.740 cpu2:4554)IDT: 1035: 0x99 for vmkernel

1468)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.740 cpu2:4554)VMK_VECTOR: 231: vector 153 enabled

1469)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.740 cpu2:4554)<5>megaraid: [5B2D:H435] detected 1 logical drives.

1470)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.740 cpu2:4554)<5>megaraid: supports extended CDBs.

1471)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.744 cpu2:4554)<6>megaraid: channel[0] is raid.

1472)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.744 cpu2:4554)<6>megaraid: channel[1] is scsi.

1473)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.744 cpu2:4554)VMK_PCI: 638: Device 002:14.0 name: vmhba1

1474)                        Feb 24 07:06:52 vmkernel: <5>scsi2: scanning scsi channel 0 0:00:00:40.744 cpu2:4554)for logical drives.

1475)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.744 cpu2:4554)ScsiScan: 844: Path 'vmhba1:C0:T0:L0': Vendor: 'MegaRAID'  Model: 'LD 0 RAID5   69G'  Rev: '5B2D'

1476)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.744 cpu2:4554)ScsiScan: 847: Path 'vmhba1:C0:T0:L0': Type: 0x0, ANSI rev: 2, TPGS: 0 (none)

1477)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.752 cpu0:4550)EVPD INQ host status changed to DID_OK

1478)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.752 cpu2:4554)ScsiUid: 268: Path 'vmhba1:C0:T0:L0' does not support VPD Device Id page.

1479)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.752 cpu2:4554)ScsiScan: 959: Path 'vmhba1:C0:T0:L0' : No standard UID: Failure. ANSI version 'SCSI-2' (0x2).

1480)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.760 cpu0:4550)EVPD INQ host status changed to DID_OK

1481)                        Feb 24 07:06:52 vmkernel: 0:00:00:40.760 cpu2:4554)VMWARE SCSI Id: Could not get disk id for vmhba1:C0:T0:L0

1482)                        Feb 24 07:06:52 vmkernel: <5>scsi2: scanning scsi channel 1 0:00:00:40.766 cpu0:4554)for logical drives.

1483)                        Feb 24 07:06:52 vmkernel: <5>scsi2: scanning scsi channel 2 0:00:00:40.794 cpu1:4554)for logical drives.

1484)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)ScsiClaimrule: 1118: Path claiming is disabled. Do not try to claim path.

1485)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)PCI: driver megaraid2 claimed device 0000:02:0e.0

1486)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)LinPCI: LinuxPCI_DeviceClaimed: Device 2:70 claimed.

1487)                        Feb 24 07:06:52 vmkernel:

1488)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)PCI: Trying 0000:0b:07.0

1489)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)PCI: Trying 0000:0c:08.0

1490)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)PCI: Trying 0000:10:0d.0

1491)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)PCI: Announcing 0000:10:0d.0

1492)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)PCI: driver megaraid2 claimed 1 device

1493)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)ScsiNpiv: 1440: GetInfo for adapter vmhba1, [0x41000403d2c0], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020

1494)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)Mod: 3003: Initialization for megaraid2 succeeded with module ID 34.

1495)                        Feb 24 07:06:52 vmkernel: 0:00:00:41.009 cpu0:4554)megaraid2 loaded successfully.

1496)                        Feb 24 07:06:52 vmkernel:

1497)                        Feb 24 07:06:53 vmkernel: sysboot: Loading VMkernel Module 'lvmdriver'

1498)                        Feb 24 07:06:53 vmkernel: 0:00:00:41.934 cpu3:4560)Loading module lvmdriver ...

1499)                        Feb 24 07:06:53 vmkernel: 0:00:00:41.934 cpu3:4560)Elf: 2320: <lvmdriver> symbols tagged as <VMware>

1500)                        Feb 24 07:06:53 vmkernel: 0:00:00:41.956 cpu3:4560)LVM: 782: LVM max heap size: 43008KB

1501)                        Feb 24 07:06:53 vmkernel: 0:00:00:41.956 cpu3:4560)FDS: 337: lvm

1502)                        Feb 24 07:06:53 vmkernel: 0:00:00:41.956 cpu3:4560)Mod: 3003: Initialization for lvmdriver succeeded with module ID 35.

1503)                        Feb 24 07:06:53 vmkernel: 0:00:00:41.956 cpu3:4560)lvmdriver loaded successfully.

1504)                        Feb 24 07:06:53 vmkernel:

1505)                        Feb 24 07:06:53 vmkernel: sysboot: Loading VMkernel Module 'deltadisk'

1506)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.046 cpu1:4566)Loading module deltadisk ...

1507)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.046 cpu1:4566)Elf: 2320: <deltadisk> symbols tagged as <VMware>

1508)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.075 cpu1:4566)FDS: 337: deltadisks

1509)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.075 cpu1:4566)Mod: 3003: Initialization for deltadisk succeeded with module ID 36.

1510)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.075 cpu1:4566)deltadisk loaded successfully.

1511)                        Feb 24 07:06:53 vmkernel:

1512)                        Feb 24 07:06:53 vmkernel: sysboot: Loading VMkernel Module 'multiextent'

1513)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.164 cpu2:4572)Loading module multiextent ...

1514)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.164 cpu2:4572)Elf: 2320: <multiextent> symbols tagged as <VMware>

1515)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.186 cpu2:4572)FDS: 337: multiextent

1516)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.186 cpu2:4572)Mod: 3003: Initialization for multiextent succeeded with module ID 37.

1517)                        Feb 24 07:06:53 vmkernel: 0:00:00:42.186 cpu2:4572)multiextent loaded successfully.

1518)                        Feb 24 07:06:53 vmkernel:

1519)                        Feb 24 07:06:53 vmkernel: sysboot: Starting Path Claiming and SCSI Device Discovery...

1520)                        Feb 24 07:06:53 vmkernel: sysboot: Executing 'esxcli corestorage claimrule load'

1521)                        Feb 24 07:06:54 vmkernel: sysboot: Executing 'esxcli corestorage claiming autoclaim --enabled=true'

1522)                        Feb 24 07:06:54 vmkernel: sysboot: Executing 'esxcli corestorage claimrule run --wait'

1523)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.398 cpu0:4583)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba0:C0:T0:L0'

1524)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.398 cpu0:4583)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L0'

1525)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.406 cpu0:4583)EVPD INQ host status changed to DID_OK

1526)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.406 cpu0:4583)ScsiUid: 268: Path 'vmhba1:C0:T0:L0' does not support VPD Device Id page.

1527)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.414 cpu0:4583)EVPD INQ host status changed to DID_OK

1528)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.414 cpu0:4583)VMWARE SCSI Id: Could not get disk id for vmhba1:C0:T0:L0

1529)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.414 cpu0:4583)vmw_psp_fixed: psp_fixedSelectPathToActivateInt: Changing active path from NONE to vmhba1:C0:T0:L0 for device "Unregistered Device".

1530)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.422 cpu0:4583)EVPD INQ host status changed to DID_OK

1531)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.422 cpu0:4583)VMWARE SCSI Id: Could not get disk id for vmhba1:C0:T0:L0

1532)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.422 cpu0:4583)ScsiDeviceIO: 2469: Get VPD 80 Inquiry for device "mpx.vmhba1:C0:T0:L0" from Plugin "NMP" failed. Not supported

1533)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.422 cpu0:4583)ScsiDeviceIO: 2479: Get VPD 83 Inquiry for device "mpx.vmhba1:C0:T0:L0" from Plugin "NMP" failed. Not supported

1534)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.489 cpu0:4583)FSS: 3702: No FS driver claimed device '4cdfecd0-88651ba4-fa57-0011435a3247': Not supported

1535)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.525 cpu0:4583)ScsiDevice: 1938: Successfully registered device "mpx.vmhba1:C0:T0:L0" from plugin "NMP" of type 0

1536)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.528 cpu0:4583)ScsiUid: 268: Path 'vmhba0:C0:T0:L0' does not support VPD Device Id page.

1537)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.529 cpu0:4583)VMWARE SCSI Id: Could not get disk id for vmhba0:C0:T0:L0

1538)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.529 cpu0:4583)vmw_psp_fixed: psp_fixedSelectPathToActivateInt: Changing active path from NONE to vmhba0:C0:T0:L0 for device "Unregistered Device".

1539)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.530 cpu0:4583)VMWARE SCSI Id: Could not get disk id for vmhba0:C0:T0:L0

1540)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.530 cpu0:4583)ScsiDeviceIO: 2469: Get VPD 80 Inquiry for device "mpx.vmhba0:C0:T0:L0" from Plugin "NMP" failed. Not supported

1541)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.530 cpu0:4583)ScsiDeviceIO: 2479: Get VPD 83 Inquiry for device "mpx.vmhba0:C0:T0:L0" from Plugin "NMP" failed. Not supported

1542)                        Feb 24 07:06:57 vmkernel: 0:00:00:45.530 cpu0:4583)ScsiDevice: 1938: Successfully registered device "mpx.vmhba0:C0:T0:L0" from plugin "NMP" of type 5

1543)                        Feb 24 07:07:00 vmkernel: sysboot: Path Claiming and SCSI Device Discovery Complete

1544)                        Feb 24 07:07:00 vmkernel: sysboot: Executing 'esxcfg-mpath -r'

1545)                        Feb 24 07:07:00 vmkernel: sysboot: Loading VMkernel Module 'dvsdev'

1546)                        Feb 24 07:07:00 vmkernel: 0:00:00:48.773 cpu2:4594)Loading module dvsdev ...

1547)                        Feb 24 07:07:00 vmkernel: 0:00:00:48.774 cpu2:4594)Elf: 2320: <dvsdev> symbols tagged as <VMware>

1548)                        Feb 24 07:07:00 vmkernel: 0:00:00:48.796 cpu2:4594)Mod: 3003: Initialization for dvsdev succeeded with module ID 38.

1549)                        Feb 24 07:07:00 vmkernel: 0:00:00:48.796 cpu2:4594)dvsdev loaded successfully.

1550)                        Feb 24 07:07:00 vmkernel:

1551)                        Feb 24 07:07:00 vmkernel: sysboot: Loading VMkernel Module 'etherswitch'

1552)                        Feb 24 07:07:00 vmkernel: 0:00:00:48.893 cpu2:4600)Loading module etherswitch ...

1553)                        Feb 24 07:07:00 vmkernel: 0:00:00:48.893 cpu2:4600)Elf: 2320: <etherswitch> symbols tagged as <VMware>

------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------

At the CLI I issued the command:

esxcfg-mpath.pl -l --server 10.145.0.2 --username xxxx --password xxx

and received the response:

ide.vmhba0-ide.0:0-mpx.vmhba0:C0:T0:L0

   Runtime Name: vmhba0:C0:T0:L0

   Device: mpx.vmhba0:C0:T0:L0

   Device Display Name: Local TEAC CD-ROM (mpx.vmhba0:C0:T0:L0)

   Adapter: vmhba0 Channel: 0 Target: 0 LUN: 0

   Adapter Identifier: ide.vmhba0

   Target Identifier: ide.0:0

   Plugin: NMP

   State: active

   Transport: ide

unknown.vmhba1-unknown.0:0-mpx.vmhba1:C0:T0:L0

   Runtime Name: vmhba1:C0:T0:L0

   Device: mpx.vmhba1:C0:T0:L0

   Device Display Name: Local MegaRAID Disk (mpx.vmhba1:C0:T0:L0)

   Adapter: vmhba1 Channel: 0 Target: 0 LUN: 0

   Adapter Identifier: unknown.vmhba1

   Target Identifier: unknown.0:0

   Plugin: NMP

   State: active

   Transport: parallel

------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------

At the very bottom of an article I found, there is something that sounds relevant to this situation, but it is in a format that seems to relevant to ESX and maybe not ESXi.  If it is relevant ESXi, I do not know how to implement it.

Here is the link:

communities.vmware.com/thread/303695 (Very bottom of the article).

------------------------------------------------------------------------------------------------------------

I am also receiving a lot of these messages:  “Lost access to volume 4cdfecd0-af285957-4667-0011435a3247 (datastore1) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.”  I found an article that may be relevant, but it has not helped me yet.

Here is the link:

kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009557

------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------

I am stuck.  Any help would be much appreciated.

Thank you,

  Charles Varvayanis

hello

I have HP Servers having HP embedded ESXI server installed with HP owned ISO, I want to know physical drive details in ESXi ( as like hpacucli), because i have drive failure and want to replace that drive,

Could anyone tell me how to get the info. I am also missing storage info in Health status tab(VI client)

Regards,

DJ

Hello All ,

We are trying to install  Intel® Hardware Accelerated Execution Manager, but we are getting following error.

Can any please guide me how to resolve this .

Error Msg : This Computer doesnt support Intel Virtulization Technology (VT-X).

Checked the following :

• esxcfg-info|grep "HV Support"

          |----HV Support............................................3

• Use Intel VT-X for instruction set virtualization and Software for MMU is enabled in VM CPU configurations.

Thanks in Advance !!..

Shashi

Hi,

I've created a FreeNAS iSCSi mirrored storage for my ESXi host, following this tutorial Step by Step Configuration FreeNAS 8.3.1 as iSCSI Target External Storage by Nathan Gusti Ryan - YouTube but unfortunately I can see the path in ESXI configuration but not the actual device. Can you tell me what the problem might be? I have exactly the same configuration on another server DL360 and it is working properly but it doesn't have Intel network cards. The new one's got them and I've been thinking if that might be the problem. Can you help me out?

Hi,

This morning we had an issue with our ESXI 4.0 host. It appears that we have a failed drive in the array and once this was fixed we faced an issue with error - PANIC - Error while reading file 5 - state.tgz.

I repaired the host which wiped the config of the host and retained all data in the datastore, My next steps included reconfiguring the servers network settings and creating a new VM with the VMDK of our server that was retained. I successfully built the VM however windows woldnt boot, i was faced with tghe below error in windows boot manager:

File: \Windows\system32\winload.exe

Status: 0xc000000f

Info: The selected entry could not be loaded because the application is missing or corrupt

I have booted from the server 2003 installation disk to enter Windows Recovery Console and run the following

F:\Windows\System32\bcdedit /store F:\Boot\BCD /set {bootmgr} device boot

The operation completed successfully.

F:\Windows\System32\bcdedit /store F:\Boot\BCD /set {default} device boot

The operation completed successfully.

F:\Windows\System32\bcdedit /store F:\Boot\BCD /set {default} osdevice boot

The operation completed successfully.

However.... here's the problem... when selecting the installation i want to log onto in the recovery console, i am never prompted for a password and the console just hangs, i did check CPU utilisation and there is activity so something is happening.

Anyone came across this issue before?

Thanks in advance for your help.

Hi,

I am having the following problem with vsphere client 4.1.

When I open a vmware console to a v.Host, every keystroke that I type, it goes into the vmachine linux, or windows, as if my keyboard was a USA keyboard.

My keyboard a swiss german layout, and likewise, every vhost has a swiss german keyboard layout.

If I ssh to a machine, the keys I send are not a problem.

The problem takes place only through the vmware console interface to the machine.

Initially vSphere was working properly. This problem started taking place after i use the vsphere cliente 4.1 build 799345

to connect to a vsphere server Esxi 4.0, which installed some packages on my machine.

I have tried playing with my windows 7 locale. Deleting the USA keyboard from the list of available keyboard layouts to switch to in the language bar, etc...

In the end nothing seems to work.

I type - and the virtual machine receives /. I write ^ the host receives =.

Anyway what might be going on?

Thanks in advance

hi everyone,

I have no idea what caused this, but all of the sudden, I have 4 vm,s windows xp sp2, that I cant backup using veeam backup, as there is a snapshot in progress.

Meaning, veeam needs to take a snapshot before backing up a vm, but, there is already a snapshot in progress.

Create virtual machine snapshot

YALABMGR

In Progress

vpxuser

6/20/2010 12:02:16 PM

6/20/2010 12:02:16 PM

how do I kill this "in progress" snapshot?

Peter

Some of my VMs (Guests) are doing advanced routing and packet manipulation (using Linux).  Unfortunately, the support for "TCP Segment Offload" in the VMXNET 3 driver causes this to malfunction, as the machine needs to process the TCP packets individually, and not as preassembled TCP segments.

Under ESXi 4.0u1 I could solve this by turning off TSO in the VMXNET 3 driver using "ethtool -K ethX tso off ; ethtool -K ethX gso off", but after I upgraded to ESXi 4.1 and VMware tools 8.3.2, this no longer helps, and the VM still receives oversized pseudo-packets combined from multiple network packets, which in turn causes connections to fail.

So how do I turn off TCP Segmentation Offload for VM/vSwitch traffic under ESXi 4.1 ?

P.S.

In case it matters: This is a HP DL385 G5p with on board Broadcom NICs.

My ESX host names appearing in lower cases in vCenter 4.1.  How can I make them appear in upper cases which looks way better than lower cases.?

thanks.

Hi Everyone,

I'm having problem with deleting my empty VMFS3 datastore I have restarted the host already but somehow it is still stuck cannot bedeleted, can anyone help me in deleting this empty VMFS3 datastore please ?

Thanks.

I am running ESXi 4.1.0.  I have a number of 2k8 R2 machines running on this server.

What I've noticed is that some, not all VMs are using 75%-95% of the available memory.  When I look at the processes running, it's very minimal with nothing really using anywhere near that much memory.  I used  RamMap to try to try to see who was the hidden culprit.  RamMap showed that "Driver Locked" was using 4-5GB of memory.  (As shown here in another site thread)

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_26259037.html

Upon further research, I found some people said this was related to VMWare Tools.  Sure enough, as soon as I uninstalled VMWare Tools from the VM the memory went to where I would expect, and "Driver Locked" went to almost nothing, and eventually disappeared. 

I installed VMWare tools with an upgrade when I converted the VM.  Of the maybe 12 VMs I think 3-4 are experienceing this.

Anyone have any thoughts?

Hi guys,

     I am currently having an issue with my ESX/ESXi 3.5 server.  I am trying to update the BIOS firmware but have been unsuccessful.

I have downloaded the required files and followed the instructions from HP but to no avail.  After running the command from root "sh cp006541.scexe" I get the following error:

cp006541.scexe: cannot find a required program.

I can verify that gzip and tar are installed on the server.  Is it that i am logged in as root that this will not work? 

HP SmartStart cd does not support VMware ESX host so i cannot use this CD either.

Can anyone please help me with this issue as i am unable to find any other information at hp.com

Your help is appreciated

Kind Regards

Angelo

what is an acceptable read/write latency on a virtual disk? I have a figure in my head of 20ms threshhold, or 50ms threshhold(spikes) for SAN disks on physical hardware, what about VMs?

I have 6 esxi hosts and I'm running vcenter 4.1. Two of the six esxi hosts get this error when I try to migrate vm's. They are all configured exactly the same, and it doesn't add up that two of them don't work. When I go to "Virtual Machine Swapfile Location" it is clearly set to - "virtual machine directory" (the recommended option), just like the other 4 that work fine.

The only thing I have found to fix this is to update to vcenter 4.1, but I'm already on 4.1

All help appreciated! Thanks!

Got below error while trying to combine snapshot files.

vmkfstools -i AXTST167-000001.vmdk /vmfs/volumes/datastore1/axtstbundled/AXTST167.vmdk

Destination disk format: VMFS zeroedthick

Failed to open 'AXTST167-000001.vmdk': Invalid argument (1441801).