Can we get vmware and xentools into the CHR release asap please? This facilitates a number of features, especially in xenserver. You can't do live-migration and full HA without the xentools....

I have a pair of servers running xenserver 6.5sp1. I'd LOVE to be able to have my CHR for the wISP be true HA. Right now, I can do a 'restart' which brings it back up on the other node after ~20-30 seconds... but that's downtime.

Thanks.

Can we get vmware and xentools into the CHR release asap please? This facilitates a number of features, especially in xenserver. You can't do live-migration and full HA without the xentools....

I have a pair of servers running xenserver 6.5sp1. I'd LOVE to be able to have my CHR for the wISP be true HA. Right now, I can do a 'restart' which brings it back up on the other node after ~20-30 seconds... but that's downtime.

Thanks.

I totally agree I am waiting on this for few years already Please guys start support xentools in mikrotik.

What are these extra features that are missing? CHR already has all the drivers that you need (interfaces and storage) which is what usually people need, when they ask for VMware tools.

Also see this thread: http://forum.mikrotik.com/viewtopic.php?f=15&t=101204

we will consider adding such features, however, I cannot promise that they will be available some day and all these tools packages will never be available in RouterOS.

one major need is for live migration. Without xentools, live migrations are done using a method that locks up CHR. Add xentools and live migrations will work. This issue exists on vanilla linux as well.

Secondly, without xentools, CHR locks up when altering CPU priority. This issue exists on xentools and vmware and exposes itself in vmware whenever the CPU resources are lower than CPU Mhz. If the CPU is 3Ghz, the cpu resources mush be set at 3Ghz or you get random lockups. In XenServer, it's just CPU priority, and anything but medium locks up CHR.


I realize and agree that all tool platforms isn't reasonable to maintain in routeros, but if you guys could handle the most common ones. Vmware, XenServer, Hyper-V and VirtualBox....

+1 for this. If it could be distributed as npk files then we could pick the tools we need for the hypervisor we run.

I second this request too.

+1 for me. CHR needs Vmware tools, at least the basics so the server can shut down the guest, and move it to a different host.

Integrating open-vm-tools is a must for CHR.

+1 for this

I would also like vmware tools please. Just started using a few routers on ESXi and yep, going to continue doing this.

Definitely. Much easier to run a scheduled shutdown than have it culled when an urgent shutdown is required.
That and if a maintenance reboot / ESXi update is applied a stable shutdown of all guests on a server is much easier than having to SSH/Winbox in as an extra step just to shut down the CHR..

In VMware, no tools, means you cant monitor the VM with the same tools for automatic restarts.

"Application monitoring requires heartbeats from vmtools"

https://pubs.vmware.com/vsphere-50/inde ... D78E7.html

The CHR 6.42RC version now includes these tools!