Hi Guys,

I have VMWare ESX410-Update02 on my server, trying to install VMWare tools on fresh Centos 6.4 minimal install. Getting this:

What is the location of the directory of C header files that match your running kernel? /usr/src/kernels/2.6.32-358.14.1.el6.x86_64/arch/cris/include

The path "/usr/src/kernels/2.6.32-358.14.1.el6.x86_64/arch/cris/include" is not

valid.

Would you like to change it? [yes]

so I tried various options and no luck so far.

kernel headers are installed:

[root@php55 2.6.32-358.14.1.el6.x86_64]# yum install kernel-devel

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

* base: mirrors.cat.pdx.edu

* epel: dl.fedoraproject.org

* extras: centos.mirror.ndchost.com

* updates: mirrors.bluehost.com

* webtatic: us-east.repo.webtatic.com

Setting up Install Process

Package kernel-devel-2.6.32-358.14.1.el6.x86_64 already installed and latest version

Nothing to do

[root@php55 2.6.32-358.14.1.el6.x86_64]#

[root@php55 2.6.32-358.14.1.el6.x86_64]# ls -l /usr/src/kernels/

total 4

drwxr-xr-x. 22 root root 4096 Aug 14 11:53 2.6.32-358.14.1.el6.x86_64

lrwxrwxrwx.  1 root root   43 Aug 14 11:53 2.6.32-358.el6.x86_64-x86_64 -> /usr/src/kernels/2.6.32-358.14.1.el6.x86_64

[root@php55 2.6.32-358.14.1.el6.x86_64]#

Any ideas?

Please can anyone suggest me a simple method of backing up Esxi Host Configuration which can later be restored  on a freshly installed copy of Esxi( same version) if required. in the event of HDD Failure etc...

Normally, we use vsphere client on Windows Workstations to access Esxi Hosts. I was reading into different posts related backing up using vicfg-cfgbackup command using vCLI or vMA but couldn't really get a step-by-step how to....Will appreciate if someone guides me in a simplest manner possible.

A bit of background to this issue. We have a SAN datastore for a number of servers. Originally we had a single HP Proliant ML 350 G6, connected to the SAN via NFS. The SAN served a number of Linux guest servers which themselves were running NFS to provision shared folders between the Linux OS's.

The problem we found was an inherent slowness in the NFS serving file requests, which caused time stamp issues between shared files. We initially moved the guests from the SAN to the local storage of the HP server. But again, there was still a slowness to NFS running between the the Linux guest OS'S. There isn't standardisation between the Linux guests, so they are a variety of Red Hat, Ubuntu and Fedora. The server is well spec'd with 48GB RAM, Intel Xeon E5530 with two quad core processors, quad 1GB NIC & 15k 300GB SAS drives. The utilisation of all of these resources is well within the thresholds.

The question I have though, is there an optimal configuration for running Linux hosts with share NFS storage on VMware. We are about to invest in some new hardware for these guest OS's. If there is a particular server that handles this better or whether we should buy a server with two disk arrays and controllers and have the NFS run off one & the other configured for the ESXi hosts. Or should we upgrade to ESXi 5.1 if this manages NFS any better. I have seen numerous posts about similar issues, but I would love to know if anyone has nailed a solution or at least got reasonable performance. This seems to be an issues with VMware and NFS run from within the guest OS, but I can't see why.

Thanks,

R.

Hi.

Newbie here to VMWare; in checking an alert for battery status on one of our VMHosts I see a warning with the current state as Assert.  What does this mean?  Furthermore, why would "failed" be normal for several other batteries (with current state: Deassert)?

Thanks in advance!

Hi, we have an HP Proliant ML350 G6 with a p410i RAID controller. The raid was created using 4 1TB disks, as this:

Disk 1: RAID 0

Disks 2-4: RAID 5

The server is running ESXi 4.1 since 2011 without any issue until yesterday.

What we did was installing two new SAS disks, and created a new logical volume using the HP ORCA Setup. Then, when we tried to reboot, the server was trying to boot from the new disks, so, we removed the new disks and deleted the new logical volume, the other two where left untouched.

When we booted again, entering into viClient, in the configuration tab, theres a big "The VMware ESX server does not have persistent storage" label. And I can't access any VM, nor datastore.

From command line, if I do fdisk -l it doesn't show anything.

I've attached my /var/log/messages file for you to check it out.

Does anyone know what can I do to get access to the disks?.

I use Veeam Backup & Replication to backup our VMs and I've been having an issue backing up 1 VM for the past week or more. It has always backed up with no issues in the past and all of my other VMs are backing up just fine. However, after less than a minute, this VM always fails and I get an error that says, "Creating VM snapshot | Error: A snapshot operation cannot be performed." Trying to rule out Veeam as the issue, I just tried creating a snapshot of the server in vSphere and I got the error, "The virtual disk is either corrupted or not a supported format." After looking around, it appears that error usually has something to do with a correct snapshot or an issue after trying to delete a snapshot but this is the first one I've ever done, so I don't think that's the issue. Anywhere else I can look?

Thank you.

I'm running a Windows XP virtual machine on ESX Server 4.0.0 Releasebuild-171294. In this virtual machine I'm running VMwarePlayer and trying to launch another virtual machine. VMware Player installed and launches correctly, but when I try to run a virtual machine, I get this error:

Running VMware Player in a virtual machine requies the outer virtual machine to be configured for running a VMware ESX guest operating system. You may not power on a virtual machine until the outer virtual machine is reconfigured.

I wasn't sure it would work, and it doesn't say that it won't work. The message would seem to indicate that this would actually work. My question is: How do I configure the outer virtual machine to run VMware ESX guest operating system? I've been through the settings and permissions, and I don't see anythin like this. Is it a manual update to the configuration?

Configuration info (as requested):

• What exact version of VMware Player: 3.0.0 build-203739

• What is your host OS and include if it is 32-bit or 64-bit OS. Windows XP 32-bit with latest patches

• What is the guest OS and include if it is 32-bit or 64-bit OS. Not applicable

• Are VMware Tools installed in the guest OS: No (not applicable)

• Are VMware Tools installed in the outer virtual machine: Yes

• How often you see the problem (e.g. all the time, sometimes, rarely, etc.), and if it had previously worked in the same setup (e.g. same virtual machine, same computer): All the time - it has never worked

• What seems to trigger the problematic behavior: Starting a virtual machine in VMware Player

• If there are any conditions where it does work: It never works

In case you are wondering why I would want to run one virtual machine inside another, I am running an application on Linux that I want to virtualize and make available through RDP. Once this application is running, I could telnet to it, but it would be nice to be able to see the machine boot, rahter than just pinging it until it comes up.

Hello,

I have IBM BladeCenter S with two SAS switches and two IBM Blade Servers HS21.Next I have IBM tape library TS3100 with one LTO 4 HH SAS drive connected to one of SAS switches. Both blades have vmWare ESXi 4 installed and they host 3 virtual machines with Windows Server 2003 operating systems.

I added TS3100 into one VM as two SCSI devices (drive and changer) and corectlly installed drivers into guest operating system. There are no errors in Device Manager.

This VM has Microsoft Data Protection Manager 2007 SP1 installed. And here begins my problem, because DPM see only tape drive but no tape changer. When I try to use DPMDriveMappingTool I get error.

c:\Program Files\Microsoft DPM\DPM\bin>DPMDriveMappingTool.exe

Performing Device Inventory ...

Mapping Drives to Library ...

Mapping the Drives in the Library
.\Changer0 failed.

Error Code is: 0x80070001, Error Message is: Incorrect function.

Adding Standalone Drives ...

Writing the Map File ...

Drive Mapping Completed Successfully.

Does anybody meet similar problem? Thanks for any advice.

Hi.

I have a problem when accessing files that are shared on a Windows 2008 Server 64-bit from a Windows 7 client computer. It takes a long time (up to a few minutes) to open i.e. a Word file from the network share. It's not all the time, but quite often.

This also happens on two different client servers with almost the same hardware. Which is a basic IBM x3400 with local harddrives in RAID. I have disabled the TCP/IP Offloading feature on the network adapter inside the VM.

Does anyone have an answer for this? Am I missing something, some configuration maybe? I'm totally lost here...

Regards,

-Satheesh-

We have a large project underway to virtualize our Windows 2003 terminal server farms and I am having an issues with network performance on my VM's.

Here is the scenario:

• My physical TS app server is a Dell 1950 Gen III with dual Quad core procs and 8GB of RAM. A pair of local 146GB, 10K SAS HDD's in RAID-1 config. We use an Intel Dual port PCI-E adapter for our network connectivity (instead of the on-board Broadcom NetExtreme II adapters)
  
• Server is loaded with Windows 2003 Ent x32 with all the latest SP's and Patches and the physical box has the latest firmware and drivers.
  
• We also have a bunch of applications installed that are required for or TS farm.
  
• Typical app server can support up to 80 users before resources become an issue.
  
• From a networking standpoint, the server is attached to two Cisco 2960G edge switches (one port to each switch).  We run our RDP traffic through one switch and our local data access through the other. (We do this because our server farm app load balancer does not use MSNLB; we use a Cisco F5 device to manage connection distribution and it has to own the RDP VLAN.) Note: we only configure 1 gateway address (on the RDP nic) and have static routes in place to direct local traffic to the data NIC in case anyone was worried about multi-homing issues.
  

We have taken one of these app servers (with the exact same HW config) and pulled it from the farm.  we added 1 additional connection to an on-board Broadcom adapter for management purposes so we can use the Intel NIC's as we did before.  Wiped the server and loaded ESXi 4.1..fully patched.

• We have pretty much left the ESXi server in an out of the box config. \
  
• We have three vswitches: vswitch0 for management access to our VCenter server, vSwitch1 for RDP and vSwitch2 for Data. 
  
• Built from scratch a new v7 VM using the paravirtualized SCSI adapter and VMXNET3 adapters. Server is configured with 1 vCPU and 4GB's of RAM, 2 18GB Hard drive VMDK's (configured used the local storage on the server)
  
• Loaded the same software, revision levels, etc that we have on our physical servers.  (BTW, all our servers are built using automation scripts to ensure consistency and minimize any potential user errors in configuration). Obviously, the drivers are different and we do not have Dell OpenManage installed...so technically, it is a little simpler build. Needless to say, we are also running the latest VMWare tools version.
  

So, long story short, with only 1 VM running on ths app server, we wanted to compare performance to the physical to see exactly how we would go about scaling out vs up.

Testing scenario:

• We pulled another physical app server, cleared off all users and rebooted it to make sure it was clean.
  
• We have just 1 VM running on the ESXi app server, also with no users on it.
  
• Part of out testing included running basical log on/off timings as well as application work flows to (with only 1 user logged on the physical and virtual servers).
  

The problem:

We are seeing a significant difference in run times between the two, specifcially for tasks that reach out to network resources, in some cases, the VM is running about 30-40% slower.

What have we tried:

• replacing the vNIC with a VMXNET2, e1000 and flexible....result...performance became even worse
  
• went down to a single nic configuration....no change.
  
• increased CPU and Memory...no change
  
• when down to a single vSwitch config...no change
  
• tried using broadcom NIC instead of the intel....still, no change.
  
• We through every option available in the guest OS for the VMXNET3 adapter...most had no effect, others made things way worse.
  

Bottom line, we expect (hopefully correctly) that with only 1 user on a single VM running on a server exactly configured like a physical, that the performance should be the same...but it is not.  I know that there is a substantial amount of tuning paramters available in ESXi under Advanced Setting/NET...but I have not found ANY guide out there that explains in lamens terms what those setting are supposed to do nor have I found anything out there that says: 'heres how to configure VMWare to optimize networking for Terminal services and/or network based applications that require low-latency."

So, lot's of info here, but I am at a point where i need to start asking for help from those that may have actually encoutered this behavior before.  ANY input/suggestions would be much appreciated as this is a show-stopper for us moving forward in our Virtualization project.

Greetings,

As far as I can tell there is still an 8 vCPU limit to guest in 4.1 and to a single vCPU for FT.

As of 4.1u1 we can assign multiple cores to a vCPU.

Does this mean I can work around the 8 vCPU limit and the 1vCPU limits noted above by assigning multiple cores?

As an example, if I have a Win2008R2 Enterprise guest needing 12 cores, could I assign 6 vCPU each with dual cores thereby bypassing the 8 vCPU limit?

Or at the end of the day will vSphere realize the math and limit the build?

Thanks

Rick

Hello All,

I am running one VM with 12G & another is 4G RAM.Wile tkaing snapshot it taking long time.file vmsn with 12G is already created but dont know why its taking so much time.At 95% get stuck but from 1hr its show 100%.Dont know why is happening.I am using Netapp NFS Storage.

Regads

Ankit

I have ESXi 4.0.0, 208167, server trying to install VMWare tools on Ubuntu 11.10 I'm getting the following error:

***************************************************************************************************************************************

Unable to create symlink "/usr/lib64/libvmcf.so" pointing to file "/usr/lib/vmware-tools/lib64/libvmcf.so/libvmcf.so".

***************************************************************************************************************************************

Any ideas???

Thanks

Here's the complete log after trying to install the second time:

***************************************************************************************************************************************

The removal of VMware Tools 4.0.0 build-208167 for Linux completed
successfully.

Installing VMware Tools.

In which directory do you want to install the binary files?
[/usr/bin]

What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc]

What is the directory that contains the init scripts?
[/etc/init.d]

In which directory do you want to install the daemon files?
[/usr/sbin]

In which directory do you want to install the library files?
[/usr/lib/vmware-tools]

In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]

The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]

The installation of VMware Tools 4.0.0 build-208167 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]

Unable to create symlink "/usr/lib64/libvmcf.so" pointing to file
"/usr/lib/vmware-tools/lib64/libvmcf.so/libvmcf.so".

Execution aborted.

***************************************************************************************************************************************

I'm having this problem with an ESXi 4.1 host on an almost weekly basis - the host suddenly becomes unresponsive and the guests appear to be completely dead. I can still navigate through the vSphere Client but cannot perform any tasks, and the VM console screens are blank. The VMs appear to be running (according to status in vSphere Client), but I cannot ping them or connect to them in any way. I try the reboot from the DCUI but it does nothing - I end up having to power cycle the server to get it working again.

I have looked in /scratch/log/messages on the host and do not see anything obvious. Here's the last few minutes before the last time it hung:

Oct 24 14:22:48 Hostd: [2011-10-24 14:22:48.055 343F0B90 error 'App'] Failed to read header on stream TCP(local=127.0.0.1:51337, peer=127.0.0.1:0): N7Vmacore15SystemExceptionE(Connection reset by p
Oct 24 14:22:48 Hostd: [2011-10-24 14:22:48.068 33F2EB90 verbose 'Proxysvc Req01002'] New proxy client SSL(TCP(local=193.120.91.121:60914, peer=193.120.91.2:443))                                  
Oct 24 14:22:58 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:22:58 Hostd: [2011-10-24 14:22:58.866 33F2EB90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:23:27 Hostd: [2011-10-24 14:23:27.863 33F2EB90 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root                                                                           
Oct 24 14:23:58 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:23:58 Hostd: [2011-10-24 14:23:58.923 33F6FB90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:24:58 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:24:58 Hostd: [2011-10-24 14:24:58.983 342DBB90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:24:59 Hostd: [2011-10-24 14:24:59.304 FFEC5E80 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root                                                                           
Oct 24 14:25:59 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:25:59 Hostd: [2011-10-24 14:25:59.038 33F2EB90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:26:29 Hostd: [2011-10-24 14:26:29.926 33EEDB90 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root                                                                           
Oct 24 14:26:59 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:26:59 Hostd: [2011-10-24 14:26:59.092 343F0B90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:27:13 Hostd: [2011-10-24 14:27:13.010 33F2EB90 verbose 'Proxysvc Req01003'] New proxy client TCP(local=127.0.0.1:57757, peer=127.0.0.1:80)                                                
Oct 24 14:27:13 Hostd: [2011-10-24 14:27:13.011 344B1B90 info 'Vmomi'] Activation [N5Vmomi10ActivationE:0x34708c28] : Invoke done [waitForUpdates] on [vmodl.query.PropertyCollector:ha-property-coll
Oct 24 14:27:13 Hostd: [2011-10-24 14:27:13.011 344B1B90 verbose 'Vmomi'] Arg version:                                                                                                              
Oct 24 14:27:13 Hostd: "50"                                                                                                                                                                         
Oct 24 14:27:13 Hostd: [2011-10-24 14:27:13.012 344B1B90 info 'Vmomi'] Throw vmodl.fault.RequestCanceled                                                                                            
Oct 24 14:27:13 Hostd: [2011-10-24 14:27:13.012 344B1B90 info 'Vmomi'] Result:                                                                                                                      
Oct 24 14:27:13 Hostd: (vmodl.fault.RequestCanceled) {                                                                                                                                              
Oct 24 14:27:13 Hostd:    dynamicType = <unset>,                                                                                                                                                    
Oct 24 14:27:13 Hostd:    faultCause = (vmodl.MethodFault) null,                                                                                                                                    
Oct 24 14:27:13 Hostd:    msg = "",                                                                                                                                                                 
Oct 24 14:27:13 Hostd: }                                                                                                                                                                            
Oct 24 14:27:13 Hostd: [2011-10-24 14:27:13.012 342DBB90 error 'App'] Failed to read header on stream TCP(local=127.0.0.1:62851, peer=127.0.0.1:0): N7Vmacore15SystemExceptionE(Connection reset by p
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:13 sfcb-vmware_base[5907]: LsaFindUserByName: 40008                                                                                                                                    
Oct 24 14:27:46 Hostd: [2011-10-24 14:27:46.929 342DBB90 verbose 'DvsManager'] PersistAllDvsInfo called                                                                                             
Oct 24 14:27:59 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:27:59 Hostd: [2011-10-24 14:27:59.148 3436DB90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:28:00 Hostd: [2011-10-24 14:28:00.549 33EEDB90 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root                                                                           
Oct 24 14:28:59 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:28:59 Hostd: [2011-10-24 14:28:59.203 33F2EB90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:29:31 Hostd: [2011-10-24 14:29:31.171 33EEDB90 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root                                                                           
Oct 24 14:29:59 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:29:59 Hostd: [2011-10-24 14:29:59.260 33F2EB90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:30:59 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:30:59 Hostd: [2011-10-24 14:30:59.316 342DBB90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'                                                                           
Oct 24 14:31:02 Hostd: [2011-10-24 14:31:02.675 343F0B90 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root                                                                           
Oct 24 14:31:59 nssquery: Group lookup failed for 'S3\ESX Admins'                                                                                                                                   
Oct 24 14:31:59 Hostd: [2011-10-24 14:31:59.374 34431B90 warning 'UserDirectory'] Group lookup failed for 'S3\ESX Admins'

Then there is nothing and at 14:43:35 I rebooted the machine. I don't really understand most of the above log, but none of it looks critical to me. I can't see any obvious errors on the VMs either, and they're not under any high load.

Host hardware:

• Dell PowerEdge R210
• Xeon X3440 (quad core + HT)
• 8 GB RAM
• Dell SAS 6/iR RAID controller
• 2x 250 GB SATA disks in RAID 1 array
• Broadcom BCM5716 onboard NIC (NIC teamimg set up in ESXi)

• BIOS 1.8.2, iDRAC 6 Express firmware 1.80, Lifecycle Controller firmware 1.4.0.445, RAID controller firmware up-to-date

VMs:

• RHEL 5.7 desktop (64-bit)
• CentOS 5.7 (64-bit)
• Windows XP Professional SP3 (32-bit) - this is only used on occasions and was not running the last time the host failed

I have an iSCSI target set up on this (there was a Windows 2008 R2 domain controller on this too but I moved it to another host due to unreliability with this one) but it was failing before this was configured. I have installed patches on the host so it is currently running 4.1.0 Build 433742. Guests are also reasonably up to date. However this problem has been happening for a few months, even before I upgraded to U1.

I noticed one time the system failed that upon restarting, ESXi was reporting (in Configuration -> Health Status) that one of the disks in the array was rebuilding. I have not noticed this happen again, and the rebuild was successfull.

I ran Dell Diagnostics and MemTest (one pass) on the machine and everything seemed ok. There are no errors in the iDRAC event logs.

Any ideas what could be wrong?

My esxi with 10 vms has been working great during 2.5 days and then crash with the following exception :

(Hardware details)

I7 3770

32gb ram

ESXI 5.1 - 799733 x86_64

2x 3Tb 7200t

4Vms Windows 2012

4 Vms Ubuntu 12.10

1 Pfsense 2.1 (freebsd)

1 NexentaStor

2012-11-16T16:15:35.233Z cpu6:4102)World: 8381: PRDA 0x418041800000 ss 0x0 ds 0x4018 es 0x4018 fs 0x4018 gs 0x4018

2012-11-16T16:15:35.233Z cpu6:4102)World: 8383: TR 0x4020 GDT 0x4122001a1000 (0x402f) IDT 0x41800b112000 (0xfff)

2012-11-16T16:15:35.233Z cpu6:4102)World: 8384: CR0 0x80010031 CR3 0x125f24000 CR4 0x42768

2012-11-16T16:15:35.238Z cpu6:4102)Backtrace for current CPU #6, worldID=4102, ebp=0x41220019bc10

2012-11-16T16:15:35.239Z cpu6:4102)0x41220019bc10:[0x41800b052105]IRQ_DoInterrupt@vmkernel#nover+0x5c stack: 0x0, 0x418041800180, 0x0,

2012-11-16T16:15:35.239Z cpu6:4102)0x41220019bc50:[0x41800b04bd92]IDT_IntrHandler@vmkernel#nover+0x139 stack: 0x41220019bd68, 0x41800b

2012-11-16T16:15:35.239Z cpu6:4102)0x41220019bc60:[0x41800b110064]gate_entry@vmkernel#nover+0x63 stack: 0x4018, 0x4018, 0x0, 0x0, 0x0

2012-11-16T16:15:35.240Z cpu6:4102)0x41220019bd68:[0x41800b2dbd6f]Power_HaltPCPU@vmkernel#nover+0x276 stack: 0x41220019be68, 0x4122001

2012-11-16T16:15:35.240Z cpu6:4102)0x41220019be68:[0x41800b1bd114]CpuSchedIdleLoopInt@vmkernel#nover+0x873 stack: 0x41220019be98, 0x41

2012-11-16T16:15:35.240Z cpu6:4102)0x41220019be78:[0x41800b1c66ae]CpuSched_IdleLoop@vmkernel#nover+0x15 stack: 0x6, 0x6, 0x41220019bfe

2012-11-16T16:15:35.241Z cpu6:4102)0x41220019be98:[0x41800b04f6ce]Init_SlaveIdle@vmkernel#nover+0x49 stack: 0x0, 0x0, 0x0, 0x0, 0x0

2012-11-16T16:15:35.241Z cpu6:4102)0x41220019bfe8:[0x41800b2e1f86]SMPSlaveIdle@vmkernel#nover+0x31d stack: 0x0, 0x0, 0x0, 0x0, 0x0

2012-11-16T16:15:35.241Z cpu6:4102)VMware ESXi 5.1.0 [Releasebuild-799733 x86_64]

#PF Exception 14 in world 4102:idle6 IP 0x41800b052105 addr 0x417fd1837b01

2012-11-16T16:15:35.242Z cpu6:4102)cr0=0x8001003d cr2=0x417fd1837b01 cr3=0xcdff6000 cr4=0x216c

2012-11-16T16:15:35.242Z cpu6:4102)frame=0x41220019bae0 ip=0x41800b052105 err=0 rflags=0x10006

2012-11-16T16:15:35.242Z cpu6:4102)rax=0x66f1400 rbx=0x41220019bc50 rcx=0x41800b2dbd6f

2012-11-16T16:15:35.242Z cpu6:4102)rdx=0x417fcb146700 rbp=0x41220019bc10 rsi=0x41220019bc70

2012-11-16T16:15:35.242Z cpu6:4102)rdi=0x19bc50 r8=0x4100018d29b0 r9=0x4ca88b

2012-11-16T16:15:35.242Z cpu6:4102)r10=0xdf r11=0x1 r12=0x4122001a7000

2012-11-16T16:15:35.242Z cpu6:4102)r13=0x19bc50 r14=0x41220019bc70 r15=0x1

2012-11-16T16:15:35.242Z cpu6:4102)pcpu:0 world:6211 name:"vmm1:Windows_2012_-_SQL" (V)

2012-11-16T16:15:35.242Z cpu6:4102)pcpu:1 world:4109 name:"directMapUnmap" (S)

2012-11-16T16:15:35.242Z cpu6:4102)pcpu:2 world:6255 name:"vmm0:NexentaStor" (V)

2012-11-16T16:15:35.242Z cpu6:4102)pcpu:3 world:6194 name:"vmm0:Windows_2012_-_App" (V)

2012-11-16T16:15:35.242Z cpu6:4102)pcpu:4 world:6207 name:"vmm0:Windows_2012_-_SQL" (V)

2012-11-16T16:15:35.242Z cpu6:4102)pcpu:5 world:5855 name:"vmm0:Windows_2012_-_AD" (V)

2012-11-16T16:15:35.242Z cpu6:4102)pcpu:6 world:4102 name:"idle6" (IS)

2012-11-16T16:15:35.242Z cpu6:4102)pcpu:7 world:4103 name:"idle7" (IS)

2012-11-16T16:15:35.242Z cpu6:4102)@BlueScreen: #PF Exception 14 in world 4102:idle6 IP 0x41800b052105 addr 0x417fd1837b01

2012-11-16T16:15:35.242Z cpu6:4102)Code start: 0x41800b000000 VMK uptime: 2:11:18:25.729

2012-11-16T16:15:35.242Z cpu6:4102)0x41220019bc10:[0x41800b052105]IRQ_DoInterrupt@vmkernel#nover+0x5c stack: 0x0

2012-11-16T16:15:35.243Z cpu6:4102)0x41220019bc50:[0x41800b04bd92]IDT_IntrHandler@vmkernel#nover+0x139 stack: 0x41220019bd68

2012-11-16T16:15:35.243Z cpu6:4102)0x41220019bc60:[0x41800b110064]gate_entry@vmkernel#nover+0x63 stack: 0x4018

2012-11-16T16:15:35.244Z cpu6:4102)0x41220019bd68:[0x41800b2dbd6f]Power_HaltPCPU@vmkernel#nover+0x276 stack: 0x41220019be68

2012-11-16T16:15:35.244Z cpu6:4102)0x41220019be68:[0x41800b1bd114]CpuSchedIdleLoopInt@vmkernel#nover+0x873 stack: 0x41220019be98

2012-11-16T16:15:35.244Z cpu6:4102)0x41220019be78:[0x41800b1c66ae]CpuSched_IdleLoop@vmkernel#nover+0x15 stack: 0x6

2012-11-16T16:15:35.245Z cpu6:4102)0x41220019be98:[0x41800b04f6ce]Init_SlaveIdle@vmkernel#nover+0x49 stack: 0x0

2012-11-16T16:15:35.245Z cpu6:4102)0x41220019bfe8:[0x41800b2e1f86]SMPSlaveIdle@vmkernel#nover+0x31d stack: 0x0

2012-11-16T16:15:35.247Z cpu6:4102)base fs=0x0 gs=0x418041800000 Kgs=0x0

2012-11-16T16:15:35.247Z cpu6:4102)vmkernel             0x0 .data 0x0 .bss 0x0

Can you help me finding the cause / solution for this issue

Thanks

All of a sudden, we are not able to deploy from a template to one of our ESXi 4.1 U3 clusters.  It goes to 87% and then we get "Could not complete network copy for file".  We can deploy from this same template to other clusters.  I SSH'ed to the host we happen to be deploying to and noticed the following errors get logged in the messages log as it's happening.

Feb  8 17:18:48 vmkernel: .... cpu2:5469)BC: 2591: Blocking due to no free buffers. nDirty = 1764 nWaiters = 3

Anyone seen this before?  I've opened a SR.

Also, I should mention, though it could be unrelated - We've had a few strange HA issues that have affected at least this cluster and another cluster intermittently, where the HA Agent thinks it can't talk to other slaves/master, though if you manually ping from the host as it's happening the replies come back just fine.  When this happens, the logs spew messages such as "...XXX.XXX.XXX.XXX (IPs of other hosts in cluster) is bad IP", etc.

Is there a way to configure VMWare ESXi 4.1 to recognize only 1 instead of 2 processor sockets?  An application's licensing only supports one socket, and I was surprised to find there were two on my server.  I had found this article www.swuve.com/?p=63 that gives the instructions below, but I have not found this configuration discussed anywhere else, and am skeptical. 

1. Modify the VMkernel.Boot.maxPCPUS setting
2. This is listed under Configuration -> Software -> Advanced Settings ->VMKernel -> Boot
3. The number you put here depends on your configuration.  For instance, if you have a 4 proc by 4 core system and you want to reduce the number of physical processors to 2 and maximize the logical processors, you would put 8 as the number. 2x4.
4. If you have a 4 proc by 2 core system and you want to reduce the number of physical processors to 2 and maximize the logical processors, you would put 4 as the number. 2x2

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

After a few months running esxi4.1 on a supermicro server with a areca 1212 raid controller following errors show up after POSD:

Disks are in RAID 1.

Any help aprreciated.

WARNING: LinScsi: SCSILinuxAbortCommands: Failed, Driver ARCMSR ARECA SATA/SAS RAID ControllerDriver Version 1.20.00.15.vmk.100202, for vmhba2 [0m
[7m66:16:44:51.630 cpu0:10101331)WARNING: arcmsr5: abort device command(0xe01fc00) of scsi id = 0 lun = 0  [0m
[7m66:16:44:51.630 cpu0:10101331)WARNING: LinScsi: SCSILinuxAbortCommands: Failed, Driver ARCMSR ARECA SATA/SAS RAID ControllerDriver Version 1.20.00.15.vmk.100202, for vmhba2 [0m
[7m66:16:44:51.843 cpu0:10101331)WARNING: arcmsr5: abort device command(0xe030400) of scsi id = 0 lun = 0  [0m
[7m66:16:44:51.843 cpu0:10101331)

and

WARNING: LinScsi: SCSILinuxAbortCommands: Failed, Driver ARCMSR ARECA SATA/SAS RAID ControllerDriver Version 1.20.00.15.vmk.100202, for vmhba2 [0m
[7m66:16:45:19.941 cpu1:4161)WARNING: LinScsi: SCSILinuxAbortCommands: Failed, Driver ARCMSR ARECA SATA/SAS RAID ControllerDriver Version 1.20.00.15.vmk.100202, for vmhba2 [0m
[7m66:16:45:19.941 cpu1:4161)WARNING: arcmsr5: abort device command(0xe02e800) of scsi id = 0 lun = 1  [0m
66:16:45:21.018 cpu0:4098)<5>arcmsr5: pCCB ='0x0x4100b50e9400' isr got aborted command
66:16:45:21.018 cpu0:4098)<5>arcmsr5: isr get an illegal ccb command     done acb = '0x0x41000b813588'ccb = '0x0x4100b50e9400' ccbacb = '0x0x41000b813588' startdone = 0x0 ccboutstandingcount = 41
[31;1m66:16:45:21.018 cpu0:4098)ALERT: LinScsi: SCSILinuxCmdDone: Attempted double completion [0m
66:16:45:21.019 cpu0:4098)Backtrace for current CPU #0, worldID=4098, ebp=0x417f800179a8
66:16:45:21.019 cpu0:4098)0x417f800179a8:[0x4180278577b5]PanicLogBacktrace@vmkernel:nover+0x18 stack: 0x417f800179d8, 0x417f8
66:16:45:21.019 cpu0:4098)0x417f80017ae8:[0x4180278579f4]PanicvPanicInt@vmkernel:nover+0x1ab stack: 0x417f80017bd8, 0x4180278
66:16:45:21.020 cpu0:4098)0x417f80017af8:[0x418027857fdd]Panic_vPanic@vmkernel:nover+0x18 stack: 0x3000000008, 0x417f80017be8
66:16:45:21.020 cpu0:4098)0x417f80017bd8:[0x41802788a572]vmk_Panic@vmkernel:nover+0xa1 stack: 0x24c0, 0xd0b50e9400, 0x417f800
66:16:45:21.021 cpu0:4098)0x417f80017c48:[0x418027c6a35e]SCSILinuxCmdDone@esx:nover+0x2c1 stack: 0x202, 0x418027d78e38, 0x410
66:16:45:21.021 cpu0:4098)0x417f80017c88:[0x418027d78df6]arcmsr_interrupt@esx:nover+0x241 stack: 0xd000000023, 0x418027d78e38
66:16:45:21.021 cpu0:4098)0x417f80017cc8:[0x418027c7bd38]Linux_IRQHandler@esx:nover+0x77 stack: 0xd0, 0x417f80017d08, 0x417f8
66:16:45:21.021 cpu0:4098)0x417f80017d58:[0x418027832201]IDTDoInterrupt@vmkernel:nover+0x348 stack: 0x4100b6030150, 0x417f800
66:16:45:21.022 cpu0:4098)0x417f80017d98:[0x4180278324da]IDT_HandleInterrupt@vmkernel:nover+0x85 stack: 0x2637d9eee01956, 0x4
66:16:45:21.022 cpu0:4098)0x417f80017db8:[0x418027832e2d]IDT_IntrHandler@vmkernel:nover+0xc4 stack: 0x417f80017ec0, 0x418027a
66:16:45:21.022 cpu0:4098)0x417f80017dc8:[0x4180278da747]gate_entry@vmkernel:nover+0x46 stack: 0x4018, 0x4018, 0x0, 0x0, 0x0
66:16:45:21.023 cpu0:4098)0x417f80017ec0:[0x418027aacb36]Power_HaltPCPU@vmkernel:nover+0x27d stack: 0x417f80017f70, 0x1, 0x26
66:16:45:21.023 cpu0:4098)0x417f80017fd0:[0x4180279cbe1e]CpuSchedIdleLoopInt@vmkernel:nover+0x985 stack: 0x417f80017ff0, 0x41
66:16:45:21.024 cpu0:4098)0x417f80017fe0:[0x4180279d15ee]CpuSched_IdleLoop@vmkernel:nover+0x15 stack: 0x417f80017ff8, 0x0, 0x
66:16:45:21.024 cpu0:4098)0x417f80017ff0:[0x418027834916]HostPCPUIdle@vmkernel:nover+0xd stack: 0x0, 0x0, 0x0, 0x0, 0x0
66:16:45:21.024 cpu0:4098)0x417f80017ff8:[0x0]<unknown> stack: 0x0, 0x0, 0x0, 0x0, 0x0
66:16:45:21.025 cpu0:4098) [45m [33;1mVMware ESXi 4.1.0 [Releasebuild-260247 X86_64] [0m
66:16:45:21.025 cpu0:4098)Failed at vmkdrivers/src_v4/vmklinux26/vmware/linux_scsi.c:2190 -- NOT REACHED
66:16:45:21.025 cpu0:4098)cr0=0x80010039 cr2=0x0 cr3=0x10ce1000 cr4=0x16c
66:16:45:21.025 cpu0:4098)pcpu:0 world:4098 name:"idle0" (I)
66:16:45:21.025 cpu0:4098)pcpu:1 world:7146 name:"sfcb-vmware_bas" (U)
@BlueScreen: Failed at vmkdrivers/src_v4/vmklinux26/vmware/linux_scsi.c:2190 -- NOT REACHED
66:16:45:21.025 cpu0:4098)Code start: 0x418027800000 VMK uptime: 66:16:45:21.025
66:16:45:21.025 cpu0:4098)0x417f80017af8:[0x418027857fd8]Panic_vPanic@vmkernel:nover+0x13 stack: 0x3000000008
66:16:45:21.026 cpu0:4098)0x417f80017bd8:[0x41802788a572]vmk_Panic@vmkernel:nover+0xa1 stack: 0x24c0
66:16:45:21.026 cpu0:4098)0x417f80017c48:[0x418027c6a35e]SCSILinuxCmdDone@esx:nover+0x2c1 stack: 0x202
66:16:45:21.026 cpu0:4098)0x417f80017c88:[0x418027d78df6]arcmsr_interrupt@esx:nover+0x241 stack: 0xd000000023
66:16:45:21.027 cpu0:4098)0x417f80017cc8:[0x418027c7bd38]Linux_IRQHandler@esx:nover+0x77 stack: 0xd0
66:16:45:21.027 cpu0:4098)0x417f80017d58:[0x418027832201]IDTDoInterrupt@vmkernel:nover+0x348 stack: 0x4100b6030150
66:16:45:21.027 cpu0:4098)0x417f80017d98:[0x4180278324da]IDT_HandleInterrupt@vmkernel:nover+0x85 stack: 0x2637d9eee01956
66:16:45:21.028 cpu0:4098)0x417f80017db8:[0x418027832e2d]IDT_IntrHandler@vmkernel:nover+0xc4 stack: 0x417f80017ec0
66:16:45:21.028 cpu0:4098)0x417f80017dc8:[0x4180278da747]gate_entry@vmkernel:nover+0x46 stack: 0x4018
66:16:45:21.028 cpu0:4098)0x417f80017ec0:[0x418027aacb36]Power_HaltPCPU@vmkernel:nover+0x27d stack: 0x417f80017f70
66:16:45:21.029 cpu0:4098)0x417f80017fd0:[0x4180279cbe1e]CpuSchedIdleLoopInt@vmkernel:nover+0x985 stack: 0x417f80017ff0
66:16:45:21.029 cpu0:4098)0x417f80017fe0:[0x4180279d15ee]CpuSched_IdleLoop@vmkernel:nover+0x15 stack: 0x417f80017ff8
66:16:45:21.030 cpu0:4098)0x417f80017ff0:[0x418027834916]HostPCPUIdle@vmkernel:nover+0xd stack: 0x0
66:16:45:21.030 cpu0:4098)0x417f80017ff8:[0x0]<unknown> stack: 0x0
66:16:45:21.038 cpu0:4098)FSbase:0x0 GSbase:0x418040000000 kernelGSbase:0x0
66:16:45:21.018 cpu0:4098)LinScsi: SCSILinuxCmdDone: Attempted double completion
0:00:00:28.899 cpu1:4825)Elf: 3028: Kernel module arcmsr was loaded, but has no signature attached
Coredump to disk.
Slot 1 of 1.
storage message on vmhba32: Bulk command transfer result=0
                         usb storage message on vmhba32: Bulk data transfer result 0x1
0:00:00:46.061 cpu0:5552)ScsiScan: 1059: Path 'vmhba1:C0:T0:L0': Vendor: 'TEAC    '  Model: 'DV-28S-W        '  Rev: '1.2A'
0:00:00:46.061 cpu0:5552)ScsiScan: 1062: Path 'vmhba1:C0:T0:L0': Type: 0x5, ANSI rev: 5, TPGS: 0 (none)
0:00:00:46.063 cpu0:5552)ScsiUid: 273: Path 'vmhba1:C0:T0:L0' does not support VPD Device Id page.
0:00:00:46.072 cpu0:5552)VMWARE SCSI Id: Could not get disk id for vmhba1:C0:T0:L0
0:00:00:46.073 cpu0:5552)ScsiScan: 1059: Path 'vmhba2:C0:T16:L0': Vendor: 'Areca   '  Model: 'RAID controller '  Rev: 'R001'
0:00:00:46.073 cpu0:5552)ScsiScan: 1062: Path 'vmhba2:C0:T16:L0': Type: 0x3, ANSI rev: 0, TPGS: 0 (none)
[7m0:00:00:46.073 cpu0:5552)WARNING: ScsiScan: 116: Path 'vmhba2:C0:T16:L0': Unsupported pre SCSI-2 device (ansi=0) [0m
0:00:00:46.073 cpu0:5552)ScsiScan: 1059: Path 'vmhba2:C0:T0:L0': Vendor: 'Areca   '  Model: 'ARC-1212-VOL#000'  Rev: 'R001'
0:00:00:46.073 cpu0:5552)ScsiScan: 1062: Path 'vmhba2:C0:T0:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
0:00:00:46.073 cpu0:5552)ScsiScan: 1059: Path 'vmhba2:C0:T0:L1': Vendor: 'Areca   '  Model: 'ARC-1212-VOL#001'  Rev: 'R001'
0:00:00:46.073 cpu0:5552)ScsiScan: 1062: Path 'vmhba2:C0:T0:L1': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
0:00:00:46.075 cpu0:4493)usb storage warning (0 throttled) on vmhba32 (SCSI cmd INQUIRY): clearing endpoint halt for pipe 0xc0008280
                         usb storage message on vmhba32: scsi cmd done

Hi All,

I have deployed OVF ( CentOS VM image) on ESXi 4.1 server host but found the following martian source messages on CentOS guest OS console after booting completed.

Following messeges keep flooding on VM console and log files also:

..

Martian source 255.255.255.255 from <ip 1>, on dev eth0 II header ff:ff:ff:ff:ff:ff:00:1b:42:33:0a:08:00

Martian source 255.255.255.255 from <ip 2>, on dev eth0 ll header ff:ff:ff:ff:ff:ff:00:2b:35:43:0c:08:00

..

Additional info:

While booting up VM, found the following failed message on eth0.

               Determining IP information for eth0 ..... failed.

Appreciate for your help.