- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: Hyper-V VSA Bug
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2011 11:40 AM
12-12-2011 11:40 AM
Hyper-V VSA Bug
I've been playing around in my lab with the VSA for Hyper-V prior to rolling it into production. I've discovered a rather evil bug that I wanted to see if someone else could replicate. I can duplicate this problem non-stop, so it's either my particular configuration, or I'm doing something wrong.
Brand new, Windows Server 2008 R2 SP1. Create a basic VM just to verify it all works. (it does)
Install VSA for Hyper-V.
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). 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. 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.
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.
Also, can we make the install smarter so if the path doesn't exist during installation it gets created? 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.
(note: all this was done on the machine itself, logged in as a local administrator)
- Tags:
- Hyper-V
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2011 11:51 AM
12-12-2011 11:51 AM