<?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>topic Hyper-V VSA Bug in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/hyper-v-vsa-bug/m-p/5415695#M4244</link>
    <description>&lt;P&gt;I've been playing around in my lab with the VSA for Hyper-V prior to rolling it into production.&amp;nbsp; I've discovered a rather evil bug that I wanted to see if someone else could replicate.&amp;nbsp; I can duplicate this problem non-stop, so it's either my particular configuration, or I'm doing something wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brand new, Windows Server 2008 R2 SP1.&amp;nbsp; Create a basic VM just to verify it all works. (it does)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Install VSA for Hyper-V.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the VSA installation fails for any reason, it will delete the entire Hyper-V folder out of C:\programdata\microsoft\windows (the default hyper-v installation folder).&amp;nbsp; I've had this happen at least 5 or 6 times now, the latest was because I tried to create a VHD to a path that didn't exist.&amp;nbsp; Thankfully, after the previous time I got wise and backed up the Hyper-V folder before running the VSA installation, so all I had to do was copy it back.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is kind of nasty though, if it's not just me I can imagine the wailing and gnashing of teeth that would occur in a production environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, can we make the install smarter so if the path doesn't exist during installation it gets created?&amp;nbsp; Minor detail I know, but I can't remember the last time software installation would die instead of creating a path that was specified but didn't exist.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(note: all this was done on the machine itself, logged in as a local administrator)&lt;/P&gt;</description>
    <pubDate>Mon, 12 Dec 2011 19:40:54 GMT</pubDate>
    <dc:creator>NCoppersmith</dc:creator>
    <dc:date>2011-12-12T19:40:54Z</dc:date>
    <item>
      <title>Hyper-V VSA Bug</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/hyper-v-vsa-bug/m-p/5415695#M4244</link>
      <description>&lt;P&gt;I've been playing around in my lab with the VSA for Hyper-V prior to rolling it into production.&amp;nbsp; I've discovered a rather evil bug that I wanted to see if someone else could replicate.&amp;nbsp; I can duplicate this problem non-stop, so it's either my particular configuration, or I'm doing something wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brand new, Windows Server 2008 R2 SP1.&amp;nbsp; Create a basic VM just to verify it all works. (it does)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Install VSA for Hyper-V.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the VSA installation fails for any reason, it will delete the entire Hyper-V folder out of C:\programdata\microsoft\windows (the default hyper-v installation folder).&amp;nbsp; I've had this happen at least 5 or 6 times now, the latest was because I tried to create a VHD to a path that didn't exist.&amp;nbsp; Thankfully, after the previous time I got wise and backed up the Hyper-V folder before running the VSA installation, so all I had to do was copy it back.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is kind of nasty though, if it's not just me I can imagine the wailing and gnashing of teeth that would occur in a production environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, can we make the install smarter so if the path doesn't exist during installation it gets created?&amp;nbsp; Minor detail I know, but I can't remember the last time software installation would die instead of creating a path that was specified but didn't exist.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(note: all this was done on the machine itself, logged in as a local administrator)&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2011 19:40:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/hyper-v-vsa-bug/m-p/5415695#M4244</guid>
      <dc:creator>NCoppersmith</dc:creator>
      <dc:date>2011-12-12T19:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Hyper-V VSA Bug</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/hyper-v-vsa-bug/m-p/5415715#M4245</link>
      <description>Actually it looks like it deletes whatever folder you install to if it fails. I had a folder called C:\Hyper-V with a single VM created inside of it and after it failed it removed the entire C:\Hyper-V folder. (doesn't go into the recycle bin either)</description>
      <pubDate>Mon, 12 Dec 2011 19:51:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/hyper-v-vsa-bug/m-p/5415715#M4245</guid>
      <dc:creator>NCoppersmith</dc:creator>
      <dc:date>2011-12-12T19:51:01Z</dc:date>
    </item>
  </channel>
</rss>

