• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 979
  • Last Modified:

VMware Migration Issue Error Device 0:0 - cold migration

VMware migration issue:
 
Migrating a P2V’d  VM that was an original HP DL 380 G5 physical server. The VM is now a virtual machine running Microsoft Server 2003 with SQL 05 with a RDM. The goal is to convert the RDM to a VMDK. We are running VSphere 5 migrating from an IBM 3500 series to an IBM V7000.
 
On the Cold migration, VSphere is showing about 18% complete while the array on the other end continues to increase up to about 580 GB out of the total VM size of approximately 600 GB. The VM continues to show 18% and stops after around a 580 GB transfer with a Device 0:0 error.
 
VMware and Google searches say it’s due to the CD Rom. VMSupport says that it works sometimes and other times it doesn’t. The process is magic per VM support. So, after taking that under advisement, we ran a Storage vMotion again (about 2 more times) with the same error. We tried to remove the CD rom drive completely, Storage vMotion’d with VM powered off with the same results.
Only other option is to V2V and try again. Or, create another VM with SQL 08 and be done with it. I’d rather see if there’s something worth a try to avoid more problems. Also, just need to add, I've done the same with other VMs with RDMs  that completed successfully within the same environment.
 
Any help would be greatly appreciated.
0
RustyZ32
Asked:
RustyZ32
  • 4
  • 2
3 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
 
RustyZ32Author Commented:
hanccocka:

I appreciate the prompt response. I will try this out later. I was hoping there was something else I could try that would solve the root cause of the problem with your solution as the "workaround". Either way if it get's me to point B, I'm moving forward. I'd like to do this while the VM is powered on. Appreciate the articles. Very informative and will adjust the SSL to false for increased transfer rates.

Any idea why this occurs even with a cold migration? Do we know what could be preventing this even with the vCD removed on a cold migration as to take the CD completely out of the picture?

Thanks!
0
 
RustyZ32Author Commented:
Any idea why this occurs even with a cold migration? Do we know what could be preventing this even with the vCD removed on a cold migration as to take the CD completely out of the picture? Before I run a V2V, can this be resolved any other way? I appreciate the help. Would like to know what might be causing this if we remove the variable causing this.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
the only way would be to start looking through the processes with lsof, and the kernel logs.

But this is really a job for Escalation Engineering within VMware Support, and not and end user fix, this could be a known issue with VMware ESX/ESXi, known internally.

Either v2v, if try an Escalation Route with VMware Support. Ask for it to be Escalated to Escalation Engineer, there might not be a fix. (Contact VMware Account Manager if you have one).
0
 
RustyZ32Author Commented:
Great work hanccocka!
0
 
RustyZ32Author Commented:
To assist others and provide a connection between the original solution, my response and another great solution for others to follow.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now