VMware Cloud Community
khughes
Virtuoso
Virtuoso
Jump to solution

vmotion from 3.0.2 to 3.5 warning

When we go to vmotion from a 3.0.2 machine to a 3.5 box, we get a combatability warning displayed below. Is there any reason to be concerned about this message or is it simply updating the .vmx file to make it compabtable with 3.5? When we migrate it to a 3.5 box will be able to vmotion it back to a 3.0.2 box after this modification?

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
1 Solution

Accepted Solutions
Troy_Clavell
Immortal
Immortal
Jump to solution

it's kind of a warning message, but can be safely ignored.

http://kb.vmware.com/kb/1003770

View solution in original post

Reply
0 Kudos
10 Replies
hstagner
VMware Employee
VMware Employee
Jump to solution

Hello Kyle,

I have not tried to vmotion between two different versions of ESX (not a best practice, I can assume). I would create a test vm on the cluster and try it out to see what happens first. That would probably be the safest route.

Regards,

Harley Stagner

----------------------------------------- Don't forget to mark this answer "correct" or "helpful" if you found it useful (you'll get points too). Regards, Harley Stagner VCP3/4, VCAP-DCD4/5, VCDX3/4/5 Website: http://www.harleystagner.com Twitter: hstagner
Reply
0 Kudos
khughes
Virtuoso
Virtuoso
Jump to solution

I'm pretty sure I know a handful of people that run a mix environment until they fully convert to 3.5, so I'm pretty sure there shouldn't be any issues vmotioning between 3.5 and 3.0.2 as long as we don't update the vmtools

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal
Jump to solution

it's kind of a warning message, but can be safely ignored.

http://kb.vmware.com/kb/1003770

Reply
0 Kudos
khughes
Virtuoso
Virtuoso
Jump to solution

Thanks Troy, so it is just modifying the config of the machine to run in the new host (3.5) but it can still go back and forth between 3.0.2 and 3.5.

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal
Jump to solution

yup, no probelm at all go back and forth

mikepodoherty
Expert
Expert
Jump to solution

We see the same warning during our upgrade from 3.0.1 to 3.5 U2. We've tested and can VMotion back and forth without problems. We VMotion the VMs to the upgraded server and then upgrade the host and have had no problems.

khughes
Virtuoso
Virtuoso
Jump to solution

Thanks guys, I had no doubts it could. Of course now that my boss wanted me to show him, it wont VMotion... time to call up vmware and figure out whats going on.

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
mikepodoherty
Expert
Expert
Jump to solution

Check your VM network names - 3.5 used a different default than 3.0.1 so I had to sync the names in order for VMotion to work.

Reply
0 Kudos
khughes
Virtuoso
Virtuoso
Jump to solution

That was the first thing I checked, vmotion group, lan port groups all match up

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
mikepodoherty
Expert
Expert
Jump to solution

Have you looked at /var/log/vmwre/vpx/vpxa.log on the host server you are VMotioning from to see what error is generated?

We had a typo in the VMkernel gateway that caused VMotion to fail and the log helped us pinpoint the issue.

Reply
0 Kudos