// zi0r.com

Sun, 06 Dec 2009 12:24:45

When attempting to install the Dell OMSA extensions on ESXi, I ended up with an error indicating that the SMBIOS values reported by the host didn’t match the metadata stored in the cross_oem-dell-openmanage-esxi_6.1-0000.zip file.

Encountered error NoMatchError:
The error data is:
Id -
Message – No bulletins for this platform could be found. Nothing to do.
Detailed reasons why no bulletins match: This Vib supports
hardware vendor ‘Dell’ but BIOS reports vendor as ‘Dell Inc.
’ This Vib supports hardware vendor ’Dell Computer Corporation’
but BIOS reports vendor as ‘Dell Inc. ’ This Vib
supports hardware vendor ’Dell Inc.’ but BIOS reports vendor as
’Dell Inc. ’
Errno – 13
Description – No matching bulletin or VIB was found in the metadata.

Apparently, esxupdate thinks the manufacturer is "Dell Inc. " instead of “Dell Inc.” Seems sort of silly.

1. unzip cross_oem-dell-openmanage-esxi_6.1-0000.zip
2. unzip metadata.zip
3. Edit platforms.xml and remove the hwPlatform lines, save the file and add/overwrite platforms.xml in metadata.zip
4. untar cross_oem-dell-openmanage-esxi_6.1-0000.vib (which is actually a debian dpkg)
5. Edit descriptor.xml and remove the hwPlatform lines
6. Recreate the vib (without the pkcs7 sig file and the newly edited descriptor.xml) with: ar -r cross_oem-dell-openmanage-esxi_6.1-0000.vib debian-binary control.tar.gz data.tar.gz short.rpm descriptor.xml
7. Recreate cross_oem-dell-openmanage-esxi_6.1-0000.zip, which should contain the .vib and metadata.zip.
8. Login to your host and run: esxupdate —nocache —nosigcheck —bundle cross_oem-dell-openmanage-esxi_6.1-0000.zip update

/tmp # esxupdate —nocache —nosigcheck —bundle cross_oem-dell-openmanage-esxi_6.1-0000.zip update
cross_oem-dell-openmanage-esxi_6.1-0000.zip ########################################################################################## [100%]

Unpacking cross_oem-dell-openmanage-esxi_6.1-0000.vib ########################################################################################## [100%]

Installing packages :cross_oem-dell-openmanage-esxi_6.1-0000 ########################################################################################## [100%]

Running [/usr/sbin/cim-install.sh]…
ok.
Running [/usr/sbin/vmkmod-install.sh]…
ok.
/tmp #

Wed, 25 Nov 2009 22:35:57

.tmux.conf file to make tmux behave a bit like screen.
Note: keybind to detach is ^A^D, unlike screen which is ^AD

#$Id: screen-keys.conf,v 1.2 2009/01/16 20:04:54 nicm Exp $
#
#This configuration file binds many of the common GNU screen key bindings to
#appropriate tmux key bindings. Note that for some key bindings there is no
#tmux analogue and also that this set omits binding some commands available in
#tmux but not in screen.

set-option -g status-bg blue
set-option -g status-fg cyan
set-option -g status-interval 0
set-option -g set-titles on
set-option -g status-right-length 0

###Unbind existing tmux key bindings (except 0-9).
unbind ‘"’
unbind ‘#’
unbind &
unbind ,
unbind -
unbind :
unbind =
unbind ?
unbind [
unbind ‘\’
unbind ]
unbind c
unbind d
unbind l
unbind n
unbind o
unbind p
unbind r
unbind s
unbind t
unbind w
unbind x

unbind Up
unbind Down
unbind M-Up
unbind M-Down
unbind C-Up
unbind C-Down

unbind C-b

###Set the prefix to ^A.
set -g prefix ^A

###Bind appropriate commands similar to screen.
#removebuf =

#clear C

#lockscreen ^X x
bind ^X lock-server
bind x lock-server

#reset Z

#colon :
bind : command-prompt

#log H

#screen ^C c
bind ^C new-window
bind c new-window

#copy ^[ [
bind ^[ copy-mode
bind [ copy-mode

#login L

#select ’
bind “’” select-prompt

#detach ^D d
bind ^D detach

#meta a
bind a send-prefix

#silence _

#digraph ^V

#monitor M

#split S

#displays *
bind * list-clients

#next ^@ ^N sp n
bind ^@ next-window
bind ^N next-window
bind " " next-window
bind n next-window

#suspend ^Z z

#dumptermcap .

#number N

#time ^T t

#fit F

#only Q

#title A
bind A command-prompt “rename-window %%”

#flow ^F f

#other ^A
bind ^A last-window

#vbell ^G

#focus ^I

#pow_break B

#version v
bind v server-info

#hardcopy h

#pow_detach D

#width W

#help ?
bind ? list-keys

#prev ^H ^P p ^?
bind ^H previous-window
bind ^P previous-window
bind p previous-window
#XXX bind ^? previous-window

#windows ^W w
bind ^W list-windows
bind w list-windows

#history { }

#quit \
bind \ kill-server

#wrap ^R r

#info i

#readbuf <

#writebuf >

#kill K k
bind K kill-window
bind k kill-window

#redisplay ^L l
bind ^L refresh-client
bind l refresh-client

#xoff ^S s

#lastmsg ^M m

#remove X

#xon ^Q q

#select -

#paste ] ^]
bind ] paste-buffer
bind ^] paste-buffer

#split -v |
bind | split-window

#:kB: focus up
bind Tab down-pane
bind BTab up-pane

#" windowlist -b
bind ‘"’ choose-window

Sun, 22 Nov 2009 18:50:01

Dell SC1420’s appear to limit CPUID information available to the OS and do not appear to present a BIOS option to the end user to enable/disable the ‘feature’

In order to get ESXi to install/boot, you need to do a couple of things:

1. When the ESXi bootloader appears, hit tab.
2. Find vmkboot.gz and append nocheckCPUIDLimit, before the -
3. Find vmkernel.gz and also append nocheckCPUIDLimit, before the -
4. Hit enter and the ESXi installation will continue.
5. After ESXi has been installed, it will reboot, you’ll then need to press shift-o to access advanced options, simply type in nocheckCPUIDLimit in order to get it to boot for the first time.
6. ESXi should boot for the first time, connect to it with vSphere and goto Configuration→Advanced settings.
7. Navigate to VMKernel→Boot and locate VMkernel.Boot.checkCPUIDLimit and untick the box.
8. Profit.