VMware Cloud Community
phil_H1
Contributor
Contributor

Vmware importer Reboots System

Evertime I run the importer. The server reboots itself. I run the importer converting a Wosktation 5.5 to VMServer 1.0 standalone image. Running the tool on a Windows 2003 R2 server.

But when I use the importer utility I get a spontaneous reboot. Here is the last entry in the import log

\[2006-05-15 15:27:48.099 'App' 3820 verbose] \[imageProcessingTaskStep,294] copy local->local: 11% completed

\[2006-05-15 15:27:48.099 'App' 416 verbose] \[imageProcessingTaskStep,294] Cloning into disk E:\VMTesting\VMTesting.vmdk: 11% completed

\[2006-05-15 15:27:48.099 'App' 652 verbose] \[imageProcessingTaskWrapper,358] Waiting for updates...

\[2006-05-15 15:27:48.115 'App' 416 verbose] \[imageProcessingTaskStep,294] cloning target disks: 11% completed

\[2006-05-15 15:27:48.115 'App' 416 verbose] \[imageProcessingTaskWrapper,358] Waiting for updates...

\[2006-05-15 15:27:48.115 'App' 652 verbose] \[imageProcessingTaskStep,294] clone to VM: 11% completed

\[2006-05-15 15:27:48.115 'App' 652 verbose] \[imageProcessingTaskStep,294] create and clone to VM: 15% completed

\[2006-05-15 15:27:48.115 'App' 416 verbose] \[imageProcessingTaskWrapper,358] Waiting for updates...

\[2006-05-15 15:27:48.115 'App' 652 verbose] \[imageProcessingTaskStep,294] Clone and reconfigure VM: 14% completed

\[2006-05-15 15:27:48.115 'App' 652 verbose] \[imageProcessingTaskWrapper,358] Waiting for updates...

\[2006-05-15 15:27:48.115 'App' 416 verbose] \[imageProcessingTaskWrapper,358] Waiting for updates...

\[2006-05-15 15:27:48.115 'App' 652 verbose] \[imageProcessingTaskWrapper,358] Waiting for updates...

Windows Event - 6008 - The previous system shutdown at 3:27:06 PM on 5/15/2006 was unexpected.

Vm Server is the only other application on the system

Any ideas...

Thanks in advance.

Reply
0 Kudos
2 Replies
RDPetruska
Leadership
Leadership

First off, why are you running the importer on a Workstation 5.5 image if you want to run it in Server 1.0? They are already at the same version level for hardware and configuration. Just copy/move the workstation image over to your Server computer, register the VM, and run it.

Reply
0 Kudos
gautam
Expert
Expert

This is very surprising and not something I have seen. Are you having this problem when running VM Importer 2 on other hosts? Are you having this problem when importing this particular VM or does it happen for all VMs that you try to import?

Reply
0 Kudos