×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

VMware ESXi 4.0 to ESXi 3.5 ?

VMware ESXi 4.0 to ESXi 3.5 ?

VMware ESXi 4.0 to ESXi 3.5 ?

(OP)
Before anyone asks "why would you want to do that?" I'll explain the situation.
In our production enviroment we run ESXI 4.0. Management has asked that I create a lab enviroment using some old equipment, but using the exact same vmdks as the production enviroment. The old equipment at hand is a Dell 2600 with dual 32 bit Xeons. They cannot run ESXi 4.0 since they are not 64bit compatible. So thats one part of the problem.
The other part of the problem is that the production enviroment and the lab enviroment are in two physical locations and different networks and per management they need to remain that way, so I can't simply tell VMware converter to send the files to the other ESXi server.
I have copied the VM folder from thevia download from the datastore (incorrect?) and placed this onto the external drive and then use vmware converter to import it into the ESXi 3.5 server.
I get the error "The VMWARE Consolidated backup source: E:/VMDKname has a missing catalog file" before I can specify a destination. Can someone please tell me where to look for a solution to this? Thanks.
 

RE: VMware ESXi 4.0 to ESXi 3.5 ?

If the virtual machine you are trying to move has a snap-shot on the source, delete the snap-shot before attempting to move the VM.

Also, if the virtual machine hardware was updated to version 7, 3.5 won't run it.  The process your following sounds like your just simply copying the VMDK over and wanting to start it up (you need the VMX file as well).  I would suggest you use P2V process to move the machine over.
 

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt                    Senior Network Engineer
Keep IT Simple http://www.kiscc.com  
Novell Platinum Partner          Microsoft Gold Partner
VMWare Enterprise Partner    Citrix Gold Partner
 

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close