Even if its not on the HCL, it should still work. it essentially means that HP didn't pay to make sure that the hardware is certified for this release since its end of life However it won't b...
See more...
Even if its not on the HCL, it should still work. it essentially means that HP didn't pay to make sure that the hardware is certified for this release since its end of life However it won't be supported by vmware in case you need assistance. So if it's production, I wouldn't update.
the customized versions would have vibs specifically for your hardware which the vmware iso might not. I would normally use the vendor iso and run the updates as needed.
like dGeorgey said re installation of the esxi hypervisor is the best method. I havent tested the following but if you NEED the password try this http://www.vdsyn.com/resetting-the-root-pass...
See more...
like dGeorgey said re installation of the esxi hypervisor is the best method. I havent tested the following but if you NEED the password try this http://www.vdsyn.com/resetting-the-root-password-for-esxi-5-x/
matt's suggesstion is still the best since that unit has the highest density processing (8core 1Pcpu) vs the others and its also has the highest ram capacity (768gb m4 vs 288?GB m3 )
DarkPassenger wrote: Hi guys, I'd like to write a list of things you have to keep in mind and potential problems that can occure when upgrading to 5.1. Are there reasons for you not to upg...
See more...
DarkPassenger wrote: Hi guys, I'd like to write a list of things you have to keep in mind and potential problems that can occure when upgrading to 5.1. Are there reasons for you not to upgrade right now and stick to 5.0 for the moment? Even a new installation on 5.0? I came up with these: - a stricter compatibility matrix regarding supported servers. - the need of using SSO even in small environments which don't leverage from it. - some features only available through the web client?! (But I guess we all have to get used to the web client anyway ) - new releases always comes with bugs (saw 3 PSODs in different 5.1 environments yet) Hope you can help me with some other arguments or maybe you disagree with mine. Appreciate it! I think the major issue many people experiance is the complexity and additional requiremetns of SSO. as far as using the webclient, that is only for the new features of 5.1, anything from 5.0 is still in the vi client.
you turn off a virtual machine before migrating to a different host or storage its use is in cases where you are moving to different arcitectures, say intel host to amd or moving the vms to diff...
See more...
you turn off a virtual machine before migrating to a different host or storage its use is in cases where you are moving to different arcitectures, say intel host to amd or moving the vms to different datacenters http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.vcenterhost.doc_50/GUID-326DEC3C-3EFC-4DA0-B1E9-0B2D4698CBCC.html
Zanelli wrote: So ... Re explain ... The database, the old vCenter (on which there were 3 Hosts), it is damaged and could not be reset because my predecessor never did backup. So I created ...
See more...
Zanelli wrote: So ... Re explain ... The database, the old vCenter (on which there were 3 Hosts), it is damaged and could not be reset because my predecessor never did backup. So I created a new vCenter with a new database using the same licenses the old vCenter. Now, when I try to add the Hosts, tells me that the licenses are not available because they were all used. So, I have no new licenses available that I can use ... I'm reusing the licenses that I had before. My question is: is it possible to remove from the old vCenter the hosts directly from them? Thanks yes you could remove the hosts from the old vcenter and add them into your new one. right click remove the vms will keep running. when the host is added to your new vcenter the vms will be brought along
sharoncook wrote: This would take the vm from one host to another, I would prefer to copy it and leave 1 copy on the original and have a copy on the new host. No, vmroyales suggestion is wh...
See more...
sharoncook wrote: This would take the vm from one host to another, I would prefer to copy it and leave 1 copy on the original and have a copy on the new host. No, vmroyales suggestion is what you want. you can export as ovf, and the orignal is left at the source. exporting doesnt move anything, only creates copies.
jrocket wrote: Can I ask what the use case is for limiting the I/O? probably the vm is generating too many iops or saturating his NFS causing the other vms to have a high latency
Anupreet01 wrote: What is the best practice to increase the datastore to 4.5 TB? Will expanding the datastore impact currently running VMs? datasstore and vms will be unaffected you can in...
See more...
Anupreet01 wrote: What is the best practice to increase the datastore to 4.5 TB? Will expanding the datastore impact currently running VMs? datasstore and vms will be unaffected you can increase the lun size on the storage side then increase it in the vi client here is a POC I did if you wanted to verify http://sparrowangelstechnology.blogspot.com/2012/07/growing-and-expanding-vmfs.html