new1234.jpg

Archive

Posts Tagged ‘ESXi 4.1’

VMware: Insufficient video RAM. The maximum resolution of the virtual machine will be limited to 1672×1254

January 16th, 2011 9 comments

I created a new VM via the “New virtual machine" wizard at my ESXi 4.1 server, after configuring the correct network settings and added some disks I started the VM.. but received this warning:

Insufficient video RAM. The maximum resolution of the virtual machine will be limited to 1672×1254. To use the configured maximum resolution of 2560×1600, increase the amount of video RAM allocated to this virtual machine by setting svga.vramSize="16384000" in the virtual machine’s configuration file.

image

 

Solution:

– Edit the VM settings

– Select: Video card

– Select: “Auto-detect video settings”

– Power on your VM… and it’s working

 

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: ESXi 4.1 installation hangs on “multiextent loaded succesfully” HP DL380 G7

December 23rd, 2010 6 comments

Last week I build a rack for a customer with some brand new HP DL380 G7’s, pre-sales decided (happy me) to install ESXi 4.1.. after creating a RAID10 (2x 72GB) configuration on HP SmartArray 410i I started the installation.

After the installation my first boot, ESXi keeps hanging on “multiextent loaded successfully” .. rebooted once again.. no result, waited more then 20 minutes.. still no result.

VMpros

 

Watching some log files (ALT + F12) I saw some warnings/errors:

Could not detect setting of QErr for device naa.60a98000572d504c654a573236636b6c. Error Failure

ScsiDeviceIO: 4494: Could not detect settings of QErr for device naa.6005….

LinScsiLLD:

VMWARE SCSI Id: Could not get disk id for vmhba32:CO:TO:LO

 

Solution:

The current (out of the box) firmware for the  HP SmartArray 410i was 3.03 , upgrade to version 3.66 (latest).

But… to solve this issue you need to delete the current array configuration and create a new one. Run the ESXi 4.1 installation again and the problem is permanently solved.

I know.. before you plan to install a new server.. first install the latest firmware with the HP Firmware DVD (955 mb).. I thought.. I’ll do this later.. NOT!

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: VMware ESX 4.1, Patch Release ESX410-201010001

November 16th, 2010 No comments

VMware released the first patches for ESX en ESXi 4.1, more information:

ESX:

ESX410-201010401-SG Security                            -                            KB 1027013

ESX410-201010402-SG Security                            -                            KB 1027014

ESX410-201010404-SG Security                            -                            KB 1027016

ESX410-201010405-BG Critical                              -                            KB 1027017

ESX410-201010409-SG Security                            -                            KB 1027019

ESX410-201010410-SG Security                            -                            KB 1027020

ESX410-201010412-SG Security                            -                            KB 1027022

ESX410-201010413-SG Security                            -                            KB 1027023

ESX410-201010414-SG Security                            -                            KB 1027024

ESX410-201010415-BG Critical                              -                            KB 1027025

ESX410-201010419-SG Security                            -                            KB 1027026

 

ESXi:

 

ESXi410-201010401-SG Security                            -                            KB 1027021

ESXi410-201010402-BG Critical                              -                            KB 1027028

 

Download patches: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , , , ,

VMware: ESX and ESXi 4.1 Comparison

July 15th, 2010 1 comment

Capability

VMware ESX

VMware ESXi

Service Console

Service Console is a standard Linux environment through which a user has privileged access to the VMware ESX kernel. This Linux-based privileged access allows you to manage your environment by installing agents and drivers and executing scripts and other Linux-environment code.

VMware ESXi is designed to make the server a computing appliance. Accordingly, VMware ESXi behaves more like firmware than traditional software. VMware has created APIs through which monitoring and management tasks – traditionally done through Service Console agents – can be performed. VMware has provided remote scripting environments such as vCLI and PowerCLI to allow the remote execution of scripts and commands.

Tech Support Mode (TSM) provides a command-line interface that can be used by the administrator to troubleshoot and correct abnormal conditions on VMware ESXi hosts.

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , , ,

VMware: “Failed to read the upgrade package metadata.xml” upgrading to ESXi 4.1

July 15th, 2010 24 comments

I was upgrading my ESXi 4.0 Update 2 host to ESXi 4.1 with “VMware vSphere Host Update Utility”, I downloaded the “ESXi 4.1 (upgrade ZIP from ESXi 4.0)” file and selected this package to upgrade the host. After validating the upgrade package I received this error:

Failed to read the upgrade package metadata: Could not find file metadata.xml

image

I’ve checked the MD5 checksum.. it was correct.. I downloaded again the upgrade package from the VMware site.. still this warning..

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn