Virtual machine still sees ~ 200-300 MB less memory than... ?

Similar Questions

• VMs vCAC deleted using vSphere.  Virtual machines still appear in vCAC

  I deleted the virtual machines created in vCAC with vSphere, but they still appear in vCAC.

  How can I remove these vCAC VMs?

  This seems to be the correct procedure.  I ended up back to a previous on my machines management snapshot since it's a beta environment.

• Do not allow the virtual machine to power on if the host memory usage over 75%?

  Hi all

  I'm looking for a way to do not allow the power of virtual machines on if the clutser average memory usage is greater than 75%, or if its corresponding host memory usage is greater than 75%.

  Any idea.

  Thank you very much

  Hey Valot,.

  One way to achieve this is HA admission control that does not allow a virtual machine to be turned on if the availability constraints are not met

  http://www.VMware.com/PDF/vmware_ha_wp.PDF

  Also chwck on http://www.yellow-bricks.com

  Concerning

  one

• Windows 7 x 64 shows less memory than installed

  Hello

  I have a Dell Dimension 5150 with Windows 7 x 64 and 4 GB (2x2gb) RAM. But Windows 7 is said under properties I have a 2.5 GB of RAM. (He does NOT like in other posts 4 GB (2.5 GB usable)).  Where is used the rest?  I used the (3.5 GB) together with XP x 86.

  Thank you

  Markus

  Hi Markus,.

  This problem could occur due to these reasons.

  1. The devices that are installed in the computer and the memory reserved by these devices.
  2. The ability of the motherboard to manage memory.
  3. The version of the BIOS of the system and the parameters.
  4. The version of Windows 7 that is installed (for example, Windows 7 Starter Edition does support 2 GB of memory installed.)
  5. Other system settings.

  I suggest you to return the item and check if it helps.

  Usable memory may be less than the memory installed on Windows 7 computers
  

  Note: BIOS change / semiconductor (CMOS) to complementary metal oxide settings can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee
  that problems resulting from the configuration of the BIOS/CMOS settings can be solved. Changes to settings are at your own risk. Hope this information helps. Answer the post with an up-to-date issue report to help you further.

  Hope this information helps. Answer the post with an up-to-date issue report to help you further.

• Photos on ipad use less memory than on iphone

  Hello

  with the help of iPad 2 Air. Use of the photos 14.3 GB app memory. Same number of photos on the iphone and the same parameters but the pictures use 28.4 GB

  I checked the settings iCloud and photos on both devices and they are identical.

  No idea why this is happening?

  Thank you

  One reason might be that your iPhone has more space free storage to your iPad. (Assuming that the parameter storage to optimize is activated.) More storage, photos more will remain on your device at full resolution. In theoray at least.

• From the backup with less memory than the size of backups

  I recently had my phone stolen. Fortunately, enough that top has been saved. In order to save insurance money for other things, I am considering the reduction in the strength of 128 GB to 64 GB. The problem is that the backup from which I intend to restore my new phone is more than 64 GB. What will happen if I tried to download this backup on my phone? Whatever it would be eventually get lost?

  It will not restore if it contains more than held the replacement phone.

• WAIT % - % IDLE, what is the average for a virtual machine?

  I did some research on performance of VM problems and worked with the media to see that there is maybe a bottle neck IO that occur with a virtual VMware machine I have performance problems on. The technician found that the WAITING % - % IDLE on average for this virtual machine is around 200%. The tech said it was abnormally high. I forgot to ask her what was normal but wanted to put a post to see if some people out there know what they are on average. What is an average number of see? I have the system done nothing right now and I see 579% waiting and 372% IDLE. The technology has been able to confirm that no IO queue was occurring in the VMkernel or on the HBA controller.

  Some average % positions would be useful. Thank you.

  gdewulf18480 wrote:

  Supposibly the amount of time in a State of waiting for I/O is the WAIT - IDLE % difference. I was wondering if anyone had the numbers for this feeling. Is there anyone with some of them?

  Q: How will I know the VCPU world waiting for I/O events?

  A: WAIT - % IDLE % can give you an estimate on how much time processor is spent waiting for I/O events. It is an estimate only, because the world wait perhaps for other than the i/o resources. Note that we should do it only for the worlds of the WWW, not the other kind of worlds. Because the VMM worlds represent the best guest behavior. For the disk i/o, another alternative is to read the disk latency stats that we explain in the drive section.

  WAIT % by itself cannot be used, you must develop and examine the individual vCPU % EXPECTATION values and subtract their idle time.  You can't do it on the initial view of a single line by VM CPU in esxtop.  If technology that you mentioned did not explain it, he doesn't know what it takes.

  I have lots of virtual machines that are never less than 300% when I wait - % idle and I have no problems.

  It is an example, I caught NimSoft server:

  DHSNMS1 100 100 5 192.63 193,80 0.24 0.03 291,44 1.04

  %EST USED (s) 192 - in other words, almost two processors are used 100%

  The %Idle is 1.04% WAIT 291.44 - according to the calculation of waiting idle, I have a super serious problems of e/s past  But this isn't the case, and expanding, I can see that.

  5665 vmware-vmx 100 1 0.09 0.11 100.00 0.00 0.00 0.01

  5667 100 vmassistant.566 1 0.62 0.65 99,63 0.00 0.00 0.00

  5703 100 mks:DHSNMS1 1 0.01 0.01-100.00 0.00 0.00 0.00

  5704 vcpu 100 - 0:DHSNMS1 1 32,35 32.88 67,28 0.28 0.11 67,14

  5705 vcpu 100 - 1:DHSNMS1 1 31,58 32.05 68.11 0.00 67.85 0.12

  So the changed values unfortunately because of ESXTOP bike when you develop... which is annoying, but anyway.  In this you see % waiting is 67 and 68 with another respectively being 3 to 100% (which is normal) and the idle being %, 0, 0, 0, 67 and 67.8.  Doing the calculation on the processors shows a wait - slowed virtually 0 - or very little IO wait past with processors.  But if you add up all the expectations of % and % is idling, you have 434ish, and the 134ish and do the calculation is the difference of 300 - which is the 3 who are always 100%.

  So there is no way we can answer your question, we can only help you to understand how the values should be interpreted.

  Waiting for i/o States almost always go on the disc anyway, it is unlikely, therefore, the network or the user entered, looking at the stats of disc ESXTOP is a much better way to determine if there is a problem of e/s.

• Required physical server Vs Virtual Machine memory

  Is there a white paper explains why we we need less memory in the Virtual Machine as compared to the physical Machine.

  The problem is that my boss wants to know why this is so. It is very difficult for me to explain this to him, he wants to see a white paper OR some article on the internet.

  As long as a VM administrator, I know that we can add and remove a virtual computer memory but it will be not that simple when it comes to physical servers. I suggested to him that we must follow a standard, and if there is a requirement for business we can increase or decrease is according to the needs. So when the salesman comes in they give us specifications for the physical server and not the virtual and there is always an argument that why should have 6-8 GB memory VM from the outset. In order to avoid everything that the arguments it needs more proof.

  Thank you

  Here is a simple explanation of why VM need less memory.  Transparent page sharing.

  If you install a virtual of Windows 2008 SP2 single server machine, lets assume that it uses 500 MB of RAM while sitting idle.  It's basically all running components loaded into memory.

  If you then put a same VM, the new machine virtual don't re-charge not the exact same components in memory.  ESX will see the same exact memory block has been loaded into the memory of the host Server1 (phyiscal material) and then simply point the virtual machine to the component already loaded into memory.

  After the virtual machine has been loaded and GST has kicked, you will probably find that for 2 identical virtual machines you use not only 650MB of memory (not 1000 as expected).  This is because 80% of the components has need of the new virtual machine, it only uses the existing memory blocks, instead of duplicating.

  Now, repeat this operation on 10 VM and assume only 50% of the memory is the same between them... it is still a huge economy of memory.  In this case, since each VM Windows is really loading only 250 MB of itself in memory and split the rest, technically you don't need to allocate 2 GB of RAM for each virtual computer... you can easily get away with putting 1 to 1.5 GB on this server and I have always the same ratio of available memory for the programs that you would do if it was a physical server.

• Virtual machine suck GBs

  Hello

  I am running windows Vista x 64 Edition with vmware fusion (v2.0) on my macbook (intel 2.4 ghz) and his very fast memory to aspire. I do not have stereotypes and for now the virtual machine occupies approximately 26 GB of my memory.  Whenever I have start windows with vmware, that I immediately lose about 1 GB of memory on my macbook, which I can recover after the closure of vmware, so I guess it's normal. However my memory has been declining constantly when using vista, without doing me anything other than use internet explore (no games or downloads) and I never get back that memory. I can't seem to understand what causes this loss memory constant and fast (in an hour, it can go up to 2 GB of memory loss). (I also get an error message when you start vmware stating: "serial0: unable to connect to the printer virtual daemon after 25 attempts.", but I think that its not relevant).

  Here are some details on how to configure the settings for vmware:

  -Processor: 1 virtual processor - RAM: 1084 MB - Autoprotect: disabled - HDD: SCSI Bus type, size of 40 GB drive, pre-allocate space unchecked, divided into 2 GB files audited.

  I tried also to enter the windows Vista x 64 Edition in my virtual machine library by right-clicking and selecting "view the contents of the package. I noticed he called files named "Windows Vista x 64 Edition - s0xx.vmdk", from of "Windows Vista x 64 Edition - s001.vmdk" to "Windows Vista x 64 Edition - s021.vmdk" and "Windows Vista x 64 Edition-000001 - s0xx.vmdk" ranging of "Windows Vista x 64 Edition-000001 - s001.vmdk" to "Windows Vista x 64 Edition-000001 - s021.vmdk» These files are the 26 GB of memory of my virtual machine.

  I would be grateful for any suggestion, as my vmware fusion is rendered unnecessary by this problem (less than 2, 2 GB of free space on your computer, that you can not even start the virtual machine so I had to remove tons of things to make it work) and I need it badly vista for my studies.

  Thank you very much for your help!

  alex1256 wrote:

  1. Yes, I did in fact meen of hard drive space.

  2. and as for the snapshot, I check again and realized indeed he had a snapshot, so I deleted it and an error message appears saying it cannot be deleted: the snapshot is not visible in the menu snapshot, but the files on the disk of the child are still there, but this time named differently ("Edition-000003 - s0xx.vmdk" ranging of "Windows Vista x64Edition-000003 - s001.vmdk" to "Windows Vista x 64 Edition-000003 - s021.vmdk"). I tried to delete the file, but then I get an error message when launching vmware: "file not found: Windows Vista x 64 Edition - 000003.vmdk this file is necessary to power on this virtual machine."  If this file has been moved, please provide its new location. »

  There it is again! This problem from time to time. Bug in merge IMHO.

  Check http://communities.vmware.com/thread/190301

  You must create a new disk and clone your old to get rid of it.

• Could not power on VM: no space is available on the device: cannot power on the virtual machine.

  VMware esx ei, 3.5.0 123629

  Physical memory: 64 GB

  Hard drive: 1.63 TB

  7 virtual machines. 5 of them are configured with 4 GB memory and 2 of them with 2 GB of memory. I am able to power on 3 virtual machines with 4 GB of memory.

  When I try to turn on 4th VM with 2 GB of memory, I get this error message "could not power on VM: no space is available on the device: cannot power on VM.»

  I would like to know if this is the limitation of the ESX Server? How should I size the memory for VMS if I want to run every 7 virtual machines to the

  Moreover, given that I have 64 GB of physical memory. Is there documentation that provides a report of the maximum allowed memory configurable

  compared to the virtual memory?

  Thank you

  Ganesh.

  Ganesh,

  Memory reservations are defined based on VM by VM.

  You can allocate more memory to the virtual machines you have in your host (it's not really a good idea to go crazy with the overcommitment of memory, but some level of excessive pressure is used in general).  Memory applied to your VM resources are shares, bookings and VMkernel Swap limits.

  Just to illustrate:

  You allocate 8 GB memory to a virtual computer.  If you take all the parameters by default, ESX will allot a 8 GB VMkernel Swap file in the base directory of your VM (it will have the extension ".vswp") this VMkernel Swap file is a safety net.  Your virtual machine, at this stage, can consume up to 8 GB of memory If physics is available from the host.  If the memory of your host is overcommitted, some of the available memory 8 GB could be allocated on 8 GB VMkernel Swap file.

  If you set a reserve of memory - 2 GB - this means that the vmkernel will still award the first 2 GB of memory used by the virtual machine to the physical memory.  This is not means that the 2 GB of memory reserved is carved off the coast and completely dedicated to the virtual machine.  This means that the vmkernel offers up to 2 GB of RAM to the VM when and if she needs to use it.  It is a guarantee that the memory will be available upon request.  Because of this guarantee of the VMkernel, VMkernel swap file only has to make sure that the 6 GB memory is satisfied (4 GB total less the 2 GB reserved), so the VMkernel Swap file is only 6 GB in size.

  Actions are a mechanism for prioritization and limits are a cap on physical memory ever allocated to the VM.

  You can set up any number of memory for the virtual machines that you want - frankly, overcommitment of memory for ESX is a very good thing, but you must be vigilant about watching your systems if approve you.  If you have 64 GB of RAM, and you only configure your virtual machines to use total 32G, then you lose 32 GB of RAM.  If you allocate, say, 96 GB of RAM (total) to your virtual machines, then you look at a 50% overcommitment.  What to watch in overcommitting memory is application performance (and more importantly - perception of the user of this performance) and also the memory ballooning and VMkernel Swapping activity.  Those who can both will be in graphics performance in VirtualCenter.  I would recommend reading the Guide to management resources for more details.

  Hope that provides an overview.

  Thank you

  -jk

• Large SQL virtual machines running on ESXi

  Hello

  When you decide to run or do not run large SQL VMs on ESXi, what are the points that you take into consideration?

  -How much memory physical RAM more should the ESXi host at least have in relation to the virtual machine? If I have a Go 96 VM on a host of 144 GB, you would use this room for other virtual machines as well? Would you go to bigger hosts? Or that you would a one-VM-host?

  -In a "a virtual machine by host" scenario, is there still a sufficient reasons to virtualize the VM? VMotion, the portability of the virtual machine, adding disks, disks, resizing easy resize memory still reason enough to virtualize this VM?

  -When I add now Microsoft clustering in the equation, killing VMotion and flexibility, it is always possible to virtualize this SQL Server?

  I know how capable ESXi is the delivery of this workload. I have the white papers of performance on HOW to virtualize SQL successfully. My question is above all on: If you...

  Gabrié

  It is like arguing about policy; There are people with all kinds of views and a large part of it boils down to personal opinions. Some things to consider;

  (1) you do not mention how CRITICISM (aversion to downtime) is the database. If it is super important, certainly looking to HA or even fault tolerance. This increases considerably resources on a virtual machine.

  (2) even if you use one approach "a virtual machine by host", you must make sure that the availability on OTHER hosts in the case where HA is triggered.  So you have basically two hosts per VM

  (3) in view of the above, and how this intensifies that you get in redundancy, HA and FT, you can compare the cost a cluster HA environment.

  We personally, it is facing a prior work. We went with material in the physical server cluster.  In my opinion, if the server is simply great, but didn't need to HA or FT, then I would consider virtualization it. If she needs these features, the fresh material support worsen significantly. Size alone is not a huge problem, assuming you have the SAN space or storage. I am currently supports environments with virtual machines that are more than 1 TB and will work perfectly.

  I hope this helps.

• default virtual machine resource allocation

  Hi all

  I have a host vmware with 64 GB Ram and 12x2.799GHZ cpu cores with 12 VCPU known as multithreading is not active

  When I create a virtual machine with the default settings (there is no reservation or limitation)

  (1) in the tab of the virtual machine resource allocation I see 4167 MB of memory host and 4096 MB of memory comments

  -Why the host memory is only about 4 GB so I have 64 GB of physical memory, which is displayed on the summary of the host tab

  -When I create a virtual machine with the default settings it should be able to use all the resources I'm wrong? in my case, it should be able to use 64 GB of ram

  (2) with the default settings, the virtual machine has only 1 VCPU

  -does that mean that the virtual machine will be able to use speed 1 VCPU? for example, if my vm has a lot of work and it may be necessary to use 3 GHz so I'll have to add virtual vcpu another machine? as the speed of a vcpu is 2.8 Ghz am I bad?

  -If I activate multithreading I 24 VCPU

  each vcpu speed will be (2.799 / 2)?  without active multithreading I have 12 vcpu each 2,799 GHz

  Please clarify for me

  Hello

  You asked a few questions, so that questions will be answered inline

  ) in the tab of the virtual machine resource allocation, I see 4167 MB of memory host and 4096MB of memory comments

  So I guess that you have created a virtual machine with 4 GB of memory (windows 2008 64 bit R2 virtual machine default settings). For this purpose of resource allocation tab 4 GB (4096 MB) of comments. The virtual machine is like a container, providing a configured together to programs and the operating system inside the virtual machine. If memory watch kernel scheduler is 4096MB is available for this customer.

  Now, the kernel needs to use little memory to run the virtual machine, it's called an airline booking memory and is in your case 71 MB, therefor the memory footprint of this virtual machine in the VMkernel (memory of the host) is 4096 + 71 = 4167 MB MB

  -Why the host memory is only about 4 GB so I have 64 GB of physical memory, which is displayed on the summary of the host tab

  This is because you have provided that the virtual machine 4 GB, it's the "use-space" for the virtual machine guest OS to run in. It cannot expand beyond the limit of the virtual machine.

  -When I create a virtual machine with the default settings it should be able to use all the resources I'm wrong? in my case, it should be able to use 64 GB of ram

  If there is no claim, where the demand for resources is less than the provision of resources, the scheduler memory is going to provide the virtual machine, the resources that it requires, and that can go up to 4096 MB, as this is the limit of the container.

  (2) with the default settings, the virtual machine has only 1 VCPU

  -does that mean that the virtual machine will be able to use speed 1 VCPU? for example, if my vm has a lot of work and it may be necessary to use 3 GHz so I'll have to add virtual vcpu another machine? as the speed of a vcpu is 2.8 Ghz am I bad?

  A vCPU runs on a physical basis and may not exceed, for this purpose if you need to have several cycles availble cpu for your virtual machine, you must configure the virtual machine with more than 1 vCPU.

  -If I activate multithreading I 24 VCPU

  each vcpu speed will be (2.799 / 2)?  without active multithreading I have 12 vcpu each 2,799 GHz

  A vCPU can be scheduled on a full physical core or on an element of hyperthreading (SMT), this is done by the VMkernel CPU scheduler. It is completely transparent for the virtual machine.

  Remember that the default settings are a few recommendations, they are not strict guidelines.

• Cannot use 'lab1' host because the host CPU is not compatible with the judgment of the virtual machine suspend state.

  I see that this error was mailed here, but can't seem to find a position with a resolution.

  We use Lab Manager 4.0.4 and just upgraded the hosts in our laboratory.  Before updating to ESXi 4.1 ESX 4.0 u1, we cancelled all VMs in all configurations.  There is none who were suspended, they were all turned off.  We have improved vcenter 4.0 to 4.1 as well.  We moved from a dell poweredge 1950 with two quad core intel L5410 to a r610 with two quad core intel processor E5506.

  When I try to turn on some of the lab configurations (our VM models all work fine), I get this error:

  • Cannot use 'lab1' host because the host CPU is not compatible with the judgment of the virtual machine suspend state.

  I threw the State for the lab configuration (even if it was turned off and cancelled) and still get this message.  I guess the processor architecture of these chips is quite similar, and both are Intel.

  If I go into this directory of Manager of laboratory inside the data store for one of these virtual machines that does not light and add to the inventory, he turned and starts fine on my server esxi 4.1.  So how do Lab Manager to get account it's well deploy and start it?

  Hey billk.

  Although not supported completely, you can solve it by going to the SQL of Lab Manager database.  Make sure that you back up your database before you do anything like that.

  Open the table "fsdir" and corresponds to the dir_id with the id Lab Manager VM.  Once you find the relevant line, change suspend_proctype_id to null (Zero-Ctrl).  You can do this while Lab Manager is still running.

  The results can be unstable (i.e. Windows can crash if it was a drastic change of CPU), but at least you look at a hard reset.  The bat reset certainly not being able to return to the previous state.

  Also note that while Lab Manager does not include CVS, if you activated, your virtual machines still work in CVS mode.  If you have a mixture of heterogenious of hosts in a cluster for Lab Manager, you can see this question pop up a lot.  There is absolutely nothing wrong with take back the virtual machine because of the VCA, but Lab Manager thinks otherwise and prevents it.

• Unable to start the virtual machine after failing to remove the snapshot

  Recently, I tried to delete a snapshot on a Windows XP virtual machine in VMware server 2.0. After a few minutes, the operation has failed, then the GUI crashed. I was not able to manage one of my virtual machines until I rebooted the server. My other virtual machines still work fine. I can't just run the virtual machine on which I tried to remove the snapshot. This virtual machine is very important to me and I would try to get it back. Does anyone have advice? Also, I upgraded this version of VMware server 1.x to 2.x, so please let me know if this may have something to do with this problem. Thanks in advance.

  An additional note. If the virtual machine starts, I suggest that you run chkdsk, just to make sure that there are no problems with the file system of the client.

  André

• Can not power on virtual machines "cannot access the file because it is locked.

  Virtual machines have been working well - then the storage system is down.  After the storage system returns upwards that I can't turn on a number of virtual machines.  Get this error when I try to turn it on:

  Cannot power on vmname on esxhostname.xxxxx.com. Unable to access file < unspecified file name > because it is locked
  error

  1. To check the locks on the Service Console on non ESXi servers, run the command:

     lsof | grep

     COMMAND PID USER FD TYPE SIZE NŒUD NOM_PERIPHERIQUE
     71fd60b6-3631 root 4r REG 0.9 10737418240 23533

     Note: If there is no Console of Service process the locking file, you should receive no printed output. If you receive results, however, file a support request to identify the process and to determine the causes.  If it is a third-party process, however, contact the appropriate provider to determine the cause before you kill the process ID, because it can happen again in the future.

     Stop the process and the lock ID using the kill command. In the example above, the process ID is 3631:

     kill the 3631

     After the termination of the process, you can try to turn on the virtual machine or access the file resource.

  2. To check if the virtual machine is always a world ID assigned, run these commands on all ESX/ESXi hosts:

     CD/tmp
     VM-support - x

     Available to debug worlds:
     WID =

     On the ESX/ESXi host where the virtual machine still works, kill the VM, which releases the lock on the file. To kill the virtual machine, run the command:

     VM-support - X

     Where the is the ID of the world of the virtual machine with the locked file.

     Note: this command takes 5-10 minutes to complete. Answer No to "can I include a screenshot of the virtual machine", and answer Yes to all subsequent questions.

     After the termination of the process, you can turn on the virtual machine or access the file resource.

  Deleting the file .lck (NFS only)

  The virtual machine files can be locked via NFS storage. You can identify this as reported by .lck files. # (where # is the ID of the world that holds the lock file) at the end of the file name. It is a NFS file lock and appears only when you use the ls command as it is the hidden file.
  Beware: they can be removed safely only if the virtual machine is not running.

  Note: VMFS volumes have no .lck files. The locking mechanism for VMFS volumes is managed within VMFS metadata on the volume.

  You must kill the process that is locked, if it is not the case, you probably need to restart the VMware host.
  I tell you from experience most likely end up rebooting it.