monitor.virtual_exec = hardware
monitor_control.restrict_backdoor = true

Für alle die es bis hierhin ausgehalten haben habe ich nun noch meine .vmx Datei welche zu 100% funktioniert.

config.version = “8″
virtualHW.version = “7″
numvcpus = “2″
scsi0.present = “TRUE”
scsi0.virtualDev = “lsisas1068″
memsize = “1512″
scsi0:0.present = “TRUE”
scsi0:0.fileName = “pathtovmdk”
ide1:0.present = “TRUE”
ide1:0.autodetect = “TRUE”
ide1:0.deviceType = “cdrom-image”
floppy0.startConnected = “FALSE”
floppy0.autodetect = “TRUE”
ethernet0.present = “TRUE”
ethernet0.virtualDev = “e1000″
ethernet0.wakeOnPcktRcv = “FALSE”
sound.present = “TRUE”
sound.fileName = “-1″
sound.autodetect = “TRUE”
svga.autodetect = “TRUE”
mks.enable3d = “TRUE”
pciBridge0.present = “TRUE”
pciBridge4.present = “TRUE”
pciBridge4.virtualDev = “pcieRootPort”
pciBridge4.functions = “8″
pciBridge5.present = “TRUE”
pciBridge5.virtualDev = “pcieRootPort”
pciBridge5.functions = “8″
pciBridge6.present = “TRUE”
pciBridge6.virtualDev = “pcieRootPort”
pciBridge6.functions = “8″
pciBridge7.present = “TRUE”
pciBridge7.virtualDev = “pcieRootPort”
pciBridge7.functions = “8″
vmci0.present = “TRUE”
roamingVM.exitBehavior = “go”
displayName = “Other 64-bit”
guestOS = “other-64″
nvram = “Other 64-bit.nvram”
deploymentPlatform = “windows”
virtualHW.productCompatibility = “hosted”
easyInstall.removeFloppy = “FALSE”
unity.customColor = “|23000000″
tools.upgrade.policy = “useGlobal”
monitor.virtual_exec = hardware
monitor_control.restrict_backdoor = true

extendedConfigFile = “Other 64-bit.vmxf”

floppy0.fileName = “A:”

ide1:0.fileName = “pathtoiso”

ethernet0.addressType = “generated”

Der Fettmarkierte text ist das was man bei der VMX wenn man sie nach meinen Screenshots generiert ergänzen müsste.

• DirectX 9.0 Shader 2 3D experimenteler support
• Multi-Monitor support
• Virtual Printing
• Virtual Machine Library
• Integrated VMware Importer

Allen Macusern wünsche ich viel Spass beim testen.

• Vollen Support für Solaris und Mac OSX als Host
• Seamless window für Solaris und Linux Gastsysteme
• Support für virtuelle SATA Fesplatten
• PAE Memory support für Gastsysteme

Herunterladen kann man das ganze dann hier

New patches are available for ESX Server 3.5/3i.

Please follow the instructions on the appropriate patch download page.

VMware ESX Server 3.5 Patch Download Page

ESX350-200804401-BG (Critical): Prevent DHCP from resetting the IP address and netmask when trying to acquire or renew a lease. Change the default multipath policy for all HDS modular storage arrays such as AMS, SMS, WMS, 9500V to “fixed”.

ESX350-200804402-BG (Critical): Prevent the guest from stalling for a long time during snapshot operations. Prevent the ESX Server host from crashing during snapshot consolidation. Prevent the ESX Server host from rebooting while powering on a vSMP virtual machine on a Unisys ES7000/one with eight or fewer logical CPUs. Fix emulation of instructions that access I/O ports. Fix emulation of string instructions on 64-bit guest operating systems.

ESX350-200804403-BG (Critical): Prevent hostd from crashing due to incompatible entries in /etc/vmware/hostd/authorization.xml. Allow spaces in a password while creating and editing local ESX Server users through the VI Client. Set the executable bit for .vmx configuration files. Fix a vmware-vpxa crash caused by invalid UTF-8.

ESX350-200804404-BG (General): Allow Windows virtual machines to boot when DataDigest is enabled in software iSCSI.

ESX350-200804405-BG (General): Include a megaraid2 driver fix for UNISYS platforms.

ESX350-200804406-BG (General): Add support for the Intel PRO/1000 PF Quad Port Server Adapter.

ESX350-200804407-BG (Critical): Add support for the Broadcom HT-1100 SATA/IDE controller. Prevent path thrashing during an Invista all paths down condition.

VMware ESX Server 3i Patch Download Page

ESXe350-200804401-I-BG (Critical): Fix typographic errors in the message strings of storage controller battery status, which is displayed in the VI Client. Include fixes for issues addressed by the following 3.5 patch bundles: ESX350-200804401-BG, ESX350-200804405-BG, ESX350-200804405-BG, ESX350-200804403-BG, and ESX350-200804407-BG.

We expect the next patch release in May 2008

Nun kann man das folgende Script ausführen das ich bei Dell auf der Website gefunden habe ausführen:

#!/bin/sh
# scott_hanson@dell.com
# modified by markus.gehm
#
# Script to apply DUPs (Dell Update Packages) on ESX 3.x hosts
#
# WARNING : This script applys updates with no user interaction or
# WARNING : prompting. Make sure this is what you want done. See below
# WARNING : for the line to un-comment to make it work.
#

echo ‘Creating SUU Comparison report …. patience is a virtue’
/tmp/Dell/suu -c > /tmp/suu_comparison_report

# Pull out the .BIN file names from the report - dump everything else
for i in `grep -i ‘.bin’ < /tmp/suu_comparison_report | perl -pi -e ’s/.*\s(.*?.bin).*/$1/gi’`
do

echo ‘———————————————-’
echo ‘Applying package ‘$i

# Apply DUPs with -q option to update silently with no user prompts
# Un-comment out the line below when done testing to apply updates.
# As-is the script just list updates it **would** have installed.

# /tmp/Dell/repository/$i -q

done

echo ‘ ‘
echo ‘ ‘
echo ‘Updates applied’
echo ‘Now would be a good time to reboot the system.’
echo ‘This script brought to you by the Dell Enterprise TechCenter’
echo ‘Join us at www.delltechcenter.com’

Es zeigt an ob und wenn ja welche Firmware upgedated werden können.
Sollte man das Upgrade durchführen wollen muss man nur die # vor dem fett markierten Text entfernen.
Dann werden alle Firmwares installiert.

Update 1: Habe einen Workaround gefunden der mir in sofern weiterhilft das ich nun zumindest mal wieder arbeiten kann.
Man muss den INTERNEN USB Controller deaktivieren.
Dann funktioniert es dahingehend wieder das der Server beim reboot die neuen LUN’ s erkennt und man sie nutzen kann.
Allerdings führt ein manueller Rescan weiterhin zum PSOD.

Update 2: So nun erstmal eine praktikable Lösung auf die mich der Dell Support gestoßen hat.
Nachdem man den internen USB Controller im BIOS deaktiviert hat, muss man noch in der /etc/modules.conf alle USB einträge auskommentieren.
Danach noch ein Reboot und auch einem manuellen Rescan steht nichts mehr im Wege.

Hier erstmal der Link zum VMTN Thread

Bei mir war es allerdings nicht wie im Forum beschrieben:
/var/pegasus/vmware/install_queue/3_files/mofs/root/cimv2/roleauth-schema.mof
sondern:

/var/pegasus/vmware/install_queue/1_files/mofs/root/cimv2/roleauth-schema.mof
ansonsten war aber alles soweit korregt.
Daher hier nochmal als fullquote:

Edit the roleauth-schema compiler directive to include the VMware_Identity class definition using

nano /var/pegasus/vmware/install_queue/3_files/mofs/root/PG_Interop/roleauth-schema.mof

Add the bolded line above the pre-existing member directive.

#pragma include (”VMware_Identity.mof”)
#pragma include (”VMware_IdentityMemberOfCollection.mof”)

It also needs to be added in the standard cimv2 path.

nano /var/pegasus/vmware/install_queue/3_files/mofs/root/cimv2/roleauth-schema.mof

#pragma include (”VMware_Identity.mof”)
#pragma include (”VMware_IdentityMemberOfCollection.mof”)

Copy the missing file from the stardard cimv2 path to the shared path.

cp /var/pegasus/vmware/install_queue/3_files/mofs/root/cimv2/VMware_Identity.mof /var/pegasus/vmware/install_queue/3_files/mofs/root/PG_Interop/

Stop and start the service with these commands.

/etc/init.d/pegasus stop
/etc/init.d/pegasus start

Once the scripts completes the install_queues will be empty and the service will start much more quickly.

ESX 3.5 Update 1 und VirtualCenter 2.5 Update 1

Wichtig zu wissen ist man kann von ESX 3.0.1 und 3.0.2 nicht per Tarball updaten, dazu muss man von 3.0.x auf 3.5 und dann kann man erst 3.5 Update 1 patchen.