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.
This is a confirmed problem. There appears no problems with images, but rather the Xen package itself.
This problem started in v3.23 and still isn't fixed in v4.2. Email support [at] mikrotik [dot] com and ask them to fix it.
Referenced post: http://forum.mikrotik.com/viewtopic.php?f=15&t=32036
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.