CHR v6.42 with ESXI

RouterOS Virtualization
1

Hi!

According to release notes, starting v.6.42 CHR supports open-vm-tools:

*) chr - added “open-vm-tools” on VMware installations;

Well, after the software upgrade and restart, indeed, it looks like vm-tools feature-set is supported, but also now I’ve got notification from ESXI with the text below:

“The configured guest OS (Other (64-bit)) for this virtual machine does not match the guest that is currently running (Other 3.x or later Linux (64-bit)). You should specify the correct guest OS to allow for guest-specific optimizations”

and of course, VMWare offers me to change VM guest OS software version and type to resolve the issue.

This CHR installed a year ago in line with the documentation on wiki (https://wiki.mikrotik.com/wiki/Manual:CHR_VMWare_installation) where recommended OS type was “Other 64-bits”.

So, what should I do next to resolve the issue and remove annoying notification from ESXI web interface?

Thanks in advance!

2

I changed the Guest OS to “Other 3.x or later Linux (64-bit)” in ESXI and the message dissapeared.

3

Can anyone explain why the documentation differs from what VMWare is recommending?

What is actually impacted?

4

Hi everyone,

I encountered the same issue, but on ROS 7. Specifically:


The configured guest OS (Other Linux (64-bit)) for this virtual machine does not match the guest that is currently running (Other 4.x Linux (64-bit)).

I’ve tried about a dozen guest OS options, but the error persists. Setting it to “Other 3.x or later Linux (64-bit)” doesn’t help either.

ESXi-803-ROS716.PNG
I’m using ROS 7.16.x under ESXi 8.0.3, the latest version.

5

You should select “Other 4.x Linux” in the guest OS option just as it tells you to do

6

Thank you, Cap! But there is no such option, and that is the issue.

7

Maybe need to recreate the VM or got your settings mixed up.
I cant check right now but im sure ESXi 6.7 even has “other 4.x Linux” option.


UPDATE:
I found this archlinux topic with a screenshot clearly showing “Other 4.X Linux” on 6.7
https://bbs.archlinux.org/viewtopic.php?id=246075
https://imgur.com/flameshot-screenshot-hUpZVhq

EDIT: I just noticed you’re running ESXi 5.5?
Thats ancient

If not might have to upgrade compatibility

8

Check these out:
Linux-1.PNG
Other.PNG
Linux-2.PNG

9

Incorrect. Please review the initial post information more carefully.


I’m using ROS 7.16.x under ESXi 8.0.3, the latest version.

10

Yeah i was sure i read 8 somewhere but couldnt find it again lol


EDIT:
Btw ur CentOS doesn’t even go up to 8/9 either, so definitely ESXi 5.5 Mode

Suse 9 lol

11

I’m no rookie, buddy. I’ve been in IT for 20 years. It looks like there are no longer generic script versions for the Linux 4 kernel in ESXi—only branded builds.

12

Yes, but compatibility is set to 5.5 so the available OSes for 5.5 could not cover the needed one. You have to try clone that VM, set compatibilty to the later one closer to the 8.x VMWare host and check what happens. Cloning machine will kill the license in the clone but you have to check not if cloned CHR works but what VMWare says about the OS..

13

You never stop learning :wink:
And today is ur day to learn about ESXi compatibility mode.

Not true. Other 6.x or later is an option in current versions (with current compatibility!)

You even have Suse 9 in the list.
current version is 15 btw.

https://www.linuxquestions.org/questions/blog/rkelsen-138375/setting-up-a-slackware64-15-0-virtual-machine-on-vmware-esxi-8-0-0-38763/

14

Hi. Thank you, this helped solve the problem. There’s no need to clone anything; there’s an “Upgrade VM Compatibility” option in the right-click context menu.

There was no license since this was a trial copy. So, there are no issues here.

Thanks for not passing by this thread!

15

Cloning was suggested just for safety to not brake anything on the running/production VM. Forgive me that “professional distortion” (*).
“Upgrade” option is the proper official way. If you need you can downgrade/upgrade VM version editing directly the vmx configuration file downloading, editing and uploading it back when VM state is “off”. Very usable if you want to run VM with the newer HW version set in an older ESXi to bypass problems of unsupported devices being used as they are accepted just as they are defined. Tried that not so long ago.

(*) Admins could be divided into two groups: The ones that MAKE backups and the ones that WILL BE making backups. It is only the matter of time. :slight_smile: