Accedi
 
HomeLibraryRisorseFormazioneDownloadSupportoCommunityForumBlog
Risorse per professionisti IT >
> 
> 
Hyper-V to Virtual PC

Answered Hyper-V to Virtual PC

  • martedì 11 novembre 2008 17:21
     
     
    Registrati per votare
    0

    Here is the scenario I am curious about:

    At my office I would like to run a windows 2008 hyper-v server to host developement guest machines. Some of our developers are remote so I would like to be able to have them stop by the office and get a copy of there guest os vhd and run it on thier laptop via Virtual PC. The guest OS in this situaton would be windows server 2008 standard.


    In short I would like to go back and forth from Hyper-V to Virtual PC, can I make this situation work and what if any are the technical hurdles?

     

Tutte le risposte

  • martedì 11 novembre 2008 18:09
    Moderatore
     
     Con risposta
    Registrati per votare
    0
    From Hyper-v to VirtualPC can be done.

    However, back and forth between the two is not recommended.

    And generally, moving backward from Hyper-V to VirtualPC is not recommended at all.

    Why, VMAdditions and the VHD format. 

    The VMAdditions drivers are not happy with Hyper-V.

    Now, if this is really necessary. (since you mentioned WS08 as your guest OS). it can be done. - however there are no guarantees that it will work, or will not crumble over time, if you do get it to work.

    In theory - do not install VMAdditions (you will only miss a few of the VirtualPC plusses, such as shared folders, copy/paste, and dragging files into the VM.

    The interaction with the VM would have to be as it is with Hyper-V - you use RDP directly into the VM to get the rich desktop and to transfer files (or use traditional file sharing).

    All the important things like booting, desktop, and networking will function just fine.

    Another important item, build your VHD on VirtualPC, not Hyper-V.  The VHD format is slightly different (I don't know the details).

    FYI - I just copied a VHD from Hyper-V (built on Hyper-V) to VirtualPC and the boot does not complete.

    The best (and most prudent) recommendation at this time is to not do it.

    Brian Ehlert (hopefully you have found this useful)
    • Contrassegnato come risposta Chang Yin venerdì 21 novembre 2008 02:00
    •  
     
  • martedì 11 novembre 2008 18:33
    Moderatore
     
     Con risposta
    Registrati per votare
    0
    Brian is correct. I'll be more blunt. Don't do this, it's a bad idea. Go from VPC to Hyper-V only. Chemists have what they call irreversible reactions (example: vulcanization of rubber). This is ours. 
     
  • giovedì 4 dicembre 2008 16:50
     
     
    Registrati per votare
    0
    I need to move my virtual guest OS's from my hyper-v server to my laptop and back also. This can and is being done with MS Virtual server to VIrtual PC and VMware server to from vmware workstation/player.

    Has anyone found a reliable solution other that VMWare for this issue? Is Microsoft offering a desktop player/developer solution that is compatable with Hyper-v server virtual guests?
    RonG
     
  • lunedì 8 dicembre 2008 01:49
    Moderatore
     
     
    Registrati per votare
    0
    Many of us are running Hyper-V on our laptops so that we can move vhds from laptop to server and back. This approach is gaining in popularity among those who do demos for a living. You'll see a lot of the speakers at the next TechEd running 2008 Server on their laptops just so they can use Hyper-V. I prefer 2008 Server to Vista on my laptop. I dual booted for a few months and finally decided to single boot 2008 with Hyper-V.
     
  • giovedì 11 febbraio 2010 16:10
     
     
    Registrati per votare
    0

    Is there some way to move a Hyper-V VHD file to Virtual PC?  This is a one time move and won't be moving it back to Hyper-V.

     
  • giovedì 11 febbraio 2010 16:58
    Moderatore
     
     
    Registrati per votare
    0
    VMware works in this model because of how they do their virtualization - their architecture of emulation totally lends itself to this model.
    The Hyper-V model of paravirtualization does not lend itself well to this.

    The best option for you is to run the older Virtual Server product witht he older VirtualPC product (2007)

    Unfortunately Hyper-V + VPC 7 has not been built to support this scenario.

    And the hitch is the copying of machines from client to hypervisor and back again - that is the MSFT hitch.
    But this is only a statement for today.

    Brian Ehlert (hopefully you have found this useful)
     
  • giovedì 11 febbraio 2010 17:02
    Moderatore
     
     
    Registrati per votare
    0
    First question:  Which version of VirtualPC?

    Second question:  Do you like a little pain?  There is always pain, it is the degree that changes..

    John outlines his pain here:
    http://sqlblog.com/blogs/john_paul_cook/archive/2009/08/29/migrating-a-virtual-machine-from-virtual-pc-to-hyper-v-and-back.aspx

    If you sysprep in between all the hardware is re-detected, that might help.
    But pay attention to John's entire post and his recording.
    Brian Ehlert (hopefully you have found this useful)
     
  • mercoledì 2 maggio 2012 21:58
     
     
    Registrati per votare
    0

    I couldn't use Hyper-V drive on Windows Virtual PC which runs on 32-bit Windows 7. When the virtual machine starts, it displays "Windows is loading files ...", then it reboots and then again "Windows is loading files ..." forever.

    is there anything else that I need to configure? I simply created a new VM and pointed it to the existing Hyper-V drive.

    Strangely enough, Virtual PC 2007 drives don't work with Windows Virtual PC either. They simply hang without any messages..

    -Stan

     
  • giovedì 3 maggio 2012 01:37
     
     
    Registrati per votare
    0

    What is the OS you're trying to move?  If it is 64bit it won't work at all.  Also, if you have VHD files set larger than 127GB they won't work under VPC either.  You should probably remove the Hyper-V IC before you attempt to use the VHD on WVPC.

    VPC 2007 VMs will work, the base virtualized and emulated hardware is the same.

     
  • giovedì 3 maggio 2012 01:59
    Moderatore
     
     
    Registrati per votare
    0

    migrating between VPC, VirtualPC and Hyper-V requires a HAL change in the OS of the VM.

    So, your experience is totally dependant on the OS installed in the VM and how it deals with that.

    For the most part, a bit of seraching will show you that you must uninstall the VPC VMAdditions before going to Hyper-V.  Removing the Hyper-V ICs is not an equal issue to go back to VPC.

    But, can you go back and forth?  Not easily and not recommended.

    Also, XPMode uses a virutal snapshot / rollback virtual disk that is technically a differnecing disk but not totally equal.  So there is an implementaiton change there.

    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

     
  • giovedì 10 maggio 2012 16:54
     
     
    Registrati per votare
    0

    Guest OS is 32-bit Win 2003, VHD is smaller than 127GB.