It will be available in the traditional change of ESX 3.5 on a CD but VMware ordain also be shipping it via Hardware Manufacturers with servers as a radiate separate. Known as 3i. Leverages capacity planning capabilities to sight physical servers analyze their performance and initiate the conversion of these physical systems into virtual machines and intelligently places them on the most appropriate VMware ESX Server or VMware Server hosts

So our CTO has some questions that I cannot find answers for regarding HA they are kind of conceal but valid none the less so here we go: 1. How does HA determine the primary agent in the cluster? Does ESX cause this by which host is more powerful (cpu ram)? Is it the first entertain of the assemble? Does this ever change or will the primary agent always be the primary agent? 2. What would happen in this occurance? If you undergo two hosts in a cluster using HA. One ESX host (ESX1) gets a memory failure but it does not act drink the host do all VM's on this ESX entertain (ESX1) migrate to the other host (ESX2) (hypothetically there are enough resources to use). Then the other ESX host (ESX2(with all of the VMs now on it)) has a hardware failure but not enough to completely act down the entertain. So both ESX hosts undergo some kinda of minor hardware issue on them do the VM's contantly turn break between hosts? Or does the one ESX entertain act itself out of the cluster at that point and HA would then be unavailable so all the VM's would be stuck on ESX2? 3. Does ESX have a built in parameters of which it determines when to failover VMs to a new entertain (not DRS) ? Does ESX rates hardware failures at different levels? Like is a memory error rated higher than a CPU error etc.? I have searched the forum looked through the book etc. CTO would like answers he pays my salary.... you know how it is! HA functions on a heartbeat function so any loss of that heartbeat will initiate it. Typically this is the loss of communicate communication on the function console which severs the heartbeat and isolates the host server. So things like memory errors or cpu errors that do not take the whole host drink will not initiate HA only a catastophic failure that causes the host to come down or suffer network connectivity on the SC ordain trigger it. The below docs go into dilate on HA... Automating High Availability (HA) Services with Vmware HA - Effective DRS and HA in Production - Choosing the HA host destination - Vmware HA with 2 ESX hosts - Knocking Out Downtime with Two Punches: VMotion & VMware HA - A Practical command to HA - Das isolationaddress - HA restart request of VM's with the same priority - Setting Failure and Isolation Detection Timeout and Multiple Isolation Response Addresses - HA Technical Best Practices - 3. Does ESX undergo a built in parameters of which it determines when to failover VMs to a new entertain (not DRS) ? Does ESX rates hardware failures at different levels? Like is a memory error rated higher than a CPU error etc.? In reality this is not going happen. Memory errors are not passive events that just show up and the system bypasses them when you undergo memory errors you are gonig to undergo a multitude of issues desire host crashes. VM crashes extensive data corruption (typicalyl immediately leading ot entertain crashes). Disk errors can be more benign and manifest themselves over a longer period before causing issues but bad memory almost always causes havoc on a system which is why the 72 hour burn-in is so important. If you undergo a CPU error your whole entertain is typically going to crash as ESX will not command a physical CPU going away even if the hardware is designed to let oyu hotswap the CPU's (ie some sun boxes ordain do that).

For the most move the smaller foot print talk has been around security. I think the smaller pay print could bring about to a couple of new and interesting uses of ESX 3i in the datacenter. One possibility could be to boot ESX 3i over NFS. Linux has been doing this for years and a be of shops have found it to be very useful (yes. I am aware that the vmkernel is not based on Linux). Although a small foot create is not required to run an OS over NFS it certainly does help. Another scenario could be to PXE boot and run ESX 3i in a RAM plough. This is much more feasible with the smaller foot print. Of cover with a RAM plough there is a possible air with persistence (this could be beat with a relatively simple configuration change/update mechanism). You may be wondering why in the world I would want to run ESX in a RAM plough or boot it over NFS. It is actually quite simple; abstraction. Granted. VMware can provide ESX abstraction when booting from SAN (with either FC or with iSCSI HBAs) but not currently with NFS (I won't go into the NFS vs. FC/iSCSI debate in this article). Another benefit is that both of these methods also would give more options to run ESX in disk-less nodes. If you are a regular reader of my blog then it should be no affect that I would like to see VMware give the ability to boot ESX over NFS. In both of these scenarios there is the issue of providing a unique configuration to each new ESX instance. In fact you could alter this same argument for ESX 3i instances booted from radiate devices in environments which be to be very dynamic and flexible. This situation could be an opportunity to expand VirtualCenter's role in the datacenter. I do think that eventually hypervisors ordain become the BIOS of the datacenter (I evaluate we are a year or two away from this being 'the standard' for new servers). Unfortunately. I would be very surprised to see VMware supporting ESX either over NFS or in a RAM plough as they seem to be pushing solely towards a firmware call approach. I'm a bit curious if any readers out there would also believe/see benefits in running ESX 3i either over NFS or in a RAM disk (assuming the issues mentioned could be easily resolved)?As always all comments and feedback are welcome. I think booting ESX off the communicate is a wonderful way to alter provisioning new servers easier and at the samtime increase consistency and exceed hold back change management. The problem is how do you maintain the uniqueness calculate for each image? It would be nice if ESX would support a facility sort of like a sysprep wouldn't it? I wish they do one day. Keep up the good bring home the bacon. In the meantime. I'm checking out vPloyment to back up automate and control esx installations. Jeremiah Cookcookjeremiah blogspot com

You are probably already familiar with what VMware ESXServer is how it is revolutionary and how virtualization is changingserver infrastructure forever. Perhaps you are already an ESX Serveruser perhaps not. Either way the latest version of ESX Server. 3i(currently in Beta) could go even farther than ESX Server 3 inchanging the approach of your server infrastructure. Let me show you how... In our previous article. "" we compared the various products in VMware's product line. For example the difference between VMware Server. Workstation and Server ESX. In this article we will focus specifically on the VMware ESX product lie and the VMware virtualization suite called VMware Infrastructure. With a variety of VMware Infrastructure suites and ESX Server product options it is difficult to experience which is alter for you. Let's find out... AsVMware ESX is loaded directly on hardware and is its own virtualizationoperating system there are a number of factors to consider whensecuring it. While due to its design architecture. ESX is inherentlysecure there are still a number of security factors to consider. Inthis article we will adjoin the vulnerability points of ESX and how youcan ensure that your ESX Servers are as secure as they can be. Insummary. VMware Workstation is in my opinion the most powerfuldesktop virtualization package available. The new features in version 6just "up the ante". While it isn't free desire VMware Server is,Workstation has enough features to justify the cost. The more I usevirtualization software the more I find uses for it. It has gotten tothe point where I don't experience what I did without it. Try out VMwareWorkstation and I think you will go to the same conclusion. Inour previous article. "What you need to know about VMware ConsolidatedBackup (VCB)" we provided an overview of how VCB can back up you. In thisarticle we will investigate the command line utilities provided with VCB. There is no GUI interface for VCB so these tools are THE tools that youget with VCB. Because of that if you are using VCB you must know howto use these CLI tools well. Let's act a look...

I noticed that esx 2.0 disk files undergo dsk extensions and on esx 2.5 they are vmdkCan dsk files (win 2000. 2003 linux) be copied directly to esx 2.5 and used as is or do they be renaming etc.? The cerebrate I ask is that a Win 2003 image that I copied over ordain blue screen on startup

Click Here to See The Real Me!

comments | Add comment | Report as Spam

i'm trying to lay vmware-tools in my slackware 12 installation on an ESX 2.5.3 server. I get this message:The directory of kernel header (version @@VMWARE@@ UTS_RELEASE) does not match your running kernel (version 2.6.21.5-smp). Even if the module were to compile successfully it would not load into the running lernel. What is the location of the directory of C header files that be your running kernel? [/usr/src/linux/include]I've found something about an conjoin (vmware-any-any) but canot bring home the bacon to make it install. Does someone get it ? It should undergo a kernel version instead of @@VMWARE@@ UTS_RELEASE and it may be that this is a variable substitution failure. On the other hand first analyse you undergo the kernel source package (or whatever gives you the kernel headers in slackware) installed somewhere (it's looking in /usr/src/linux/consider so change this if it's installed it somewhere different) If it can find the right headers it should build against them I had a similar problem with ESX 3.0.2 and SlackWare 11 (I still don't have SlackWare 12 working but that's a displace gripe.)If you do a uname -r you should see something that matches the directory for include files in /lib/modules. If you don't there are two workarounds I've tried:1 alter a symlink with the alter label to the directory you've got - this didn't work so come up for me2 compile the kernel with -smp appended to the end of the kernel's name arrange - this worked but I'm not completely sure I didn't need to do both. (I'll be testing tomorrow. I wish.)-dP After trying all of the suggestions in this and other threads ultimately. I had to edit vmware-install pl. Everywhere <linux/version h> shows up replace it with <linux/utsrelease h>Not sure if this is a gcc or version h issue but version h no longer has the UTS version listed in it. On my VMware 3 x box this script had been changed so that this was not an air any more so I believe this only applies to 2.5 x installsThis worked for both Fedora C5 and RHEL5.