I'm trying to use my Xen vm machine on v4.1 but no success which perfectly runs on v3.22. Only thing seems to be inappropriate is the main memory parameter under the xen menu which i can set but os is not getting aware of it.

Do you guys have a plan to fix this issue so we can use our existing stuff with the new router os versions? We don't have a kvm capable cpu so kvm paclkage is not an option.

Thanks
Gokalp

I'm trying to use my Xen vm machine on v4.1 but no success which perfectly runs on v3.22. Only thing seems to be inappropriate is the main memory parameter under the xen menu which i can set but os is not getting aware of it.

Do you guys have a plan to fix this issue so we can use our existing stuff with the new router os versions? We don't have a kvm capable cpu so kvm paclkage is not an option.

Thanks
Gokalp

IMO, you did everything right, tombrdfrd66, but there's a problem with memory-for-main xen parameter in RouterOS versions 3.23 and 3.24 - seems like it's simply ignored.

I was using centos xen image with 3.22 and noticed it didn't work any more after upgrade to 3.23 (failed-to-setup-vm status). It was reporting full physical memory size for main and ignored any setting I entered for memory limit in xen parameters - and the same thing happens with 3.24, too. After downgrade back to 3.22, everything is back to normal.

So it's either waiting for a fix from MT or back to good ole 3.22... that is, if you need xen.

You can still use another linux distribution as the xen "hypervisor" and routeros as virtual machines.

if you have a 'master' image with a basic ROS-x86 install, and copy to different image files, it will work.
However i don't know if it violates the EULA or not.
(Running several virtual router on mikrotik "hypervisor" is allowed - so running several virtual routers on different "hypervisor" maybe the same