AutoSave is slow when the virtual machine is not active

When I actively use a Windows 2000 Server VM and AutoSave is triggered, it's very fast.  But if I did not use the virtual machine for a while, it takes some minutes and minutes.  If I'm trying to go back to the virtual machine, I have to wait indefinitely for the automatic backup complete.

Is it possible to set the priority for the automatic backup feature?

Are you talking about VMware Fusion AutoProtect feature, or something else (perhaps in the comments)? Offhand, it seems that when you have not used within a certain time, Fusion got paged out. Taking the automatic snapshot requires paging backward, which can take some time. You can test this theory by looking at activity monitor and looking at the pageout/publication numbers when you see an automatic preview slow.

Pageouts and pageins are controlled by OS X and not something we have control over. Adding RAM to the Mac, it is more likely merger will stay in memory and avoid this situation.

Tags: VMware

Similar Questions

  • Correctly remove resources when the virtual machine is deleted

    Hello

    I've created a service plan to power off the virtual machine and delete the vcenter.  The workflow works very well, but apparently not released the vRA resources.

    Then he said: the virtual machine has actually deleted vsphere, but since the vRA, Managed administration portal machines, I found the virtual machine that I removed from the service by using the mentioned service blue print now appears as "missing."


    My question is how to downgrade the machine virtual and also removed its resources reserved correctly?

    Thank you

    Jimmy

    Hi, Jimmy - I met the same problem recently and did the following:

    1. download the VC:VirtualMachine object.  This can be done in several ways, but in my particular case, I use the com.vmware.library.vc.vm.getAllVMsMatchingRegexp module.

    2. get the VCAC:VirtualMachine of the object to VC:VirtualMachine object.  Still, there are different ways to do this.  I created a getVCACVm action, which takes a #1 VC:VirtualMachine object:

    var vCACVm = null;

    var uuid = vcVM.config.instanceUuid;

    var vCACVms = Server.findAllForType ("vCAC:VirtualMachine", "VMUniqueID eq '" + uuid + "'");

    If (vCACVms.length == 1)

    vCACVm = vCACVms [0];

    Return vCACVm;

    3. delete the VCAC:VirtualMachine entity.  You can use the com.vmware.library.vcac.deleteEntity module to handle this.

    KEEP IN MIND... This removes only the vCAC/vRA entity.  You should always turn off the virtual machine (if any, see: library/vCenter/Virtual Machine management/Power Management / power off the virtual machine and wait) and delete vcenter (see: vCenter/library/Virtual Machine management/Basic/remove virtual machine).  I do this before performing the three steps above.  He there maybe better, easier, faster, etc., ways to do it.  I hope this helps.

  • How to change the network when the virtual machine is connected, in Vmware ESXi with Perl in Linux?

    Hello

    If someone can answer that the way to change the network of a VM with Perl? I would periodically change the network where the virtual machine network adapter is connected.

    Thank you

    Take a look at the vGhetto repository of scripts, where you can find a lot of useful scripts, including updateVMPortgroup.pl , which may contain what you are looking for.

    André

  • Can I download can imagine them in the data store when the Virtual Machine is running

    or do I have to stop the Virtual Machine first and then download?

    Rgds

    Chris

    If you want to have a consistent state, Yes.

    If you just need a consistent state to the accident, you can create a snapshot, download the base vmdk files and then validate once again the snapshot operation.

    You cannot download files in use (except the read-only).

    André

  • ESXi host goes to the State and the virtual machine does not restart on other host does not

    Hi all

    I'm looking for a solution, in which case the host goes to the State and the virtual machine on it does not restart on a different host (they'll just gray) does not not what could be the problem here and how to fix it

    later when the failed host returns upward machines either go to motor off the coast of the State, or they show that under tension

    While the host is down or not responding do not I am able to ping the host ESXi (5.5) and able to ping the default gateway and the DNS servers of the host itself

    Yes AF, the answer to all these questions is Yes, it is a HA and DRS cluster active, I tried restarting mgmt service, we use a shared storage (storage iSCSI HP 3PAR and left hand)

  • NPIV enabled on the virtual machine, but not seen in the comments

    Hello

    I have a 5.0 with an HBA qlogic esxi. I created a VM and rhel is installed.

    Then I activated the npiv on this virtual machine and saw that it generated node WWN and port WWN.

    However, when I logged in the comments, I am not able to see the names of ports in

    / sys/Class/scsi_host/Host {n} / device / fc_host:host {n} / port_name

    Are there additional configuration on the side of the virtual machine to allow the WWNS within the guest?

    Thanks in advance.

    Hello

    This is a very detailed description of all the required tasks for use with VMware NPIV.

    NPIV: N-Port ID Virtualization

    Kind regards

    Ralf

  • Windows on VM - says my copy of Windows 7 on the virtual machine is not authentic

    I have the Virtual Machine on a Mac and am running Windows 7 on the virtual machine.  I get a message that my copy of windows is not genuine, so, how do I get a product key.
    I get a message from Microsoft that this copy of Windows is not supported.  If I need to buy Windows overall, how can I download it to VM?

    You can purchase a license for the edition you installed and change the key and activate it on the Internet.

    http://www.Microsoft.com/Windows/buy/default.aspx

    http://Windows.Microsoft.com/en-us/Windows7/get-a-new-Windows-product-key

    Click Start, right click on computer

    Click on properties

    Scroll down to the Windows Activation

    Click on the link "change product key".

    Enter the product key and click next to activate via the Internet.

  • In opening the virtual machine: "could not find a peer valid to connect to" or "error of Transport (VMDB) - 32" / "-14" ""»

    Hello

    Since yesterday after a reboot of my host (DELL E6410, W7 SP1 64-bit, 8 GB RAM, 2x750GB SATA3 running WorkStation 9.0.2 Update Windows Update), I can't open my existing VM.

    I often get "can not find a valid peer to connect to" and sometime before: "Transport (VMDB) - 32 error: Pipe: reading is not'or'error of Transport (VMDB)"-14: fitting broke

    I worked for 2 years on this machine without a hitch, WS7 reclassification in WS9 without any problem.

    FYI: we have changed the domain 3 months ago, but it has never be a problem.

    I have google and search several Forum. So far, I tried to:

    -restart the service vmware-auth as an administrator

    -launch vmware.exe administrator

    stop/start the vmx86 service

    -uninstall / reboot / install Workstation.  3 times. First using uninstall from the Control Panel, then doing a / clean before installation and finally track down any file/reg entry.

    -HE asked if any group policy changes were made recently (like not allowing to run vmware.exe?)

    -Rename vmware.exe (logs I look similar to what is in this post: http://communities.vmware.com/thread/331099?start=0 & tstart = 0 ... but no luck)

    -excluded vmware.exe in my AV (Microsoft ForeFront). Unfortunately, in that I'm not allowed disabled...

    -Open the virtual machine using the drive == > does not work either.

    This isn't a file corrupted in a virtual machine (even backup - 7zipped - don't work on my laptop... but the launch on the other).

    Even a newly created WM (boneless), unbootable! :-(

    *, BUT to BE NOTE *: if a virtual machine is created as a shared virtual machine, I can start the application locally remotely! And this same VM, if started (via the.vmx) does not work using Workstation GUI!

    I have attached 2 newspapers. Work a (vmware.log remotely) and the inactive (vmware-vmx - 4072.log thru WS GUI).

    Of after what I saw (and what little I understand), it's as if the CPU is not detected?

    The two newspapers have this line:

    FeatureCompat: EVC masks:

    but the non-working goes - we with

    Module CPUID initialization failed.

    While working it display information on CPU (hostCPUID name / family / type... etc...)

    Any idea is welcome.

    I'll answer me to my problem!

    A lot of research to this knowledge.

    In summary: don't mess with the processor affinity... or keep it in mind!

    Response to distinguish:

    I installed 6 months ago a small utility named prio (search for "PRI prnwatch"), because it can save the priority of a given process. What I did notice, is that it also save the processor affinity ! What happened: I probably changed the affinity once for a VM running to give greater priority to a 7zip archive process to complete more quickly (setting HT no core to 7zip and one - or 2? - HT core to VM). Everything works until the next reboot, where the CPU detection during * start EVERY * VM has been somewhat "damaged" leading to the wrong log message: failed initialization Module CPUID.

    This is the reason of *my* question. Perhaps it might help someone else?

    TIPS:

    For advanced people who do not want to check the processor affinity of each process in the Task Manager, you can try this Windows Powershell command (remember to launch PowerShell as an administrator):

    Get-Process | Format-Table-PriorityClass name, ProcessorAffinity property

    ProcessorAffinity column gives the number of representation of the authorized core, 1-bit by heart.

    15 = 1111 is all possible core (for a logical processor 4). Mine is 1 CPU with 2 core HT <=>4.

    LSB is the core lowest. So if you allow only core0 and core3 (1001) on a process, the number of ProcessorAffinity will be 9...

    Post edited by: cbiero (LSB and MSB...)

  • Slow down the virtual machines on the host of underutilized - unknown reason

    Hello

    What could cause virtual machines running on a host computer with a lot of unused memory, processor power and disk IO sink so slowly that it takes 30 minutes just to open a Windows session on one of them?

    I ran about 5 virtual machines on a host with 16 GB of RAM, but have now upgraded to 32 GB of RAM in the hope to add more virtual machines. At some point, most of the machines is idle, and SysInternals Process Explorer shows less than 20% use by the processors. E/s disk too is usually measured in kb/s - 16 disks systems although RAID is capable of much more of IO.

    As soon as I run about 6 or 7 of virtual machines instead of about 5, I meet considerable slowdowns as mentioned above. I use only about 20 GB of the 32 GB in the system when problems occur.

    Dramatik2

    The aggreggate e/s disc is irrelevant.

    You need to look at the disk queue length, read, write, transfer, etc.

    http://www.computerperformance.co.UK/Healthcheck/Disk_Health.htm

  • Migration of storage when the virtual machine has several data stores

    How can I (or can I) use Storage vMotion on ESX4.0 U1 to migrate part of a virtual computer to a new data store?  I have a virtual machine with 5 data stores attached and move 1 data warehouses to a LUN of larger size.  What is the best method?

    On the "Select the data store" window, click on the button "Advanced". You can specify the location of each VMDK and configuration files.

  • Discover the virtual machine with VMware View 4.5.  "That underlies the virtual machine is not available.

    I have installed the following to an ESX 4.1 server:

    -VMware View connection server (Server 2008 R2 Ent)

    -V - Center (Server 2003 Std)

    Install the VMware Client with Local Mode 4.5 to a laptop

    Installed VMware Agent to a Windows XP and Win7 is a guest vm on the ESX Server.

    I can connet with success both of these machines.

    When I try to extract either of these machines, I get the error message after 2% saying, "underlying this desktop virtual machine is unavailable.

    Can someone tell what to do to solve this problem?  I can't find anything so far for this error.

    Thank you

    Did you install and configure a forwarding server?

    -Mike

  • ROM of the Virtual Machine is not supported

    I have a VMware ESXi 4 environment where I'm currently under several SLES 11 virtual machines with FT.  I went to activate FT another, but when I try and enable it, I see this error:

    -ERROR task-2477-vm-1033 - vim. VirtualMachine.createSecondary: vim.fault.VmConfigIncompatibleForFaultTolerance:

    {(vim.fault.VmConfigIncompatibleForFaultTolerance)

    dynamicType =,

    MSG = 'Device 'Virtual machine ROM' is not supported.',

    },

    MSG = "Configuration of virtual machine for the no fault tolerance."

    }

    I looked around, but couldn't understand what he complains.  I compared the configuration to the other SLES11 VMs I have under my feet, but I don't see the difference.  Thank you!

    Matt

    Hello.

    You have VMI or paravirtualization, activated in this guest SLES?  It is not supported with FT.

    Good luck!

  • With instant full VM LUN and now the virtual machine will not start or register

    Hello

    I have a case here, where we have a virtual machine that quickly filled the logic unit number and the snapshot is currently 110 GB. It is now available on the new LUN space, but the VM does not start and he was also addressed as 'unknown' in the viclient. I tried to cancel the registration and check-in again, but he refuses to register. It seems that the snapshot is damaged.

    When you try to save it, I get the following in hostd.log:

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': (17) successfully opened size = 48348147712, hd = 0. Type 3

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': open with success (21) size = 48348147712, hd = 0. Type 3

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': closed.

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': closed.

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 3

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 3

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': closed.

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': closed.

    DISKLIB-LINK: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': cannot open (the specified file is not a virtual disk).

    DISKLIB-STRING: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': cannot open (the specified file is not a virtual disk).

    DISKLIB-LIB: unable to open ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ' with flags 0 x 11 (the specified file is not a virtual disk).

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 8

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 8

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': closed.

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': closed.

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 8

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 8

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': closed.

    DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': closed.

    DISKLIB-LINK: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': cannot open (the specified file is not a virtual disk).

    DISKLIB-STRING: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': cannot open (the specified file is not a virtual disk).

    DISKLIB-LIB: unable to open ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ' with flags 0 x 11 (the specified file is not a virtual disk).

    Referred to as registry: AXAPTA/AXAPTA.vmx

    Vmsvc indicates file is loaded, by: /vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA.vmx

    I also tried to copy virtual machines directory down to a local PC and run via VMware Converter, but I get the message "the source VMware Consolidated Backup"filename.vmx"has a missing catalog file.

    1. VMware - v

    VMware ESX Server 3.5.0 build-130756

    Any help is appreciated.

    Lars

    The problem (according to the newspaper) is AXAPTA_1-000001 - delta.vmdk no AXAPTA_1-000002 - delta.vmdk (the error on the second snapshot is probably because of the broken parent snapshot).

    The descriptors are ok, which means that the VMDK itself is broken.

    If you do not have a backup, you can try the following:

    -Copy the files in another data store

    -change the second snapshot descriptor to point to the basedisk as the parent

    -Try and mount the drive

    -If you're lucky, you should be able to recover at least some data of

    -If the disklib is complaining again then the two snapshots are broken - which is unlikely

    Depending on how old the second snapshot (the older one is better it is) the method above will not help.

  • Windows Server 2003 physical to the virtual machine does not start

    I have converted a windows server machine 2003 virtual machine image.  Conversion completed successfully but the machine image custom virtual boot I get the blue screen of death which is probably do the scsi driver being changed during the conversion of my question is: how to install these drivers once the pc has been converted? I try to avoid to do from scratch with constraints of time it takes to get this virtual image starts, please help

    Semper Fi

    You must use SCSI.  Replace your SCSI controller during the conversion.

    ... also, I'm under the assumption that the destination ESX (i)?

  • Register the virtual machine does not properly

    I run the following script, but it does not work as expected.

    $ESXHost = 'test - 01.Test.com '.

    $ResourcePool = get-VMHost $ESXHost | Get-ResourcePool | Get-View
    $vmFolder = get-View (Get-data center-name $Datacenter |) Get - Folder - name "vm") user.user
    $vmFolder.RegisterVM_Task ("[TIER2_VMSHARED_LASCX02_LUN2017]" + $VMName + "/" + $VMName + ".vmx", $VMName, $false, $ResourcePool.MoRef, $null ")

    When the script is run, it saves the VM on Test-04?  Any suggestions?

    E4F

    The last parameter to RegisterVM_Task is the host where you want the guest to save.

    You pass $null, so DRS will decide for you.

    If you want a specific host, you can do

    $ESXHost = "Test-01.Test.com"
    $esx = Get-VMHost -Name $ESXHost $ResourcePool = $esx | Get-ResourcePool | Get-View $vmFolder = Get-View (Get-Datacenter -Name $Datacenter | Get-Folder -Name "vm").id
    $vmFolder.RegisterVM_Task("[TIER2_VMSHARED_LASCX02_LUN2017] " +  $VMName + "/" + $VMName + ".vmx", $VMName, $false, $ResourcePool.MoRef, $esx.Extensiondata.MoRef)
    

Maybe you are looking for