Hello,

A customer of ours recently upgraded from esxi to vsphere 4. After the upgrade we have been unable to see the tape drive attached to thte server.

The drive is an HP Ultrium 448 LTO plugged in to an adaptec ultra320 29320LPE.

The correct card appears in the vshpere client under configuration/storage adapters but I do not see any deivces plugged in to this card.

If I click on "path" on the adaptec card I see the status is appearing as "dead"

Any idea why this was working fine in esxi but is now not working in vsphere 4?

Thank you!

Good Day ,

I have in this days one error :

Unable to connect to the MKS:Host address lookup for server esx1.domaine.com failed:Unknow error 11001 (0x2af9)

can you help me

thank you

Hello,

I'm getting the error message below when i try to connect to esxi hosts.

"A communication error occurred while sending data to the server. (the underlying connection was closed: an unexpected error occurred on a send)"

I have two esxi hosts and i have this problem on both. I can ping them but i can't connect. There is no firewall between hosts and clients. After i restart the hosts, i can connect, but after a couple of days the problem occurres again.

Version informations are below:

ESXI 4.1.0 Build 348481

Vsphere client 4.1.0 Build 345043

Do you guys have any idea about this problem?

Thanks in advance.

hi,

One VIrtual Machine  haveing snapshot disk files, Useing  Vi client we are not able to see any snapshots.But if i login to esxi console i am able to see the delta disk files. i tried with vmkfstools -U  , But it saying invalid disk file.

Can you please help how to delete the Delta files from command line.

Regards

Surya

Virtual machines might stop responding during a snapshot removal due to a forced synchronous consolidation between the snapshot disk and the parent disk. This occurs when the virtual machine is running a heavy I/O workload during snapshot consolidation.

To disable synchronous consolidation add the configuration option snapshot.asyncConsolidate.forceSync = "FALSE" to the VMX file.

Am refering to this KB (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2041338)

*does this setting automatically modified in the patch ?

*can i modify only this setting ?

*when the KB says "Virtual machines might stop responding during a snapshot removal" does that mean the snapshot removal (consolidation) fails

or completes successfully?

Am using a VADP software(Veeam) for replicating my VMs and am doubting this setting might be the cause of troubles.

As stated in the KB, the VM am talking about does come under heavy I/O.

My issue is : The software needs to remove/consolidate the snapshots once the job is completed.this is the normal operation.

                    When the VM continues to run on snapshot(s) (after the VADP software has requested a snapshot consolidate) this is very bad.

                    It will eventually fill up all free space due to enourmous snapshot (delta files) growth.

I asked the question above so that I can confirm whether this setting can prevent this issue from happening again

Hi,

I've been scratching my head now for a while.

We are running EXSI 4.1.0 update 1 (348481), and I can't manage to customize the charts for my VM:s.

Wherever I look, documentation, forums, youtube etc. it says/shows  two buttons "overview" and "advance". I don't have them under my performance tab.

My main goal is to show statistics for 24-h and not 1h which is default. Bu they are all greyed out.

What am I doing wrong?

Thanks

Daniel

On ESXi 4.1 Update2, I have started building a VM and have attached an ISO to the virtual CDROM and it is failing with the following from the vmware.log:

Oct 24 12:05:01.365: vcpu-0| CDROM: Mode Sense for Unsupported Page 0x1B
Oct 24 12:05:01.365: vcpu-0| SCSI DEVICE (ide0:0): MODE SENSE(10) for unsupported page 0x1b
Oct 24 12:05:01.494: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0
Oct 24 12:05:01.494: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0
Oct 24 12:05:01.494: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0
Oct 24 12:05:01.494: vcpu-0| CDROM: Accepting Event Status Notification 0
Oct 24 12:05:01.494: vcpu-0| CDROM: Failed on unsupported 0x4a event 0
Oct 24 12:05:01.495: vcpu-0| CDROM ide0:0: CMD 0x4a (*UNKNOWN (0x4a)*) FAILED (key 0x5 asc 0x24 ascq 0)
Oct 24 12:05:01.495: vcpu-0| CDROM: Unknown command 0xA4.
Oct 24 12:05:01.495: vcpu-0| CDROM ide0:0: CMD 0xa4 (*UNKNOWN (0xa4)*) FAILED (key 0x5 asc 0x20 ascq 0)

I have tried changing this back and forth from ide1:0 and ide0:0 to no avail.  I have seen other posts from years ago with similar issues, but have not found a solid resolution.  I can't get the OS to start loading on the vmdk, so I am kind of stuck.  I am having to do all of this from cli for DR test preflight tests.

The server is an IBM xSeries which actually has the hyper-v onboard for install, but I went ahead and downloaded and installed from disk.  Any and all help is greatly appreciated.

My client has IBM server with ESXI4.1 with Win 2003 Std VM

Want to install IBM external sas tape drive and install symantec on that win 2003 vm

the server and tape drive are compatible and can support win 2003 also

the sas card for tape drive also can support esxi 4.1

How can i make sure that i can configure this tape drive as passthrough to the VM ?

I am trying to create a network bridge between 2 vSwitches using Linux (CentOS 5.4 / 2.6.18-164.15.1 bridge-utils 1.1)- pretty straight forward setup.

vSwitch0 has the physical NICs in the ESXi box connected and promiscuous mode allowed. vSwitch1 has no physical NICs and promiscuous mode allowed as well.  ESXi has 2 VMs, Linux machine with 2 vNICs (one in each vSwitch) and a Windows machine with a single vNIC in vSwitch1.

I've created a ethernet bridge on the Linux machine enslaving both eth0 and eth1, disabled selinux, flushed iptables and ensured both vNICs are up.

With this setup, the windows VM can not get arp replies back over the linux bridge so it never gets the mac address of the physical network GW (a cisco switch in this case). I can see the arp broadcast from the windows VM go over the bridge, and get replied too from the switch... but the reply never makes it back over the linux bridge. The response never gets sent out eth1 in vSwitch1. If I set the GW mac statically in the arp table on the windows machine, everything seems to work- so its only layer 2, ethernet broadcasts that do not seem to be able to make it over the bridge- in only one direction.

Cisco GW <-> Physical host NIC <-> vSwitch0 <-> Linux Machine vNIC eth0 <-> Linux bridge br0 <-> Linux machine vNIC eth1 <-> vSwitch1 <-> Windows vNIC

I know it sounds like a Linux issue, but this is a very basic bridge which works in the physical environment. (i set it up in the lab on physical hardware just to test that i am not forgettting something basic, and it works as expected.)

I can't be the first person to try this- is host bridging of vSwitches not supported?

(The Linux machine will -if this works- end up being a transparent Snort sensor)

Hello

We have experienced a strange ESXi 4.1 IP addressing anomaly where the ESXi host's management IP address is changed to the vMotion address.

In our lab we have 2 ESXi hosts with 6 pNICs.  All pNICS are configured on a single standard vSwitch.  All pNICS are Active (no Standby or Unused) and configured for Route Based on IP hash.  The 6 pNICS are uplinked to a Cisco 3120 stack where Etherchannel is configured.  All works ok so far.

We have found that if the ESXi host has assigned vmk0 to vMotion and vmk1 to Management, upon rebooting the ESXi host the vMotion IP address is shown as the IP address (i.e. the management address) on the DCUI!!!!  When using the DCUI to change the IP address back to its correct IP address, when exiting from the IP configuration screen and restarting the management network the IP address changes back to the vMotion address.

As mentioned earlier, we have narrowed this down to the vmk numbering.  If vmk0 is assigned to vMotion and vmk1 assigned to Management then this issue occurs.  For ESXi hosts that have assigned vmk0 to Management and vmk1 to vMotion this issue does not occur.  To fix the issue we have to remove the vMotion and Management portgroups, then re-create the Management port group which then claims vmk0 and all is ok.

So the question we are trying to answer is why/how ESXi changes the Management vmkernel port from vmk0 to vm1.  We built the hosts ESXi manually so its safe to assume that vmk0 would have been allocated to the Management vmkernel port as this is the first vmkernel port to be created.  Is this expected behaviour to have vmk0 take higher priority?  Should it matter which vmk number is assigned to Management anyway?

I have seen other users post similar observations and it seems Host Profiles is the culprit.  I am surprised VMware have not chimed in to these previous posts considering the impact.  See:

http://communities.vmware.com/message/1521966#1521966

and

http://communities.vmware.com/message/1597396#1597396

I will be logging a call with VMware but would like to hear if anyone who has ESX 4.1 running and has vmk0 assigned to vMotion and vmk1 assigned to Management to reboot the host and report the IP address on the DCUI.

Cheers

gogogo5

We have a LOT of openvz containers running on several host. How to possible convert container to vmdk format?

I want to enable ssh om my esx 4i on the console

i enter unsupported and edit the inetd.conf file, but when i press escape to exit vi nothing happens so i cant save the file

the only way out of i is to press ctrl-z but the the file is not saved.

Dear All,

I am keen to know if it is possible to force SHA1-2 scheme to store password in ESXi host. I am aware that with current ESXi4.1 there exist a workaround to enforce MD5 scheme but could not find any details about using SH1-2.

http://deinoscloud.wordpress.com/2010/07/18/esxi-4-1-major-security-issue-the-sequel-and-the-workaround/

Please let me know if there exist any such method to enable SHA scheme in ESXi 4.1.

Thanks in advance!

Regards,

Ata

Hi folks,

Had a strange problem start yesterday and continuing to today. Trying to log in to a single ESXi 4.1 server (not part of a vCenter setup), and the login screen passes the login stage and is grinding through the inventory load stage, when it loses the connection. I tried using vSphere clients on other PC's (including one plugged into the same switch as the server itself), but the same thing occurs. This server has 8GB RAM and had 18 VM's (mostly low activity, but almost all had 1GB RAM allocations). The VM's themselves are running fine it seems, no lack of CPU, and I don't get the impression there is heavy memory swapping going on because the disks aren't being thrashed and the VM's are responsive. The regular server HTTPS webpage is viewable and I can use the linked HTTPS datastore viewer. I had made no ESXi level setting changes just prior or for some time before this problem started, though I have been recently opening remote console windows to VM's and using the CD connect feature to access some ISO files.

I have tried restarting both the management agents and the management network at the server console, but that didn't fix things. There were sorta similar problems listed in google, that recommended changing the DNS settings to a known working server, but the currently set one is operating correctly ( I did try switching to another DNS server that didn't fix it either so I switched back).

Thankfully I had left SSH access on, so I went diving into /var/log/messages and I see a strange error about no buffer space during the time I attempted to access with the client.

Jan 27 23:25:01 Hostd: [2011-01-27 23:25:01.434 29281B90 verbose 'Proxysvc Req00174'] New proxy client SSL(TCP(local=10.0.1.192:3980, peer=10.0.1.32:443))
Jan 27 23:25:01 Hostd: [2011-01-27 23:25:01.531 FFD19B90 verbose 'HttpSvc.HTTPService'] User agent is 'VMware VI Client/4.0.0'
Jan 27 23:25:01 Hostd: [2011-01-27 23:25:01.531 FFD19B90 verbose 'HttpSvc.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength 374)
Jan 27 23:25:01 Hostd: [2011-01-27 23:25:01.531 FFD19B90 verbose 'HttpSvc.HTTPService'] HTTP Response: Auto-completing at 374/374 bytes
Jan 27 23:25:01 Hostd: [2011-01-27 23:25:01.531 FFD19B90 verbose 'HttpSvc.HTTPService'] HTTP Response: Complete (processed 374 bytes)
Jan 27 23:25:01 Hostd: [2011-01-27 23:25:01.531 FFD19B90 verbose 'HTTP server'] Sent response for HEAD /client/clients.xml (from /usr/lib/vmware/hostd/docroot)
Jan 27 23:25:02 dhclient-uw-4734: XMT: Solicit on vmk1, interval 117
Jan 27 23:25:05 Hostd: [2011-01-27 23:25:05.258 FFDDCB90 verbose 'Proxysvc Req00175'] New proxy client SSL(TCP(local=10.0.1.192:3981, peer=10.0.1.32:443))
Jan 27 23:25:05 Hostd: [2011-01-27 23:25:05.383 FFD19B90 verbose 'Proxysvc Req00176'] New proxy client SSL(TCP(local=10.0.1.192:3982, peer=10.0.1.32:443))
Jan 27 23:25:05 Hostd: [2011-01-27 23:25:05.541 29240B90 verbose 'HttpSvc.HTTPService'] User agent is 'VMware VI Client/4.0.0'
Jan 27 23:25:05 Hostd: [2011-01-27 23:25:05.541 29240B90 verbose 'HttpSvc.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
Jan 27 23:25:05 Hostd: [2011-01-27 23:25:05.542 FFA22E80 verbose 'HttpSvc.HTTPService' opID=A79BC4B6-00000002] HTTP Response: Complete (processed 1219 bytes)
Jan 27 23:25:06 Hostd: [2011-01-27 23:25:06.831 FFA22E80 verbose 'Proxysvc Req00177'] New proxy client SSL(TCP(local=10.0.1.192:3983, peer=10.0.1.32:443))
Jan 27 23:25:06 Hostd: [2011-01-27 23:25:06.835 FFDDCB90 verbose 'HTTP server'] Sent response for HEAD /client/clients.xml (from /usr/lib/vmware/hostd/docroot)
Jan 27 23:25:06 Hostd: [2011-01-27 23:25:06.865 FFD19B90 verbose 'HttpSvc.HTTPService'] User agent is 'VMware VI Client/4.0.0'
Jan 27 23:25:06 Hostd: [2011-01-27 23:25:06.865 FFD19B90 verbose 'HttpSvc.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
Jan 27 23:25:06 Hostd: pam_per_user: create_subrequest_handle(): doing map lookup for user "root"
Jan 27 23:25:06 Hostd: pam_per_user: create_subrequest_handle(): creating new subrequest (user="root", service="system-auth-generic")
Jan 27 23:25:06 Hostd: pam_env(system-auth-generic:setcred): Unable to open config file: /etc/security/pam_env.conf: No such file or directory
Jan 27 23:25:06 Hostd: Accepted password for user root from 10.0.1.192
Jan 27 23:25:06 Hostd: [2011-01-27 23:25:06.872 29281B90 info 'Vimsvc' opID=A79BC4B6-00000003] [Auth]: User root
Jan 27 23:25:06 Hostd: [2011-01-27 23:25:06.873 29281B90 info 'ha-eventmgr' opID=A79BC4B6-00000003] Event 8 : User root@10.0.1.192 logged in
Jan 27 23:25:06 Hostd: [2011-01-27 23:25:06.873 29281B90 verbose 'HttpSvc.HTTPService' opID=A79BC4B6-00000003] HTTP Response: Complete (processed 673 bytes)
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.037 29281B90 verbose 'HttpSvc.HTTPService'] User agent is 'VMware VI Client/4.0.0'
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.037 29281B90 verbose 'HttpSvc.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.039 FFA22E80 verbose 'HttpSvc.HTTPService'] HTTP Response: Complete (processed 12469 bytes)
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.041 29240B90 verbose 'Proxysvc Req00178'] New proxy client SSL(TCP(local=10.0.1.192:3984, peer=10.0.1.32:443))
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.044 FFDDCB90 verbose 'Proxysvc Req00179'] New proxy client SSL(TCP(local=10.0.1.192:3985, peer=10.0.1.32:443))
Jan 27 23:25:07 vmkernel: 61:18:59:13.226 cpu3:9530389)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.078 27FFFB90 warning 'Proxysvc Req00179'] Connection to localhost:8307 failed with error N7Vmacore15SystemExceptionE(Connection reset by peer).
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.078 29281B90 warning 'Proxysvc Req00178'] Connection to localhost:8307 failed with error N7Vmacore15SystemExceptionE(Connection reset by peer).
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.086 FFD19B90 verbose 'Proxysvc Req00180'] New proxy client SSL(TCP(local=10.0.1.192:3986, peer=10.0.1.32:443))
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.116 29281B90 verbose 'Proxysvc Req00181'] New proxy client SSL(TCP(local=10.0.1.192:3987, peer=10.0.1.32:443))
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.119 FFD19B90 verbose 'HttpSvc.HTTPService'] User agent is 'No-User-Agent'
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.120 FFD19B90 verbose 'HttpSvc.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength 545)
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.120 FFD19B90 verbose 'HttpSvc.HTTPService'] HTTP Response: Auto-completing at 545/545 bytes
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.156 FFDDCB90 verbose 'Proxysvc Req00182'] New proxy client SSL(TCP(local=10.0.1.192:3988, peer=10.0.1.32:443))
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.160 27FFFB90 verbose 'HttpSvc.HTTPService'] User agent is 'No-User-Agent'
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.160 27FFFB90 verbose 'HttpSvc.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength 545)
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.160 27FFFB90 verbose 'HttpSvc.HTTPService'] HTTP Response: Auto-completing at 545/545 bytes
Jan 27 23:25:07 vmkernel: 61:18:59:13.323 cpu5:9534698)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.323 cpu5:9534698)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.323 cpu5:9534698)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.323 cpu5:9534698)WARNING: Tcpip: 1313: socreate(type=1, proto=6) failed with error 55
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.168 27FFFB90 verbose 'HttpSvc.HTTPService'] User agent is 'VMware VI Client/4.0.0'
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.175 FFDDCB90 warning 'Proxysvc Req00180'] Connection to localhost:8307 failed with error N7Vmacore15SystemExceptionE(No buffer space available).
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.189 27FFFB90 verbose 'HttpSvc.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.458 29240B90 verbose 'Proxysvc Req00183'] New proxy client SSL(TCP(local=10.0.1.192:3989, peer=10.0.1.32:443))
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.458 FFD19B90 verbose 'Proxysvc Req00184'] New proxy client SSL(TCP(local=10.0.1.192:3990, peer=10.0.1.32:443))
Jan 27 23:25:07 vmkernel: 61:18:59:13.607 cpu6:9656671)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.608 cpu6:9656671)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.608 cpu6:9656671)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.460 292C2B90 warning 'Proxysvc Req00183'] Connection to localhost:8307 failed with error N7Vmacore15SystemExceptionE(No buffer space available).
Jan 27 23:25:07 vmkernel: 61:18:59:13.608 cpu6:9656671)WARNING: Tcpip: 1313: socreate(type=1, proto=6) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.609 cpu5:9531975)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.609 cpu5:9531975)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.609 cpu5:9531975)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.609 cpu5:9531975)WARNING: Tcpip: 1313: socreate(type=1, proto=6) failed with error 55
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.461 29240B90 warning 'Proxysvc Req00184'] Connection to localhost:8307 failed with error N7Vmacore15SystemExceptionE(No buffer space available).
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.462 FFA22E80 verbose 'Proxysvc Req00185'] New proxy client SSL(TCP(local=10.0.1.192:3991, peer=10.0.1.32:443))
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.462 FFD5AB90 verbose 'Proxysvc Req00186'] New proxy client SSL(TCP(local=10.0.1.192:3992, peer=10.0.1.32:443))
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.462 FFDDCB90 verbose 'Proxysvc Req00187'] New proxy client SSL(TCP(local=10.0.1.192:3997, peer=10.0.1.32:443))

Jan 27 23:25:07 vmkernel: 61:18:59:13.618 cpu5:9697632)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.618 cpu7:9534695)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.618 cpu5:9697632)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.618 cpu5:9697632)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.618 cpu5:9697632)WARNING: Tcpip: 1313: socreate(type=1, proto=6) failed with error 55
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.470 29740B90 warning 'Proxysvc Req00186'] Connection to localhost:8307 failed with error N7Vmacore15SystemExceptionE(No buffer space available).
Jan 27 23:25:07 Hostd: [2011-01-27 23:25:07.470 FFD5AB90 warning 'Proxysvc Req00187'] Connection to localhost:8307 failed with error N7Vmacore15SystemExceptionE(No buffer space available).
Jan 27 23:25:07 vmkernel: 61:18:59:13.619 cpu3:9534695)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.619 cpu3:9534695)WARNING: Tcpip: 1313: socreate(type=2, proto=0) failed with error 55
Jan 27 23:25:07 vmkernel: 61:18:59:13.619 cpu3:9534695)WARNING: Tcpip: 1313: socreate(type=1, proto=6) failed with error 55

Jan 27 23:25:13 dhclient-uw-4737: DHCPDISCOVER on vmk4 to 255.255.255.255 port 67 interval 6
Jan 27 23:25:15 dhclient-uw-4738: DHCPDISCOVER on vmk5 to 255.255.255.255 port 67 interval 10
Jan 27 23:25:19 dhclient-uw-4737: DHCPDISCOVER on vmk4 to 255.255.255.255 port 67 interval 15
Jan 27 23:25:25 dhclient-uw-4738: DHCPDISCOVER on vmk5 to 255.255.255.255 port 67 interval 11
Jan 27 23:25:32 dhclient-uw-4735: DHCPDISCOVER on vmk2 to 255.255.255.255 port 67 interval 8
Jan 27 23:25:34 dhclient-uw-4737: DHCPDISCOVER on vmk4 to 255.255.255.255 port 67 interval 15
Jan 27 23:25:36 dhclient-uw-4738: DHCPDISCOVER on vmk5 to 255.255.255.255 port 67 interval 7
Jan 27 23:25:40 dhclient-uw-4735: DHCPDISCOVER on vmk2 to 255.255.255.255 port 67 interval 12
Jan 27 23:25:43 dhclient-uw-4738: DHCPDISCOVER on vmk5 to 255.255.255.255 port 67 interval 12
Jan 27 23:25:48 Hostd: [2011-01-27 23:25:48.547 FFD5AB90 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root
Jan 27 23:25:49 dhclient-uw-4737: DHCPDISCOVER on vmk4 to 255.255.255.255 port 67 interval 13
Jan 27 23:25:52 dhclient-uw-4735: DHCPDISCOVER on vmk2 to 255.255.255.255 port 67 interval 7
Jan 27 23:25:54 Hostd: [2011-01-27 23:25:54.906 FFD5AB90 verbose 'App'] Timed out reading between HTTP requests. : Read timeout after approximately 50000ms. Closing stream TCP(local=127.0.0.1:50341, peer=127.0.0.1:8309)

Wireshark packet capture shows TCP reset packets coming from the server during the inventory load phase it seems, perhaps as a consequence of the socket failure.

ESXTOP is showing a CPU load average around 0.15

ESXTOP for memory is like so

12:23:54am up 61 days 19:58, 280 worlds; MEM overcommit avg: 1.55, 1.55, 1.55
PMEM  /MB:  8181   total:   945     vmk,  6319 other,    917 free
VMKMEM/MB:  7765 managed:   465 minfree,  4486 rsvd,   3278 ursvd,  high state
PSHARE/MB:  3225  shared,   302  common:  2923 saving
SWAP  /MB:   526    curr,   550 rclmtgt:                 0.00 r/s,   0.00 w/s
ZIP   /MB:   510  zipped,   319   saved
MEMCTL/MB:  8746    curr,  8676  target, 11631 max

   GID NAME               MEMSZ    GRANT    SZTGT     TCHD   TCHD_W    SWCUR    SWTGT   SWR/s   SWW/s   OVHDUW     OVHD  OVHDMAX
14080 ISL - TestSML08  1024.00   383.04   356.41    74.52    35.07    31.05    22.73    0.00    0.00    23.43    33.95    90.58
14081 ISL - TestSML09  1024.00   920.68   554.66   194.21   106.81     3.45     0.00    0.00    0.00    23.43    34.60    90.58
14082 ISL - TestSML10  1024.00   261.00   220.31    60.99    28.70    40.00    61.29    0.00    0.00    25.14    37.27    98.51
14088 ISL - XPJPSP3-O  1024.00   471.40   400.06    91.66    53.07     6.26     7.84    0.00    0.00    37.13    49.84   110.57
189477 ISL - TESTSML12  1024.00   246.46   226.98    60.99    21.53    74.39    83.10    0.00    0.00    40.61    54.19   126.39
  1862 A-VC6A3-main     1024.00  1005.11   642.23    81.92    61.44     8.74     0.00    0.00    0.00    54.52    84.30   195.78
90069 ISL - SourceCod  1024.00   177.48   121.35    17.94     3.59   162.43   166.53    0.00    0.00    37.13    49.41   110.57
825689 ISL - TestSML11  1024.00   436.72   479.13   119.82    78.34     6.89     7.81    0.00    0.00    35.48    45.74   102.70
825690 ISL - TESTSML13  1024.00   318.21   322.20   100.46    64.58     6.84     4.11    0.00    0.00    40.61    54.96   126.39
825691 ISL - TESTSML14  1024.00   286.11   265.83    68.17    28.70    35.33    41.10    0.00    0.00    40.61    55.39   126.39
1245163 ISL - HINPOXENA  1024.00   312.15   311.67   147.18    82.57    23.98    12.37    0.00    0.00    37.19    48.37   110.63
2782198 ISL - HINPOXENA  1024.00   975.14   473.27   247.75   118.92     8.13     0.00    0.00    0.00    37.19    48.33   110.63
14074 ISL - HINPOXEND  1024.00   268.11   258.74    50.23    21.53    28.52    52.33    0.00    0.00    35.48    46.66   102.70
14076 ISL - EXCHANGE2  1024.00   679.22   686.25   246.81   119.88     1.33     0.00    0.00    0.00    37.19    49.86   110.63
14077 ISL - TESTSMLIN  1024.00   299.77   222.84    57.44    35.90    31.96    32.29    0.00    0.00    25.14    37.52    98.52
14078 ISL - TESTSML15  1024.00   312.20   374.27   136.32   107.62     4.52     3.62    0.00    0.00    35.48    46.23   102.70
14079 ISL - TestSML07  1024.00   274.05   220.43    60.99    28.70    51.55    55.84    0.00    0.00    25.14    37.09    98.51
2783868 Z-Diver           512.00   509.14   477.72   245.76   204.80     0.98     0.00    0.00    0.00    23.06    31.11    92.40

Some of the google results talked about reserved system memory size. This server was originally installed with 4GB of RAM but was later upgraded 8GB, but I never made changes to the reserved memory. My suspicion is perhaps the reserved memory may be too low, but I am not sure how to check or change this with just command line tools.

There is one related possibility that I don't know how to go about checking. A little before this problem started, from within a VM onboard this server, I had been using a network probe tool called "The Dude" http://www.mikrotik.com/thedude.php (version 4 beta 2) to try mapping out serveral remote subnets elsewhere, accessed via a Vyatta software router VM onboard the server through a single pNIC to the remote subnets. Why I mention this is, in the past when I used an older version 3 of The Dude, I had encountered a problem where various windows IIS HTTP servers became unresponsive for no obvious reason other than I had been using The Dude. Since the vSphere client is basically accessing a HTTPS server on ESXi, it makes me wonder if this is related. I can't say that is the true cause though, because I can still even now access the remote subnets fine via the Vyatta VM, and I had already stopped and shut down The Dude before I had resarted the ESXi managemnt network and agents.

Right now, I am thinking of restarting the server and trying to cut  back on the number of VM's operating as a stopgap measure to fix this, and possibly increase the reserved system memory. Is there anything I can do to avoid restarting the ESXi server to fix connectivity, and/or are there other things/settings I can do prevent this from reoccuring. It's kinda scary to (sort of) lose control of an ESXi server, even if teh VM's are alright.

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).

Hi All,

I have searched these forums relating to an issue we have on our ESXi 4.0 181972 VMware system but cannot put snippets of information I find together into a cohesive answer to solve my urgent problem.

The issue began yesterday after the system sustained an extended power outage that shutdown the entire system. Upon powering on the SAN (MD3000i dual controller) the status led began blinking amber. Uh oh!

I checked around the back of the SAN and noticed the module 0 iSCSI nic's had a link but no activity although the link would periodically dissapear then come back on randomly. Module 1 iSCSI nics were fine.

The long and short of it is that I can boot both host servers which can connect to both storage containers on the SAN and I can also boot all the virtual servers in these containers. Whilst I can do that the servers themselves are running VERY sluggishly.

I have grabbed a number of screenshots from verious sections of the vSphere client which might throw some light on the issue for those that have a far better understanding of VMware than I. The first shot is from the events in the client.

Next is a shot of the configuration - Storage adapter - paths which shows 2 dead links. It references LUN31 but as we only have two storage LUN's this must be the management?

The next two shots are of the SCSI Initiator Dynamic and Static discovery screens.

Next is a shot of the Datastore details. You can get details for both datastores.

Lastly is a shot of the iSCSI Disk Manage Paths screen

The shot above concerns me as there is no target for the second path although if you right click on it and choose copy to clipboard you do get a path.

As the title of the topic says, I am desperate to find a solution to this but I guess I lack to confidence & skills to categorically say this is the answer. It doesnt help that I was not the one that set the system up but which I now must manage.

Any advice would be very gratefully received.

Thanks kindly,

Paul

Hi,

My System specs are as follows:

CPUs: 2x Intel Xeon E5620

Motherboard: Intel S5520HC
Ram: 12x Kingston KVR1066D3D4R7S/4GI for a total of 48GB
USB: 4GB Kingston DataTraveler for booting ESXi 4.1
RAID Controller: Adaptec 6405 (firmware build 18301) with AFM-600 NAND FLASH MEMORY BACKUP for 6 SERIES
HDD: 4x Seagate Constellation ES SAS 1TB ST31000424SS (firmware 0006)

After suffering poor write performance the first time I went ahead and produced a fresh install of ESXi 4.1 Update 1 installed to the usb stick listed above.

I then installed the VMware ESX/ESXi 4.1 Driver CD for PMC Sierra aacraid from http://downloads.vmware.com/d/details/dt_esx41_pmc_aacraid_11728000/ZCV0YnR0aipiZColcA==

After installing and restarting ESXi I could then see the raid array and create a datastore.

Currently the raid is configured as a RAID 10 I have tried RAID 6 with the same poor write performance. Write Cache is forced on and ZMM is at optimal charge!

I have been testing performance with Crystal Disk Mark running in a Windows 2008 R2 x64 VM.

Sequential Read is 286MB/s and Sequential Write is 28MB/s.

On another system which is an i7 950 with Adaptec 5805 with BBU running ESXi 4.1 with the same hard drives but configured in a RAID6.

Sequential Read is 246MB/s and Sequential Write is 207MB/s.

I would like to get the 6405 writing atleast 5x faster than its currently operating instead of sending it off as ewaste!

Thank you in advance for any assistance you can offer me.

Update: Tried Paravirtual SCSI Controller and a vdisk on the Windows vm for a bit of fun. The test results are 325MB/s Sequential Read and 28MB/s Sequential Write.

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.

Hello, all!

We are planning a network upgrade that will put our remote datacenter in the dark for about an hour.  We have two vSphere 4.1 hosts and attendant storage that are HA configured and monitored by the vCenter server in our main datacenter.

We're going to disable host monitoring in the remote cluster.  Is there anything else we should check on to avoid unnecessary alarms or system panics?

Thanks to all for suggestions on this!

Gregg

I have a server with VMWARE ESXi 4.1.0, I disabled network management and when I tried to enable it I got a message which said if I want to reset network management configuration. I can't set up an IP to login with VSphere to manage my virtual machines. Can anyone help me with this issue? It is there a way to copy my virtual machines on another VMWARE enviroment?