none
Windows 8.1 and Hyper-V

    Question

  • Hi All

    I have successfully installed windows 8.1 and Hyper-V on my HP Probook 4540s having previously run Windows 8 but I have been totally unable to import any of my Generation 1 Virtual Machines as the wizard says no machine found. These all previously in Windows 8. is there a setting I have not found or is this a beta (preview) problem? If there is no work around I will have to revert to Windows 8.

    Frank

    Frank


    Frank

    Saturday, June 29, 2013 8:36 AM

Answers

  • I have found my own solution all be it a tedious one.

    I built a Windows Server 2012 machine and activated Hyper-V (I believe a Windows 8.0 with Hyper-V would also have worked)

    Installed the virtual machines from the Microsoft installation disks

    Exported the Machines to a USB Drive. I found that it made no difference if I powered up the VMs before exporting them. It seems that all that was required is to install them into Server 2012 Hyper-V and then export them.

    Imported the VM into Windows 8.1 and they imported correctly.

    As a trial I also exported the Machines from Windows Server 2008 R2 but these machines would not import into Windows 8.1

    I trust that this will be resolved by the installation wizard before the full release

    Frank


    Frank

    Wednesday, July 03, 2013 7:20 AM
  • Thanks Bill and Bob

    I now understand the problem and the solution

    Frank


    Frank

    Thursday, July 04, 2013 7:41 AM

All replies

  •   Have you tried to create a new vm using the existing .vhdx file?

      I don't have any pre-existing guests on this machine but will try to import one from the 2012 server later today.

     

     

    Bill

    Sunday, June 30, 2013 12:02 AM
  •   I would have expected your vms to still be available if you did an upgrade. As I said above, I did not have any pre-existing Hyper-V vms on this machine. I had been using VirtualBox. (My VBox vms were certainly still available after upgrade).

       You can only import a machine which has been exported. To import them now you would need to have exported them before you upgraded. If you did not, the wizard is correct in saying there are no machines to import.


    Bill

    Sunday, June 30, 2013 3:53 AM
  • Hyper-V V3, the one in Windows 8, can import VM's without a prior export.  It's quite a bit changed from earlier versions.

    And yes, if the Win 8.1 install was an upgrade, it keeps the existing VM's that are already in the Hyper-V Manager.


    Bob Comer - Microsoft MVP Virtual Machine


    • Edited by Bob Comer Sunday, June 30, 2013 12:19 PM addition
    Sunday, June 30, 2013 12:09 PM
  • The import for Hyper-V v3 in Windows 8 is a little picky about just which folder you select.  Drill down each level into your VM's folder structure and try it until it works basically.  I was able to import with Windows 8.1 from the level about the folder that contains "Virtual Machine" and "Virtual Hard Disks", but you may have to go to the "Virtual Machines" level or lower when importing an older VM.


    Bob Comer - Microsoft MVP Virtual Machine

    Sunday, June 30, 2013 12:17 PM
  • Thanks for experimenting. I find it odd that things that imported into 8.0 won't into 8.1

    I can confirm that upgrading did maintain installed VMs but the only way I can import (so far) into 8.1 is to export a machine from my upgraded 8.1 machine.

    The machine I am trying to import are Microsoft Training Machines (Yes I know they were designed to install into Windows Server 2008 R2) but they were importable into 8.0 but fail into 8.1

    Just hope the final release will be less picky

    Frank


    Frank

    Sunday, June 30, 2013 1:53 PM
  • I have found my own solution all be it a tedious one.

    I built a Windows Server 2012 machine and activated Hyper-V (I believe a Windows 8.0 with Hyper-V would also have worked)

    Installed the virtual machines from the Microsoft installation disks

    Exported the Machines to a USB Drive. I found that it made no difference if I powered up the VMs before exporting them. It seems that all that was required is to install them into Server 2012 Hyper-V and then export them.

    Imported the VM into Windows 8.1 and they imported correctly.

    As a trial I also exported the Machines from Windows Server 2008 R2 but these machines would not import into Windows 8.1

    I trust that this will be resolved by the installation wizard before the full release

    Frank


    Frank

    Wednesday, July 03, 2013 7:20 AM
  • Hi,

    Glad you have found the solution. Thanks for sharing. We really appreciate your time and efforts. Hope your experience will help other community members facing similar problems.

    Regards,



    Vincent Wang
    TechNet Community Support

    Wednesday, July 03, 2013 7:50 AM
  • I have found my own solution all be it a tedious one.

    I built a Windows Server 2012 machine and activated Hyper-V (I believe a Windows 8.0 with Hyper-V would also have worked)

    Installed the virtual machines from the Microsoft installation disks

    Exported the Machines to a USB Drive. I found that it made no difference if I powered up the VMs before exporting them. It seems that all that was required is to install them into Server 2012 Hyper-V and then export them.

    Imported the VM into Windows 8.1 and they imported correctly.

    As a trial I also exported the Machines from Windows Server 2008 R2 but these machines would not import into Windows 8.1

    I trust that this will be resolved by the installation wizard before the full release

    Frank


    Frank

      I doubt that this will change in the RTM version. Import/Export has changed in 2012R2 and I expect Win 8.1 to be the same.

    This was posted in reply to a similar question in the Hyper-V forum by Taylor Brown from the dev team.

    VM's that are exported from Windows Server 2008 or 2008 R2 utilized the version 1 WMI namespace which resulted in a .exp file to represent the exported virtual machine.  In Windows Server 2012 we introduced a new WMI namespace (version 2 or root\virtualization\v2) which implemented a much better import/export model – allowing you to effectively just copy the virtual machine folder (with the VM’s XML configuration file inside it) as well as the VM’s VHDs and then import that directly.  For Windows Server 2012 we maintained the version 1 WMI namespace which allowed for importing of Windows Server 2008/R2 VM’s on 2012.

    In Windows Server 2012 R2 we have removed the old version 1 namespace which means we can’t import virtual machines that where exported from Windows Server 2008/R2.  However we can import them if you copy the virtual machine xml file and VHD’s – to do this you need to stop the vmms on the 2008/R2 server – copy all of the virtual machine files/vhds to the Windows Server 2012 R2 server and then import them.


    -Taylor Brown
    -Program Manager, Hyper-V
    -http://blogs.msdn.com/taylorb

     

    Bill

    • Proposed as answer by Bob Comer Thursday, July 04, 2013 4:06 AM
    Thursday, July 04, 2013 2:00 AM
  • Good find Bill, that definitely sounds like the answer and it tickles some of my own memories on the subject.  I guess I just don't have any real Hyper-V V1's anymore to see the right problem myself.

    Bob Comer - Microsoft MVP Virtual Machine

    Thursday, July 04, 2013 4:08 AM
  • Thanks Bill and Bob

    I now understand the problem and the solution

    Frank


    Frank

    Thursday, July 04, 2013 7:41 AM
  • Frank (OP), I see that you unproposed Bob Comer's reply as an answer. The reason I'm proposing it as an answer again is quite simply because it worked for me. Understanding that it might not have resolved your particular problem, based on settings, configs, etc., it is a quick and simple fix when it does work, so I think it's worth putting out there for people to try.

    No disrespect intended, just putting it out there for consideration.

    Thanks.

    PS - the fact that for some people, having to select a folder other than the one in which the .VHD file is actually stored is, I would say, a "sub-optimal" design. Something MS should look into addressing.
    • Edited by Jetboy2k Tuesday, April 01, 2014 5:11 PM
    Tuesday, April 01, 2014 5:08 PM
  • I think you will find that I indeed maked this as answered back in July 2013 (see below) so I don't understand your issue

    Frank 

      • Marked as answer by                             Frank Jennings<abbr class="affil"></abbr>                         Thursday, July 04, 2013 7:41 AM                    
      Thursday, July 04, 2013 7:41 AM

    Frank

    Wednesday, April 02, 2014 7:02 AM
  • I think you will find that I indeed maked this as answered back in July 2013 (see below) so I don't understand your issue

    Frank 

      • Marked as answer by                             Frank Jennings<abbr class="affil"></abbr>                         Thursday, July 04, 2013 7:41 AM                    
      Thursday, July 04, 2013 7:41 AM

    Frank

    Apologies, I wasn't clear. I was referring to Bob Comer's reply regarding needing to select the correct folder. I didn't see that Mr. Comer in fact has more than one reply in this thread, so I should have been clearer. The selection of a higher level folder when navigating to the .VHD file worked for me and since that solution was a quick and easy fix I proposed that particular response as an answer as well.

    Again, apologies for not being clearer as to which particular response I was referencing as another potential solution for readers.

    Wednesday, April 02, 2014 4:28 PM