Performing a “configuration only” export / import on Hyper-V

re: Performing a “configuration only” export / import on Hyper-V

Mike _ Olivet — Mon, 21 Jan 2013 19:02:39 GMT

Does anyone know how to fix the problem with access Hyper-V manager. I recieve an error stating the domain admin doesn't have the rights to open the mmc or virftmgmr.msc doesn't exits. I think the problem came from installing hyper-v before joining the 2012 server to the doamin.

Thank you

re: Performing a “configuration only” export / import on Hyper-V

James DeFelice — Thu, 22 Dec 2011 19:56:28 GMT

For anyone following the import problem, there's a thread on the support forum:

social.technet.microsoft.com/.../886189d8-7c0a-4baf-b20b-b330f1763d05

re: Performing a “configuration only” export / import on Hyper-V

James DeFelice — Thu, 15 Dec 2011 15:24:03 GMT

I saved the scripts from the link above as configexp.vbs (for the export) and configimp.vbs (for the import).

Here's what I'm doing:

(1) create VHD d:\testcase1\a.vhd, 2GB

(2) create VHD d:\testcase1\b.vhd, diff disk with parent d:\testcase1\a.vhd

(3) create VHD d:\testcase1\c.vhd, diff disk with parent d:\testcase1\b.vhd

(4) create VHD d:\testcase1\d.vhd, diff disk with parent d:\testcase1\c.vhd

(5) create VHD d:\testcase1\e.vhd, diff disk with parent d:\testcase1\c.vhd

(6) create VM D, 512MB memory, 1 cpu, no networks, use d.vhd as the disk

(7) create VM E, 512MB memory, 1 cpu, no networks, use e.vhd as the disk

(8) start VM D, wait for it to start completely

(9) start VM E, wait for it to start completely

(10) observe that they both start up OK

(11) stop VM D, wait for it to stop completely

(12) stop VM E, wait for it to stop completely

(13) cscript configexp.vbs, enter the name of the server, enter D as the VM, enter d:\D-export as the target path, click OK, the export completes

(14) cscript configexp.vbs, enter the name of the server, enter E as the VM, enter d:\E-export as the target path, click OK, the export completes

(15) delete VM D from hyperv -- observe that the VHDs are still in place

(16) delete VM E from hyperv -- observe that the VHDs are still in place

(17) cscript configimp.vbs, enter the name of the server, enter d:\D-export\D as the import path, click OK, import completes

(18) start VM D, wait for it to start completely

(19) cscript configimp.vbs, enter the name of the server, enter d:\E-export\E as the import path, click OK, import fails

(20) Observe the following error message on the console:

Get the import settings object.

Importing virtual machine. 10% complete

The virtual machine has not been imported.

ErrorCode:0

ErrorDescription:Import completed with warnings. Please check the Admin events in the Hyper-V-VMMS event log for more information.

(21) Observe that the error in the event log complains about c.vhd being already in use.

(22) In the hyperv UI, examine VM D, observe that it is using d.vhd (which is expected)

I believe this to be a bug in hyperv. I performed *every* step here using the hyperv UI except for the execution of the vbs scripts.

re: Performing a “configuration only” export / import on Hyper-V

James DeFelice — Tue, 13 Dec 2011 18:11:25 GMT

Roy B -

I'm having what sounds like a similar problem. I can import a VM that uses multiple levels of disks under a certain condition.

Given the following diff disk chain: a.vhd <-- b.vhd <-- (c.vhd, d.vhd), where c.vhd and d.vhd are children of b.vhd, a.vhd is the "root", and VM C uses c.vhd and VM D uses d.vhd, I can import and start VM C - but doing so prohibits hyperv from importing VM D. Actually, the import of VM D sort-of completes, except that it gives a warning that b.vhd is already in use - and it refuses to populate the IDE connection with d.vhd.

I can manually (either via the UI or powershell) re-attach d.vhd to VM D and start it up just fine.

Any thoughts as to why the import fails?

-James

re: Performing a “configuration only” export / import on Hyper-V

Craig Eberly — Thu, 03 Mar 2011 19:25:28 GMT

Absolutely awesome script. Server 2008 had the option to export config only. I did an in-place upgrade to R2, and the hyper-v role did not upgrade so I had to reinstall the role. Then I found out there was no config only import option in the GUI. Do I seriously need Microsoft to move my VHD's around for me?

THANKS!

re: Performing a “configuration only” export / import on Hyper-V

Roy B — Tue, 01 Mar 2011 22:01:39 GMT

Thanks for publishing the script! Gave me a leg up. Any chance you've encountered the issue of being unable to import a config-only export of a VM with multiple levels of diff disks?

re: Performing a “configuration only” export / import on Hyper-V

Benjamin Armstrong — Mon, 19 Apr 2010 06:24:44 GMT

DS -

This is an unfortunate side effect of the tool that I use to make the code look pretty. An easy solution is to paste the code into wordpad first.

Kieran Jacobsen -

I intentionally included the bin and vsv files. I wanted everything exported except for the VHD files.

Cheers,

Ben

re: Performing a “configuration only” export / import on Hyper-V

Kieran Jacobsen — Fri, 26 Mar 2010 12:25:03 GMT

Ben, I have just compared the output from the powershell library to the output your script produces, and I think there are some problems with your script.

Firstly, your script still copies the bin and vsv files for a vm which is in the saved state. Secondly, in the config.xml file at the root fo the directory, <VmStateCopied type="bool">true</VmStateCopied> which from my understanding should be false.

re: Performing a “configuration only” export / import on Hyper-V

Kieran Jacobsen — Fri, 26 Mar 2010 12:16:12 GMT

I was just looking a making this into a powershell script when i discovered the PowerShell Management Library for Hyper-V (http://pshyperv.codeplex.com/) which includes export-vm which by default is config only.

re: Performing a “configuration only” export / import on Hyper-V

DS — Fri, 26 Mar 2010 11:16:19 GMT

When I copy the code into notepad, everything is in one line only.

Not a big deal, I'll sort it, but is it possible that you save the code in some downloadable form (like zip) or whatever.

Otherwise, a great article, like many here. I'm a regular lurker and keep up the good work.