Quantcast
Channel: VMware Communities: Message List - VMware ESXi 5
Viewing all 61617 articles
Browse latest View live

Re: VM freezes as soon as datastore goes out of free disk space.

$
0
0

check if the snapshot is active  if yes the vm need space to create snapshot file

try to merge snapshot to free the datastore


Re: Best way to have HA and Fault Tolerence Non-Shared Storage

$
0
0

you nedd to install vcenter

and you need to add the VSA component to share the local datastore and will provide to you framework HA and FT via NFS technology

 

regards

Re: New ESXi 5.5 Install threw PSOD, Raid controller driver?

$
0
0

Hi ,

Indeed it appears that you have discovered a potential memory leak that is starving the vmkernel or otherwise causing mayhem.  Please ssh into the host and capture a support bundle asap while it's still fresh.  Do this by typing vm-support.  The logs will be saved in /var/tmp.

 

You should also grab the vmkernel zdump by performing an esxcfg-dumppart -L against the zdump filename.  This creates a file that is very useful for support in debugging the diagnostic screen.  Remember that the zdump you are targeting is probably in /var/core, but the file it outputs will be saved in your current directory.  So I like to cd to the /var/tmp directory before running this.  That way all my logs are in one place.

 

Optional:  This is contained in the vm-support bundle, but may be handy for quick reference.  Run an 'esxcli software vib list > /var/tmp/my-vibs.txt' so you have a list of all software installed on the host.

 

Gather all that using WinSCP (in SCP mode, not SFTP) and share with HP and VMware Support (also include the screenshot for good measure).  HP will be interested to know which SPP you are running (i.e. is firmware the latest, etc.).  Also check the iLO logs to see if there were any disk failures or raid rebuilds that were aggravating the issue.

 

Let us know if you need anything.

Re: Unable to connect host to vCenter

Is it possible to add an annotation to a datastore object instead of a VM

$
0
0

I need a script to add an annotation (custom field) to a specific datastore.

 

Example:

 

Datastore | Annotation

 

Datastore1 = with the Annotation value of A

Datastore2 = with the Custom Field value of B

Re: VM freezes as soon as datastore goes out of free disk space.

$
0
0

Hi ,

This is an amazing new feature that I really like.  Trust me it's good for you.  Historically, VMs that lived on datastores that ran out of space would simply BSoD in the case of Windows, and for Linux they would either kernel panic or the filesystem  would go read only.  This only happened to the VMs that tried to generate I/O (i.e. write to disk).  Previously, the time it took for them to crash was purely dependent on their tolerance for lack of Disk I/O (configurable in the Guest Operating System).  The problem is that the old method was very inconsistent and determining which VMs were actually affected was tough as not all VMs would crash hard.

 

This new enhancement is called "Thin Provision Stun" which is on by default when using VAAI with thin provisioned datastores (at least on NetApp and EMC gear).  It protects you from data corruption by suspending the VM.  Once you have cleared the free space or expanded the datastore, you simply answer the Guest Question with "Retry".  I typically set my datastores to autogrow to protect me from these situations, but sometimes it happens when a volume was not set properly to autogrow.

 

After the space has been cleared, to answer the question and get the VMs powered on quickly, PowerCLI does a great job.
Get-Datastore MyDatastore | Get-VM | Get-VMQuestion | Set-VMQuestion -Option "Retry"

 

EDIT:  Added the name of the VAAI primitive ("Thin Provision Stun") to encourage additional research

Re: Is it possible to add an annotation to a datastore object instead of a VM

PCNS 3.01 for ESXi

$
0
0

I have been fighting with this for a while and wanted to ask if anyone else is using this, and if so how did you get this to work.  I got PCNS installed on the vma, and setup and it talks to the UPS just fine, but it will not shut down the host.  All that happens is the PCNS stops working and I have to reboot the vma.  If I run the shutdown script manually that the PCNS is suppose to run, it works perfect.  I am running ESXi 5.1, with a 5.1 vma


Re: vSphere Web client Reliability?

$
0
0

I've grown to prefer the web client over the moldy oldy client but too have been experiencing more and more flash crashes. Obviously this is not all on VMware as anyone knows supporting the growing list of browsers is a nearly insane accomplishment. I've found that Firefox seems to work the best, but I don't know what version of flash works best or even what version of windoze. MacOS works for some things but not all (like vm consoles). The current Windoze 2008r2 svr I'm running the client on has two flash components, I wonder if they are stepping on each other?

 

 

I have noticed in my case if I'm in the midst of doing configuration changes on a host per se, when I move to another window outside the vcenter client to say capture some text string, the vcenter client will often crash when coming back to it. This can make you spit explicative's wilst having gone through a lot of config work.

 

Re: ESXi 5.5 prevents HDD spin down

$
0
0

That really looks like the final solution. I have to thank you so much!

 

Unfortunately I cannot testit at the moment, because I'm nothome during thesemester break. I could do it via Teamviewer or RDP, but then i can't hear whether the disks are spun down...


Enabling automatic spin down under Linux is no problem for me, i can do it with Openmediavault's simple web interface and manually with "hdparm -S time /dev/sdb" or "spindown_time = time" in hdparm.conf.


When I'm homeagain, I'llmarkthis problemas solved.

Re: ESXi 5.5 and LogMeIn - Host hang problem.

$
0
0

OK, I found out that it was the bug (still not fixed) of E1000 network card and Windows Server 2012 running 2 RSS queues.

Best practice to use official VMWare ESXi images or HP images for Proliant G8?

$
0
0

I'm fairly new to VMware, having previous worked only with Hyper-V, so I have a few relatively basic questions.  The VAR that installed the VMware infrastructure that I currently manage used a standard VMware image for a couple of brand new Proliant G8s.  The problem with that is it doesn't have any of the HP management agents which I'm used to utilizing.  I'm currently running vSphere 5.1 and I'm in the process of upgrading to 5.5, and I'm now to the point where I need to upgrade the hosts.  Should I use HP's image or VMware's?  Also, when I upgrade the host does vCenter house all configuration information and apply it back to the host when I upgrade using the 5.5 ISO (examples:  HA settings, FC adapter settings, LUN mappings, etc.)?  From everything I read it seems as simple as uploading the ISO to the Update Manager and upgrading using the update manager, but I want to make sure I'm not missing a crucial step somewhere.

 

Thanks for any help and suggestions.

Re: Best practice to use official VMWare ESXi images or HP images for Proliant G8?

$
0
0

Welcome to the Community - At the core of the HP build is the standard VMware Image - the only difference is the HP build will have the appropriate drivers for the HP hardware - vCenter houses the information about the vCenter environment - host configurations are store with the host but you are correct loading the ISO image in update manage will update the hosts - 

Re: Meet "Error on determining the SDK Service build" on workbench3 .0

Re: Best practice to use official VMWare ESXi images or HP images for Proliant G8?

$
0
0

Hi daccu,

For host standardization across rebuilds/upgrades Host Profiles is the way to go if you are licensed for it.  These are set on a per cluster basis typically.  After upgrading the first host in the cluster, create a new profile from that reference host.


Regarding the topic of "VMware ISO" vs the "HP ISO", it is possible to use the VMware ISO (not ideal) and then add the HP vibsdepot to VUM to fill in what's missing from the standard VMware image.  Here's an example of adding the depot to VUM.  In general though, you should always use the vendor provided ISO (i.e HP, Dell, etc.) unless there is a specific reason not to (i.e. known issue for which you want to selectively install only certain components... rare or never).  You should add the HP depot anyway just so you can scan for changes and updates in the future.


BTW, most techs prefer to cook a custom ISO for the install.  For this task, VMware PowerCLI ImageBuilder works wonders.  PowerCLI is backwards compatible so download the 5.5 version to manage your existing 5.1 and your new 5.5 hosts.  Also make sure vCenter is upgraded first before upgrading the ESXi hosts (generally vCenter must be upgraded first for Major version changes).  When in doubt check the interop matrix.


Check out the following blog for some details on how to get ImageBuilder up and running.

http://wahlnetwork.com/2012/10/22/utilizing-vsphere-esxi-image-builder-with-partner-software-depots/

 

Tip:  I know this all probably seems pretty intimidating but just take it one host at a time.  Place the host in maintenance mode so there are no VMs on it.  Then practice updating it.  If there's any doubt, and you are under a time crunch, there is nothing wrong with upgrading the host using your HP ISO directly via the iLO instead of using VUM.


Re: ESXi 5.1 Update 1 crashing randomly with purple screen #PF Exception 14

$
0
0

Hi guys, we have received some information from VMware this morning just to update everyone.

 

The cause of our crash is from Rate Limiting the Port Groups. It has been identified in our crash logs and with running ESXi debug version.

 

The fix will be included in the following updates:

 

ESXi 5.1 Patch 04 - Expected to be available by end of April 2014.

ESXi 5.5 Patch 02 - Expected to be available by end of June 2014.


In the meantime the work around is to disable rate limiting on the port-groups

Re: ESXi 5.1 Update 1 crashing randomly with purple screen #PF Exception 14

Clone issue ..

$
0
0

Hi Everybody ,

 

Today morning I created new Esxi 5.0 server for install 4 Guest OS's.

 

On another Esxi server , we have a Installed Guest Machine so I am creating a clone of that system.

 

That VM has a two Virtual HDD , (HDD1 having OS and HDD2 having Data.)

 

Now ,

 

Clone is going to create successfully , after completed the cloning it's showing two drives "C drive" & "D Drive" perfectly.....

 

But after reboot this VM , "D Drive "is invisible and HDD2 is showing as dynamic hard disk in Disk management.

 

How I can resolve this issue...

 

Thanks ,

Vaibhav

Re: Clone issue ..

$
0
0

Both HDDs were created on the same datastore of the source ESXi?

Does your ESXi to which you have cloned your VM, have enough storage to hold both HDDs .?

 

 

~dGeorgey

Re: Clone issue ..

$
0
0

Yes ..

 

On same Datastore and having enough space on datastore.

 

HDD is only 40GB ...

Viewing all 61617 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>