<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>mikrowiz Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>mikrowiz Tracker</description>
    <pubDate>Sat, 25 Nov 2023 11:19:55 GMT</pubDate>
    <dc:date>2023-11-25T11:19:55Z</dc:date>
    <item>
      <title>Re: Thinapp - Spatial Analyzer</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309188#M3408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Interesting.&amp;nbsp; I didn't see any kernelmode warnings when I packaged on Win7.&amp;nbsp; Anyways, thanks for trying.&amp;nbsp; I guess I'll give up.&amp;nbsp; I'll give you a "helpful" for spending the time to verify.&amp;nbsp; Thanks for the effort. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Apr 2012 15:28:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309188#M3408</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2012-04-25T15:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp - Spatial Analyzer</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309186#M3406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess I failed to tell you that we only want to virtualize it &lt;SPAN style="text-decoration: underline;"&gt;without&lt;/SPAN&gt; the sentinel driver.&amp;nbsp; Most people don't need that, because they're not generating data, just consuming it.&amp;nbsp; Without that selected, I've never seen the kernelmode component warnings that you show during capture.&amp;nbsp; Also, I know it can be virtualized, because it works on XP, it just can't be virtualized on Win 7 for some reason.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you try it without the sentinel driver?&amp;nbsp; Just curious.&amp;nbsp; I appreciate the try anyway.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Apr 2012 14:58:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309186#M3406</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2012-04-24T14:58:11Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp - Spatial Analyzer</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309184#M3404</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, actually there is.&amp;nbsp; You can find it at the link below.&amp;nbsp; That would be great.&amp;nbsp; Being fairly new to Thinapp, I've tried everything I know of to try to get it to work.&amp;nbsp; The application works fine natively on Windows 7 (both 32 and 64 bit), but I just can't get it to run Thinapp'd.&amp;nbsp; Works fine on XP, but that isn't horribly useful to me since we have few XP workstations left that need to run this application.&amp;nbsp; Thanks for spending the time!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.kinematics.com/products/spatialanalyzer/download-software.html"&gt;http://www.kinematics.com/products/spatialanalyzer/download-software.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Apr 2012 14:44:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309184#M3404</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2012-04-23T14:44:33Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp - Spatial Analyzer</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309182#M3402</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;4.7 &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Apr 2012 14:45:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309182#M3402</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2012-04-20T14:45:07Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp - Spatial Analyzer</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309180#M3400</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes.&amp;nbsp; I tried this configuration too.&amp;nbsp; Installed on a clean Windows 7 32 bit VM.&amp;nbsp; The application ran fine.&amp;nbsp; Ran the post-scan and packaged it up.&amp;nbsp; Same results.&amp;nbsp; Ntdll.dll and User32.dll throw faults.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2012 22:59:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309180#M3400</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2012-04-19T22:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: Primavera Project Management</title>
      <link>https://communities.vmware.com/t5/ThinApp/Primavera-Project-Management/m-p/784037#M1136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; FYI - The newest version of Oracle's P6 client Thinapps nicely without any fuss.&amp;nbsp; This problem is no longer a problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2012 17:18:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Primavera-Project-Management/m-p/784037#M1136</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2012-04-19T17:18:23Z</dc:date>
    </item>
    <item>
      <title>Thinapp - Spatial Analyzer</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309178#M3398</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm attempting to Thinapp Spatial Analyzer made by New River Kinematics.&amp;nbsp; Seeing how they release a new version every couple of months, it would be spledid to just do a side-by-side update using a Thinapp package.&amp;nbsp; The packaging goes smoothly and runs swell on Windows XP, but when attempting to run it on Windows 7 it crashes prior to launch and the Windows event log shows errors in faulting modules ntdll.dl and user32.dll on both 32 and 64 bit versions of Win7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Windows 7 x64 is the most typical place this package would need to be run, so I also tried packaging it on a clean Windows 7 x64 machine.&amp;nbsp; Results are the same though. The 32-bit version of this application runs fine installed natively on both 32 and 64 bit versions of Windows 7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any suggestion on how to get beyond this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2012 17:10:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Spatial-Analyzer/m-p/1309178#M3398</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2012-04-19T17:10:35Z</dc:date>
    </item>
    <item>
      <title>Primavera Project Management</title>
      <link>https://communities.vmware.com/t5/ThinApp/Primavera-Project-Management/m-p/784036#M1135</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anybody had any luck Thinapp'ing the Primavera P6 client and getting it to work in Windows 7?  I captured it on XP and it works on XP, but not 7.  I also tried capturing it on 7, but it still doesn't work on 7.  If I delete the %SystemSystem%\oleaut32.dll and rebuild it then the client will run on 7 and not crash, but I end up with an error about encryption not being available when trying to establish a connection to the database.  Any ideas?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Oct 2010 15:28:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Primavera-Project-Management/m-p/784036#M1135</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2010-10-01T15:28:04Z</dc:date>
    </item>
    <item>
      <title>Re: VMFS 3.31 expandable?</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/VMFS-3-31-expandable/m-p/2521338#M28154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think so.  There's a limit on the number of extents you can add, but I don't believe there's a limit on the number of times you can expand the volume.  I suspect what it is doing is more like what gparted or the resizing in Windows 2008 does, which is to actually increase the size of the partition.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Oct 2009 18:15:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/VMFS-3-31-expandable/m-p/2521338#M28154</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-10-14T18:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up Vmotion and iSCSI in ESX 3.5</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Setting-up-Vmotion-and-iSCSI-in-ESX-3-5/m-p/1618320#M82983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This looks reasonable.  I have 3 hosts as well, and run with nearly the same setup.  Since I only have 3 hosts and the vMotion and SC traffic are fairly light compared to a larger setup, I've even gone so far as to run iSCSI traffic on the same vSwitch as vMotion and not had any trouble doing so.  That is not recommended if you have more physical NICs available though. :smileygrin:&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Sep 2009 17:09:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Setting-up-Vmotion-and-iSCSI-in-ESX-3-5/m-p/1618320#M82983</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-09-30T17:09:37Z</dc:date>
    </item>
    <item>
      <title>Re: Balloon Target and Balloon above Active on host with plenty of free memory</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Balloon-Target-and-Balloon-above-Active-on-host-with-plenty-of/m-p/2087779#M190361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Brilliant!  Somehow the box got unticked on that one VM.  As soon as I set it back to unlimited the balloon driver backed off.  So obvious!  Thanks for the help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Sep 2009 16:56:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Balloon-Target-and-Balloon-above-Active-on-host-with-plenty-of/m-p/2087779#M190361</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-09-30T16:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: Balloon Target and Balloon above Active on host with plenty of free memory</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Balloon-Target-and-Balloon-above-Active-on-host-with-plenty-of/m-p/2087776#M190358</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The cluster is made up of 3 hosts.  No resource pools.  All resources are fair game to all VM's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Sep 2009 15:10:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Balloon-Target-and-Balloon-above-Active-on-host-with-plenty-of/m-p/2087776#M190358</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-09-30T15:10:35Z</dc:date>
    </item>
    <item>
      <title>Balloon Target and Balloon above Active on host with plenty of free memory</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Balloon-Target-and-Balloon-above-Active-on-host-with-plenty-of/m-p/2087774#M190356</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just when I think I understand ESX memory management, something confuses me again.  My understanding of the balloon driver, is that when an ESX host needs additional memory to allocate to other VM's that the VMKernel steals back memory from running VM's.  However, I have a VM that seems to be showing that the balloon target is well over what the currently "Active" memory is, and the ESX host that the VM is running on has 6GB of &lt;U&gt;unused&lt;/U&gt; memory.  I believe this could have led this VM to get into a memory starved state once already, because I found it unresponsive, only to discover that it was only using 30% CPU and 2GB Active out of 6GB of allocated memory, but doing a ton of memory swapping.  What gives?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Why in the world would the ballon driver target memory on a busy running VM, when there is plenty of free memory available on the host, and why would a guest start swapping when it's only using a fraction of the memory allocated to it and the host is sitting on pletty of free memory?  None of my other VM's have memory usage charts that look like this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Sep 2009 19:35:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Balloon-Target-and-Balloon-above-Active-on-host-with-plenty-of/m-p/2087774#M190356</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-09-29T19:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: No performance data (other than real time &amp; 1 day) ?</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/No-performance-data-other-than-real-time-1-day/m-p/1205942#M38538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My hosts are all version 4.  Yours sure sounds like a similar problem though.  Have you tried evacuating your guests, putting your host into maintenance mode, removing it from the cluster, then adding it back?  That cleared it up for me with my v4 hosts.  Something just wasn't happening properly in the vCenter database I guess, so re-registering the host (and a few guests that were having a similar problem) made them come to life.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Sep 2009 16:42:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/No-performance-data-other-than-real-time-1-day/m-p/1205942#M38538</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-09-14T16:42:13Z</dc:date>
    </item>
    <item>
      <title>Re: No performance data (other than real time &amp; 1 day) ?</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/No-performance-data-other-than-real-time-1-day/m-p/1205940#M38536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had a similar problem after upgrading to vCenter 4 where I could only see "Realtime" performance data on a few of my VM's and one of my hosts.  Figuring it must be some anomoly with the database, since most of them were working fine, I shut those guests down and removed them from inventory and then added them back to inventory.  A few minutes later I magically had 1 Day stats, and then later I had 1 Week Stats.  I'm assuming later I'll have 1 Month and 1 Year after those get rolled up next.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Likewise, with my one host that had the same problem.  I evacuated my guests, shut it down, removed it from the cluster, then added it back.  It fixed my performance stats for that host as well.  Good luck!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Sep 2009 22:46:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/No-performance-data-other-than-real-time-1-day/m-p/1205940#M38536</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-09-11T22:46:34Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere client:Number of active connections increases indefinitely</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-client-Number-of-active-connections-increases/m-p/2117237#M195980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you sure you don't have another connection left open somewhere else accidentally?  I was having a similar problem.  Just as you, I was the only one working in the vSphere environment.  I eventually found out that I had connected by RDP to my vCenter server, launched the vSphere client, and then accidentally left that session logged in and running rather than logging off.  I opened the Terminal Services Manager on the server with the extra remote connection running that apparently had the vSphere client running, and logged that session off, then my number of active connections decreased.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2009 16:04:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-client-Number-of-active-connections-increases/m-p/2117237#M195980</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-08-26T16:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: VMFS 3.31 expandable?</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/VMFS-3-31-expandable/m-p/2521335#M28151</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Henrik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply.  Indeed, I do see it now.  I realized after I posted that, that I was using the vSphere Client, but the actual host my VM was running on was still a 3.5 host.  I had to shut it down to move it, but once it was moved to a v4 host I can now see that it &lt;STRONG&gt;is&lt;/STRONG&gt; expandable using the free space when connected directly to that host.  Like noted previously in this thread though, the same option is not available when connected to the vCenter Server.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One final question regarding this:  Is this a non-destructive process that can be performed on a datastore where there are running guests?  I don't get any warnings so I'm guessing it is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again for this thread.  It has been most useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; HEnrik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Aug 2009 18:47:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/VMFS-3-31-expandable/m-p/2521335#M28151</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-08-24T18:47:32Z</dc:date>
    </item>
    <item>
      <title>Re: VM can't boot after clone failure: post mortem</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/VM-can-t-boot-after-clone-failure-post-mortem/m-p/1203797#M62725</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For the record, I did delete the failed clone snapshot without any ill-effects. Now I'm looking into expanding the datastore into the free space of the now larger SAN volume (thanks to ESX 4) where it lives in to solve the space issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Aug 2009 18:36:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/VM-can-t-boot-after-clone-failure-post-mortem/m-p/1203797#M62725</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-08-24T18:36:36Z</dc:date>
    </item>
    <item>
      <title>Re: VMFS 3.31 expandable?</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/VMFS-3-31-expandable/m-p/2521333#M28149</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Were you guys ever able to successfully answer this question?  I have a problem that would be easily solved if I could simply increase my datastore capacity.  I can't hot vMotion one of my VM's because there isn't enough free space in the datastore (apparently for the duplicate swap file temporarily needed).  I've added 10GB to the iSCSI SAN volume the datastore lives on, and in the vSphere Client while looking at the properties of the datastore I see the Device is 60GB and the Primary Partition is 50GB, but when I try to do an "Increase..." I'm given no choices to use for the expansion.  Just an empty box.  Shouldn't I be able to grow the datastore volume using the available10GB?  It's a VMFS 3.31 volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The evidence presented above sure looks like I should be able to do this, but I'm just not seeing it the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 21:32:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/VMFS-3-31-expandable/m-p/2521333#M28149</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-08-21T21:32:26Z</dc:date>
    </item>
    <item>
      <title>VM can't boot after clone failure: post mortem</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/VM-can-t-boot-after-clone-failure-post-mortem/m-p/1203796#M62724</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ladies and Gentlemen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need your help understanding something.  A few hours ago, in my quest to upgrade to ESX 4, I attempted to vMotion a server to another host in preparation for upgrade of the host.  VirtualCenter reported that there wasn't enough disk space to perform the action.  Huh?  I didn't realize I needed a certain amount of free space on the datastore to perform a vMotion.  Now I do.  Apparently it has something to do with storing the swap file with the VM.  Realizing this, and since the server is stored on a SAN based datastore, I figured I'd just expand the SAN volume and rescan the storage from within the vSphere Client.  However, although it isn't supposed to be a problem, I'd never expanded the SAN volume of a running VM before so I figured I'd clone my VM to loca storage first and set it aside just in case.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is where all hell broke loose.  The clone reached 4% and froze, then a short time later my VM quit responding.  I opened the console in the vSphere Client and found that it was reporting no OS and trying to do a network boot.  What!? I tried to cancel it and couldn't.  All the power options (Power Off, Power On, Restart, Shutdown) were grayed out for the server.  I tried to throw the ESX host into maintenance mode but couldn't.  It just hung as well, so I sent it for a reboot.  When it came back, I tried to power my VM back on (the power options were back).  Same thing, no OS.  I tried detaching it from the host and reattaching.  No joy.  I opened the datastore it was on to see what it looked like.  I noticed there was a couple of small vmdk files, that looked like they were part of some snapshot.  Figuring that must be part of the clone process that failed, I opened a console connection to the ESX host and opened up the vmx file for the VM to see what it had in it.  Sure enough it was pointing at one of those little vmdk files rather than the large vmdk that I new was the main one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ultimately I pointed the vmx back at the main vmdk, not really knowing what I was doing, but after doing so, the VM started.  However, I now see in snapshot manager that I have a snapshot called "clone-temp-1250801069696918".  Obviously I didn't intentionally create that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; So my question is two fold:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)  Why did this happen?  I'm guessing maybe it had something to do with the datastore from which I was trying to clone the VM not having enough space to perform a clone because it needed some sort of temporary working space, but then why didn't it tell me that and not try to do the clone rather than hosing my VM?!  Also, if it is a free space problem, how much space is required on the source datastore to create a clone?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Is it safe to delete the "clone-temp-1250801069696918" snapshot based on the way I resolved the problem by modifying the vmx file?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've never had a problem cloning running VM's before, but now I'm a little nervous about doing it again when it caused such a huge problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 22:54:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/VM-can-t-boot-after-clone-failure-post-mortem/m-p/1203796#M62724</guid>
      <dc:creator>mikrowiz</dc:creator>
      <dc:date>2009-08-20T22:54:34Z</dc:date>
    </item>
  </channel>
</rss>

