I am trying to patch ESXi 5.5 4345813 with vCenter Server 5.5 3721164. But getting error during scan. Its working fine with another ESXi 5.5 2068190.
"The host returns esxupdate error code:99. An unhandled exception was encountered. Check the Update Manager log files and esxupdate log files for more details."
Hello,
Our ESXi (5.5u2) hosts use a NetApp NFS storage (FAS2240) for datastores. The NetApp device is using 1 Gb connections, and we added recently 10 Gb interfaces, configured with IP addresses on another subnet.
The idea is to redeploy hosts with NFS mounts pointing to the new IP addresses on the 10 Gb network.
Unfortunately, ESXi computes an UUID for NFS datastores based on the IP address and the NFS share name, so it considers the datastores as different.
I think we can shutdown the VM, change the references to datastores in config files and register them to the redeployed hosts, or use SVMotion to move VM between datastores, but both solutions are a bit painful...
Is there another solution which would avoid downtime or SVMotion ? Is it possible to mount the NFS datastores by forcing the UUID to a specific value ?
Thanks in advance,
Christophe
I am currently running ESXi 5.5 passing through a LSI SAS 3041E SAS card. I don't intend to use Raid, I just need to pass through SATA drives directly to a VM. The 3041E is working fine but does not support 3TB drives and I would like to have more than 4 ports.
Is there a current 2017 cheap SAS card with the following specs:
Thanks!
I need to query a vCenter 5.5 server member of a vSphere 5.5 infrastructure via SNMP from an Ubuntu server on the same LAN.
I enabled Reciever 2 for the IP of the vCenter server for port 162 and community "public" but I from the Ubunti server I am unable to get any information from the vCente server.
I simply get no answer while the Ubuntu server can query other servers in the same LAN with non problem.
What else should I do on the vCenter server?
Whare can I locate any sample of correct syntax commands to query the vCenter server via SNMP from the Ubuntu server?
Regards
marius
I have an IBM x3500M3 running ESXi 5.0 (474610) that seems to have lost it's IMM IP address. The server is at a remote location so it's not easy to get in to check the settings in the BIOS. After some googling it seems I can check the settings using the IBM ASU tool but I can't work out how to run this tool within ESXi.
Is it possible to run ASU on a running ESXi machine? If so how can it be done?
Thanks for any help,
Colin
Hello,
Does anyone know how to collect the ESXi host CPU model through command line? I do not want to use Get-VM or PowerCLI. I need it to be via esxcli or something similar.
Thanks in advance.
Victor Fonseca.
Hi,
What needs to be done in the "Network" section of the hypervisor host in order to allow my guest Windows vm access ISCSI SAN that is on a VLAN?
Thanks in advance,
I am unable to create a snapshot on a VM that has a 2TB HArd disk 2. This is running on ESXi 5.1
any idea how I can get around this?
I'm seeing a curious thing in my vmkernel.log files. It doesn't appear to be causing me any problems besides taking up log space and potentially making other messages harder to spot amongst the noise, but just want to be sure that it isn't a precursor to another issue.
On one of my hosts, I'm seeing frequent log messages every minute or so (appears to be 66 seconds give or take, with an occasional skip) with SIOControlFlag1 flipflopping back and forth between a value and zero. Eventually it will stop on that host, but at the same time will start doing the same on a different host, yet no VMs appear to have migrated between them so don't think the messages are tied to a particular VM. In all cases, the value is the process ID of /sbin/sdrsInjector. None of my datastores have Storage IO Control enabled.
e.g.:
2016-03-01T11:12:05.649Z cpu0:34055)Config: 346: "SIOControlFlag1" = 0, Old Value: 34055, (Status: 0x0)
2016-03-01T11:13:11.522Z cpu0:34055)Config: 346: "SIOControlFlag1" = 34055, Old Value: 0, (Status: 0x0)
2016-03-01T11:14:17.742Z cpu8:34055)Config: 346: "SIOControlFlag1" = 0, Old Value: 34055, (Status: 0x0)
2016-03-01T11:15:23.595Z cpu2:34055)Config: 346: "SIOControlFlag1" = 34055, Old Value: 0, (Status: 0x0)
2016-03-01T11:16:29.796Z cpu6:34055)Config: 346: "SIOControlFlag1" = 0, Old Value: 34055, (Status: 0x0)
2016-03-01T11:17:35.643Z cpu10:34055)Config: 346: "SIOControlFlag1" = 34055, Old Value: 0, (Status: 0x0)
2016-03-01T11:18:41.838Z cpu4:34055)Config: 346: "SIOControlFlag1" = 0, Old Value: 34055, (Status: 0x0)
2016-03-01T11:19:47.696Z cpu10:34055)Config: 346: "SIOControlFlag1" = 34055, Old Value: 0, (Status: 0x0)
2016-03-01T11:20:53.878Z cpu8:34055)Config: 346: "SIOControlFlag1" = 0, Old Value: 34055, (Status: 0x0)
2016-03-01T11:21:59.748Z cpu5:34055)Config: 346: "SIOControlFlag1" = 34055, Old Value: 0, (Status: 0x0)
Anyone seen this before and can explain what's causing this, or know whether it indicates an issue or if it's normal behaviour?
Running VMWare 5.5 I have set up one ESX server. I am trying to get this ESX to connect to a iSCSI SAN. I've created a VMkernal port as a standard switch with one physical adaptor.
I go to the properties of the iSCSI adaptor. Go to the Network Configuration tab and select the port group. Enter the IP address of the SAN and then do a rescan. Nothing happens.
I go back in to the properties of the iSCSI adaptor. Remove the port group from the Network Configuration tab so it's empty. Do a rescan and the SAN appears fine with all the devices presented.
Anyone have any ideas what is going on? All the connections are pinging fine between them. The SAN can ping the ESX server, the server can ping the SAN, the VMkernal port is pinging. I'm at a loss.
When we allocate disks in VMware, we have to specify thin provisioned, thick provisioned eager zero or thick provisioned lazy zero, but what is the difference?
Hi,
I have installed windows 10 on esx5.5 with H/w version 10.No sound output device is installed.
Device manager i could not see sound,video and game controller.
How to resolve issue.
regards
Maniee.
Thick provisioning lazy zeroed, Thick Provision Eager Zeroed and Thin Provision
Although I understood the difference I did not understand when to use them
On what occasions do you use one rather than the other?
For the upgrade to VSphere 5 of our existing HP Prolient servers we wanted to use newer Supermicro Units but stay with the Hp Smart Array P410i controllers and disks we had before. For this task we could only use the standard VSphere 5 installation ISO and not the HP version of it. As a result there was not health status from the P410i controller any more which is not acceptable for a production server.
Because the Smart Array controllers were also sold separatly we could not imagine that there might be a problem to install CIM providers for this controller, but this was wrong. The CIM providres are only available as part of the "HP ESXi Offline Bundle for VMware ESXi 5.0" which contains also other HP specific drivers (eg. Ilo drivers) which may be problematic on non HP hardware (PSOD). Because of this HP blocks the installation with the hint "BIOS vendor HP ist required but host BIOS vendor is....".
In the ESXi 4.x Version this was not that problem because you only have to edit the vmware.xml file inside the metadata.zip archiv (delete the unused vib sections and the hwPlatform lines) but with ESXi 5 we have a new format for the offline bundles and VIB files. The VIB files are now complete installers based on Debian .deb packages only renamed to .vib. Because of this we can extract the hp offilne bundle zip archiv and move the hp-smx-provider-500.02.10.13.44-434156.vib out of it. This is the Smart Array provider and the only file we need.
This file can be extracted with 7Zip, which recognizes it as a Debian Archiv (deb). Inside this archiv is a descriptor.xml file which has to be modified to avoid the "BIOS vendor..." error. The following lines have to be deleted:
<hwplatform vendor="HP"/>
<hwplatform vendor="Hewlett-Packard Company"/>
<hwplatform vendor="Hewlett-Packard"/>
<hwplatform vendor="hp"/>
After that we have to pack the .vib file again. This can be done on a Linux or Mac OX (with Toolbox) System. Copy the 3 files from the .vib archiv to a folder inside the Linux disk (eg. tmp) for example with a tool like WinSCP. On the Linux console (Putty) walk to the folder with the 3 files and type in the folling command:
ar -r smx.deb descriptor.xml sig.pkcs7 hp-smx-provider
it is very important to use this exact order of the files ! Copy back and rename the smx.deb file to hp-smx-provider-500.02.10.13.44-434156.vib. Afterwards copy the file to the ESXi Server and install it with esxcli from the SSH console:
esxcli software vib install -f -v /vmfs/volumes/4ee96bcd-e80a45de-88f0-00259061b367/smx/hp-smx-provider-500.02.10.13.44-434156.vib
Reboot and you are done !
I have an existing Cluster of ESXi 5.5 Hosts (build 2068190), running on Cisco UCS blades running Intel Xeon E5-2630 v3 (codename Haswell).
I have purchased additional Cisco UCS blades and they are running on Intel Xeon E5-2630 v4 (codename Broadwell).
Do I need to enable EVC on my Cluster ?
Under the “enable EVC for Intel Hosts” I see the following options:
Intel “Merom” generation
Intel “Penryn” generation
Intel “Nehalem” generation
Intel “Westmere” generation
Intel “Sandy Bridge” generation
I don’t see “Ivy Bridge” nor “Haswell” …
What should I do ?
Regards
Kobi
Hello,
I am using ESXi 5.1 and i created a new windows server 2012r2 with the vmxnet3 nic. I tried to ping to localhost address (127.0.0.1) with the psping utility and i get results with high response times like 0.6-1.3ms. I do the same test in a VM in my Hyper-v host and the response times are 0.2-0.3ms.
Also, in esxi host there is latecy(1-1.2ms) and with the communication between two VMs. I check the esxtop but i didn't found any problem such as high ready times etc. My ESXi host is an hp bl680g7 with 160gb ram and 2x10core CPU. For hyper-v host i also have the same hardware setup.
I tried to change the vmware tools versions(to get new vmxnic drivers) and to update to esxi 6.0u2 but the results are the same. Why is there such a big difference between esxi host and hyper-v host? Are there any changes that can i do in order to reduce the latency? I already tried to enable the rss feature and change the nic to e1000/e1000e.
ps. I know that the differences are small but it makes difference in communication eg between application server and database server in the same host. (for low latency applications).
Imagine an ESXi 5.5 host member of a vSphete infrastructure.
The ESXi host is connected to 2 different datastores, let's say Datastore1 and Datastore2.
On Datastore1 a VM botts from an .iso image stored in folder ISO in Datastore1.
I need to move the VM to Datastore2 and to move the .iso image as well.
On Datastore2 I have an ISO folder with a copy of the .iso image.
Is there any way to move the VM from Datastore1 to Datastore2 and to make it use the .iso image in Datastore2 without powering it off?
Regards
marius
Hi All,
Can any body please suggest me for the latest patch (build) for vSphere 5.5, in the web its showing 5230635 ( https://esxi-patches.v-front.de/ESXi-5.5.0.html )? Please provide me the release notes for the same.
Thanks in Advance,
Suresh.
Hello,
I am investigating why the IO performance of our VM's is poor in comparison to our physical servers connected to the same storage (Dell Compellent SAN).
Here are some figures:
| host | I/O's | MB/s | IOPS | AvgLat |
| physical | 1869919 | 486,96 | 62330,25 | 0,016 |
| VM | 83851 | 21,84 | 2795,03 | 0,354 |
| physical | 1990602 | 518,38 | 66353,02 | 0,015 |
| VM | 105242 | 27,41 | 3508,06 | 0,282 |
The ESX and physical servers connect to different LUN's on the same storage system (Dell Compellent).
What could typically explain such huge differences in IO performance between physical servers and VM's ?
thnx
Johan
Hi everybody.
I need your help.
I had a situation, my array disk go broken down and my virtual machines go down.
Later the discs go up and vmware show me this message
An error was received from the ESX host while powering on VM MXMXO-I-DB4 - orig.
Failed to create swap file '/vmfs/volumes/53bf8e38-3892878b-be89-c81f66f3b1e4/MXMXO-I-DB4/vmx-MXMXO-I-DB4-542573655-1.vswp' : Not found
Could not start VMX: msg.vmk.status.VMK_NOT_FOUND
What can I do to recovery the disk information?