Hyper-V - Export & Import (Part 1)

Huge required disk for export

RobN — Thu, 28 Aug 2008 04:50:55 GMT

I have a virtual machine I am trying to export.

The virtual machine's size based on it's GUID in the folders \programData\Microsoft\Windows\Hyper-V\Snapshots and Virtual Machines is 35.8 GB. However, when I try to export the VM, it fails bc the required space for export is 120GB.

What's the deal? How is this calculation being made?

[Window Title]

Hyper-V Manager

[Main Instruction]

An error occurred while attempting to export the virtual machine.

[Content]

Failed to export virtual machine 'O14 Main Enlistment' because of low disk space under 'H:\Hyper-V\'.

[Expanded Information]

Failed to export virtual machine 'O14 Main Enlistment' because of low disk space under 'H:\Hyper-V\'. The required space is '119128.975285' MB, and the available space is '50516.031250' MB. (Virtual machine ID ACB01786-8CA7-4565-9061-A2879A2C19B3)

[^] Hide details [Close]

re: Hyper-V - Export & Import (Part 1)

TK — Thu, 28 Aug 2008 06:59:02 GMT

Any recommendations on scripting exports/imports?

Thanks.

re: Hyper-V - Export & Import (Part 1)

Chuck vdL — Fri, 29 Aug 2008 23:54:29 GMT

Robn,

my best guess would be that there must be some differencing disks or something else you failed to count up when you were figuring out the footprint of the current VM.

Rather than seeking support in the comments section of a blog, I'd suggest you try the Technet Hyper-v forum instead. Odds are you will get a rapid response there, which is not likely here as Ben is doing a lot of travelling right now.

http://forums.technet.microsoft.com/en-US/winserverhyperv/threads/

re: Hyper-V - Export & Import (Part 1)

Chuck vdL — Fri, 29 Aug 2008 23:58:51 GMT

Oh as for scripting the exports dude, learn to google! a search on "hyper-v export script" will find several useful hits on the first page, including this gem here

http://blogs.msdn.com/taylorb/archive/2008/06/07/hyper-v-wmi-cloning-virtual-machines-using-import-export.aspx

re: Hyper-V - Export & Import (Part 1)

Zac B — Tue, 02 Sep 2008 05:15:26 GMT

It would be good practice to set the VM's network adapter(s) connection property to "Not Connected" before exporting. If not a warning message will occur after the import. If moving to a different machine then... I think "Unknown" display's if the adapter was left to a setting.

No matter what (as far as I've been) it's not a problem because you can just go in and select the new server's correct adapter. Nobody likes a little warning notice when importing a machine. Personally I start to wonder if I could have messed something else up too.