2 Replies Latest reply on Dec 27, 2006 9:39 PM by blackpuma

    Disk shrink

    blackpuma Hot Shot

      FYI... I tried disk shrink using the VMware tools last night, in a WinXP guest.

       

      It worked, but it locked the GUI up pretty good for the entire twenty minutes (big VM). I could move the mouse, I could see the UIs of the other apps updating and functioning, but I could not select anything or otherwise interact. Command-Tab would not work either.

       

      I could ssh into the laptop from my Linux workstation, but I didn't do much other than verify that shh worked and that the machine was not dead.

       

      I guess one could call it a "read-only" GUI.

        • 1. Re: Disk shrink
          rcardona2k Champion

          Maybe you can run Activity Monitor prior to kicking off a VM shrink operation and/or tail the vmware.log and see where the host resources are being consumed.  If logging is excessive for instance it's possible to tune that down, although logging is critical for reporting should something go wrong.

          • 2. Re: Disk shrink
            blackpuma Hot Shot

            Maybe you can run Activity Monitor prior to kicking

            off a VM shrink operation and/or tail the vmware.log

            and see where the host resources are being consumed.

             

            I just did this with a Linux guest on the internal hard drive, with less data. The time to complete was much[/b] shorter --- only six minutes --- but the GUI was "read-only" again.

             

            CPU activity hovered around 20-25%, the  Disk Activity was busy as could be expected, and the tailing the log only showed the following:

             

            Dec 27 22:30:17.872: vmx| LOADAVG: 0.99 0.90 0.68

            Dec 27 22:30:23.781: vcpu-0| DISKLIB-LIB   : Shrink (Synchronous) chain 0x3903ce4.

            Dec 27 22:32:32.845: vcpu-0| DISKLIB-LIB   : Shrink (Synchronous) chain 0x1bd4814.

            Dec 27 22:36:04.392: vmx| LOADAVG: 0.84 0.83 0.71