No coredump target has been configured

Written by employee #33. Posted in just going through the motions

No coredump target has been configured. Host dumps cannot be saved (ESXi 5.5)

Stupid little me - removed a storage device on which the coredump target partition was defined. Therefore: "No coredump target has been configured. Host coredump cannot be saved". No idea what to do with such a dump, but I do not like issues with my ESXi hosts, so I set out to fix it. The specific problem I was facing, is not a missing definition of the diagnostics coredump target, but that my target was pointing at a missing storage device.

Install vCenter 5.0 plus update manager trial on Windows 2008 R2

Written by employee #33. Posted in just going through the motions

For the server part you only need .NET framework 3.5. Make sure it is installed and patched.

Domain it not mandatory. i.e. you can run this vCenter installation in a workgroup if you like. For a home lab setup, a single disk should be fine, but as we need to install MS SQL, a separate disk for the SQL server is perhaps a good idea.

For this run i will install the database separately, and when the db is up and running, i will install vCenter 5.0. I shouldn't be necessary - but for some reason, the default vCenter installation seems to do a fairly poor job with the SQL setup. Or at least I don’t understand the setup and consequently Update Manager fails.

ERROR: failed to locate and extract VM_ID

Written by employee #33. Posted in just going through the motions

ghettoVCB is a little sensitive about vm names and editors. Special danish caracteres is absolutely a no-go in ghettoVCB - but you wouldn't do that anyway. Spaces and brackets is also an issue. Basically you should be using basic all-americans 8 characters names to be on the safe side. But if you do keep getting the "ERROR: failed to locate and extract VM_ID for" it is not necessary your names which is the problem. It could be a issue with the difference between linux and windows text editors instead. I’m not absolutely sure what the difference actually is, but the problem arise with line breaks. If you can do the following, it’s not a problem with the name, but a problem with your editor and you will need the dreaded vi editor. VMware ESXi includes the open source terminal-based editors nano and vi.

Upgrading ESXi 5.0 to 5.1 using ESXCLI

Written by employee #33. Posted in just going through the motions

Shut down all running instances and put your host in maintenance mode. Your host must have SSH enabled.

1) Download the upgrade from VMWare and copy to ESXi host
2) Get the name or code for this update
3) Perform the update

1) At this time, the most recent version is If updated, you should be looking for "Download VMware ESXi 5.1 Installable" That is something like Home -> All Downloads -> VMware vSphere -> VMware ESXi 5.1 Installable. It's not all that easy to find. You need a login at VMware. When the file is downloaded, copy the file to somewhere on the host. Somewhere you can find.