Migration from MSVS 2005 to Hyper-v and the reverse
- Migration to is pretty straight forward - remove MS additons and things go pretty well
Has anyone tried the reverse?
I can imaging removal of the Integration Componants is the requirement here?
Answers
This should work, you can run the MP kernel on a UP machine... You will need to uninstall the intergration components prior to the migration.
But who want's to go back the Virtual Server after Hyper-V anyway :-)...
All Replies
It depends. For example the 2003 OS is being modified to a MP kernel when installing the IC's. You cannot go back to VS after that.
- Yes this appears to be the case - 2000 machines seem OK as no changes take place. I am going to try migration back to MSVS just to see how disasterous it can be.
The 2000 machines make the move back basicly unscaved and only req VMadditions to be reinstalled. It is important to realize moving VM's from one platform to another and back can be done. Moving w2k workstation and server works very well as long as the vmadditions are removed prior to migration to HyperV. Moving these back only requires reinstallation of the vmaddtions.
2003 may be moved also with great success however going from hyperV back to 2005 VS is like a P2V as the hal is modified so a full windows repair and activation is required. I have tested the reverse migration and it works fine with these extra steps. I imagine one could eliminate this problem by booting off the 2003 iso and using the repair console simply make a backup copy of the hal prior to the install of the Integration componants. Doing so one could then replace the original hal prior to the move back to 2005 VS.
I believe until HyperV becomes a working standard this type of back and forth migration will be common place.
- If I wanted to migrate from Hyper-V to Virtual Server, I would try using SCVMM's P2V feature. It is the best P2V tool available anywhere. I expect that it would work for Hyper-V to Virtual Server, but I haven't tried it for this specific case.
This should work, you can run the MP kernel on a UP machine... You will need to uninstall the intergration components prior to the migration.
But who want's to go back the Virtual Server after Hyper-V anyway :-)...
- I would agree - why would you go back? However it is not whether you wish to but rather you will "have" to. Not all clients are going to pony up an extra grand for 2008 server especialy for a DR or temp vm setup so you will probably get into the issue of configuration on 2008 then reverse migrate to service there needs. So it is important to know that it can be done and how to do the conversion.
I converted 3 systems just yesterday for this very purpose. Sorry for the ignorance, but what is an MP kernal and a UP Machine?
Peter Walke - Clarity Consulting- I agree with you, because my first attempt in migrating Virtual Server machines resulted in the following unresolved issues:- Network interface does not work on the virtual machines- Windows XP machines have to be re-activated- Some hardware drivers have to be re-installedSo far, I thought about dual booting my test machine on my previous OS (WinXP 64-bit) and re-loading the virtual machines, if I find a way to dual boot on Win Server 2008. Having said that, this "solution" is not practical for a production environment, in my opinion. I trust you understand that usually in organizations one seeks to implement standard installations.
I agree with you, because my first attempt in migrating Virtual Server machines resulted in the following unresolved issues:
- Network interface does not work on the virtual machines- Windows XP machines have to be re-activated- Some hardware drivers have to be re-installedSo far, I thought about dual booting my test machine on my previous OS (WinXP 64-bit) and re-loading the virtual machines, if I find a way to dual boot on Win Server 2008. Having said that, this "solution" is not practical for a production environment, in my opinion. I trust you understand that usually in organizations one seeks to implement standard installations.
Migration of a Virtual Server vm to Hyper-V does work, but it is much easier when using a P2V tool such as the one in SCVMM. If you choose to do a migration manually, you won't have the Integration Services present in the migrated vm. By adding a legacy network adapter, networking will work. You can use the legacy network adapter to have network acces to the vm until you can install Integration Services, assuming it is a supported OS. After installing iIntegration Serices, the legacy network adapter can be replaced with a synthetic adapter. Reinstallation of drivers is required because Virtual Server and Hyper-V handle netowrking, video, and mouse differently. Reactivation is necessary because Virtual Server and Hyper-V have different HALs. Vista and newer OSes are easier to migrate because of the force HAL detection in msconfig.
All of these issues are known and well documented in multiple places.
