Information and announcements from Program Managers, Product Managers, Developers and Testers in the Microsoft Virtualization team.
Given the rather compressed schedule of Windows Server 2008 R2, we did not have time to get too ambitious with the UI. However, the UI has been modeled to enable the following 3 scenarios:
1. Export VMs with data
2. Import VMs with data
3. Export a snapshot of a VM
4. Provide the option for copy on import or in-place import
5. Allow the user to import the VM with a newly generated ID.
Here is a screen capture of the Export UI you get when you right-click on a virtual machine in the Hyper-V Manager and click “Export…” :
It is still rather rudimentary and allows the user to specify the location to export the VM to. The VM will be exported along with its VHD files and saved state files to the specified folder. You might notice that the check-box for doing a configuration-only export is not there. This is by design, but we do support configuration-only export. More on this topic in a subsequent blogpost.
Exporting a snapshot:
To export a snapshot, right-click on the snapshot you want to export (in the snapshots pane that shows up for a selected virtual machine in Hyper-V) and click on “Export…”. It will bring up the Export UI above.
The import UI is launched from the same spot under the Actions pane in Hyper-V manager:
In the import UI, check the highlighted checkbox and you will end up copying the VM on import, leaving files in the import directory good for a second import.
The other UI elements in the import UI follow the same pattern as in v1: the location for the import directory as well as the option for regenerating the VM’s unique ID. The import UI assumes that all the necessary files for the import to succeed are in the import directory. Ideally, given that the import process has so many fine grained options, we would have had an import wizard to allow the user the full range of choices. However, short of that, the user can script against the APIs to get the functionality they need. There will be a couple of blogs following this with sample scripts that would give the reader a good idea of how to use the APIs.
Your expression was illustrated thank all of you wonderful
Ok lets say I want to upgrade a virtual machine with Windows server 2003 to Server 2008R2. I want high availability so that end users won't experience any downtime. I want to create a clone of my virtual machine so that I can do the upgrade and test to see if its working ok. When I'm finished I want to bring this new Windows 2008R2 machine replacing the old windows server 2003.
So firtst I want a new unique ID for my new virtual machine, but after I want the old unique ID back to replace the old virtual machine. Is this possible?
I'm feeling a bit stupid, but I can't seem to get the basic import/export to work more than one time.
What I did was create a new VM, named it Base2008R2, installed Windows Server 2008R2, installed Itegration services, sysprepped, shutdown. Exported to D:\ExportedVMs
I managed to Import this VM and rename it (I looked carefully to rename the lower one of the two in the Hyper-V list). I chose Copy/Create new unique ID and checked "Duplicate all files".
A second time, however, I got the error The file already exists (Base2008R2.vhd, no GUID in the filename). Then I fiddled around with renaming and copying the export folder, but either I got the above error, or something like "this is not an exported VM,
use Hyper-V Manager to create one".
I must admit, I am a newbie trying to get the grips all by myself...
So, I tried a second time. I deleted the BaseVM and created a new one, naming it Base2008R2-2 this time. I carefully followed the instructions in
technet.microsoft.com/.../ee256064(v=ws.10).aspx steps 5 and 7, except for connecting to the external network.
This time again, I got the same error: "Import task failed to copy the file from 'D:\ExportedVMs\Base2008R2-2\Virtual Hard Disks\Base2008R2-2.vhd' to 'C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\Base2008R2-2.vhd': The file already exists. (0x80070050)"
Any help or pointers in the right direction very much appreciated!