Hyper-V Virtual Machine Mover

New Post: Bug - only attach ONE vm when the importing folder contains more than one VM

macarthor — Fri, 27 May 2011 04:39:52 GMT

Dears,

If the importing folder, which contains the "Virtual Machines" and "Snapshots" folders, has more than one VM, i.e., more than one XML file in the "Virtual Machines" folder, VMM only attaches one VM to Hyper-V.

In such situation, the AttachVM() function throws an exception. I think it's quite easy to add a "foreach" to process such case.

May you fix this. Thanks!

New Post: Bug - Fail if the origianl VM is present in Hyper-V manager.

macarthor — Thu, 26 May 2011 09:14:19 GMT

Dears,

I've found it a great tool and idea!

A bug was found also...If you copy an existing (here existing means you can see it in the Hyper-V manager) VM on the same host, and attach it, the attaching would fail - due to GUID conflict.

I'd like you fix it. Thanks!

And, the format of AVHD seems to be different in windows server 2008 and windows server 2008 r2, in that Hyper-v R2 AVHD contains VHD path information. I'd like you would consider this point in future beta or release versions for R2 - modify the AVHD file for VHD path information.

New Post: Failed to set permissions

rwagnon — Sat, 06 Nov 2010 00:14:15 GMT

When we ran the program we received the error "Failed to set permissions to".

This was resolved by using "Run as Administrator".

Source code checked in, #63489

_TFSSERVICE — Tue, 27 Jul 2010 20:28:19 GMT

Checked in by server upgrade

Released: VMMove 1.0.2.0 (Jun 29, 2010)

Wed, 30 Jun 2010 01:35:50 GMT

Public release of 1.0.2.0

Updated Release: VMMove 1.0.2.0 (Jun 29, 2010)

jlaban — Wed, 30 Jun 2010 01:35:50 GMT

Public release of 1.0.2.0

Updated Wiki: Home

jlaban — Wed, 30 Jun 2010 01:20:06 GMT

This utility is meant to work on Hyper-V RTM only. It has NOT been tested heavily on Hyper-V for Windows Server 2008 SP2 nor Windows Server 2008 Hyper-V R2.

This tool was originally published here : http://www.jaylee.org/page/Hyper-V-Virtual-Machine-Mover.aspx

This utility can also work remotely, particularly with Hyper-V Server 2008.

Here is a list of facts to know before using this tool :

A VM can only be detached if it is in the "Saved" or "Stopped" state.
It is not necessary to stop the Hyper-V service and all modifications are detected live by the service.
A VM can only be imported if it contains at least on HDD on the IDE 0 controller.
All the VM files must be under the same directory, HDD and snapshots.
All files that are modified are backed-up next to the original files; All other files are not modified nor moved.
.NET 3.5 must be installed.
Both command line and GUI tools must run "as administrator".
For remote operations, the current user must be an member of the administrators group of the remote system.

This utility comes in two flavors, a command line tool and an GUI.

The Command Line utility

The command line utility supports two commands. The first to detach a virtual machine :

    vmmove d "my vm" "myserver"

The server parameter is optional. If omitted, the tool will perform the operation on the local machine.

Now to attach a VM :

    vmmove a "C:\Hyper-V\MyVM" "myserver"

The server parameter is also optional here. The path specified is always considered as a local path for the target Hyper-V service even if it is a remote machine.

The GUI Utility

The GUI utility allows to perform both attach and detach operations visually, but only on the local machine. Remote operations may be added in a future version of the tool.

Updated Wiki: Home

jlaban — Wed, 30 Jun 2010 01:19:51 GMT

A VM can only be detached if it is in the "Saved" or "Stopped" state.
It is not necessary to stop the Hyper-V service and all modifications are detected live by the service.
A VM can only be imported if it contains at least on HDD on the IDE 0 controller.
All the VM files must be under the same directory, HDD and snapshots.
All files that are modified are backed-up next to the original files; All other files are not modified nor moved.
.NET 3.5 must be installed.
Both command line and GUI tools must run "as administrator".
For remote operations, the current user must be an member of the administrators group of the remote system.