Hi,

We get kernel errors booting ROS6 on Xenserver - Version 5 is working.

/Mikael

Hello,

we have several ROS 5.26 installations on XenServer 6.2 in HVM mode running fine (support for xen/vmware/openvm tools would be superior for live migration support). But upgrading to 6.4 or doing a fresh install of 6.4 from ISO image leads to 100% cpu load during boot process and VM's boot process stops. Console only shows

Loading Linux...................
Loading initrd.rgz............
Ready.

In XenCenter we can see cpu load graphs constantly at 100% for 1 vcpu (doesn't matter how many vcpu we put in). Occasionally network traffic goes up to 1.5 kbps but we can't connect to any mac based service to do any initial (ip) configuration. I changed vcpu from 2 down to 1 and ram from 1024 MB down to 128 MB, but hadn't any success.

What may i look for? How to debug this any further?

Hi,

Same problem with a support case logged over 3 months ago.. and yet no response.

I have yet to find a workaround either.

Lee

Yes! I managed to get RouterOS 6.6 to run on XenServer 6.2. The VM in question was running 5.26.

With XenServer 6.2 (and perhaps earlier) they added support for Windows 8.1, and this support is confusing the mikrotik upgrade/install.

First you'll need a console to the Xenserver Host, so you can change the VM parameters. SSH or XenCenter should work fine.

Secondly you need to find the UUID of the VM in question. Use "xe vm-list" to show all the VMs on the host. Look for the Mikrotik VM, and copy the UUID (The clipboard is your friend here..)


Last step is to turn off the "viridian" support..

Using the uuid in the first command, enter "xe vm-param-set uuid=<UUID from first command> platform:viridian=false"

This turns off the viridian support for the VM.

You can now start a new VM for install, or upgrade an existing one. If you had a VM that was crashing during the 2nd stage of the upgrade, this should allow it to continue.

In my testing, the VM Upgrade that had crashed, worked, but locked up on "starting Services...". Forcing a reboot allowed the VM to function normally.

A 5.26 machine was changed, then upgraded, it functioned normally except it failed to reboot on the first stage when it should have. Forcing the reboot allowed it to continue fine, even through the 2nd stage.. go figure!

A fresh install using a 6.6 ISO failed again to restart after install, but a forced reboot had it boot up to login first time.

I suspect disabling ACPI or other flags may resolve the reboot issue, but at least it isn't crashing out now!

Thank you. Works like a charm.

I did the above procedure and could install version 6.9 without problems but when I put the RouterOS operating consumption processing goes to 100% and the tool / profile it states that 90% of CPU usage in this Ethernet and could not solve it, any tips?

I don't see this behaviour on my machines that were upgraded from 6.7 to 6.9. That public hotspot system is like 99% idle in tool/profile. Do you have any complex packet handling within the firewall/routing? In other threads people say resetting and reconfiguring might help and that some problems with packet marking exist.

Did somebody manage to get live migration working?
I could live migrate after manipulating XenServers metadata to let them think VMware tools were installed. But after live migration there was no network access from or to the VM possible. I guess it's something related to ARP, but I hadn't time to invest it further.

if only problem was with the network - check mac addresses and interfaces of the "router"

if only problem was with the network - check mac addresses and interfaces of the "router"

What do you mean by this? Live migration doesn't change any interface nor mac in the virtual machine.

Thanks AIVAS
Work perfect on XenServer 5.6.0 and RouterOS 6.19
Regards!

In the last RouterOS version my network problem vanished (only tested 5.24 before). Currently my test VM loses 2-4 pings during live migration. Other linux vm's are down to 0-1 lost packets.

In general XenServer supports live migration of HVM guests. But XenCenter doesn't show any buttons to migrate until XenTools are installed. So you need to trick XenServer by manipulating vm's meta data. You need to run this shell script after each boot, reboot and live migration of any RouterOS vm on the host running the vm: possible improvements to this script: the xe command line can query power-state running and meta data like tags (assign them via XenCenter vm properties). then the script could loop through vm's, querying each vm for its dom-id and do xenstore-write. You could run this as a cronjob. An event driven change would be even better. Anyone out there who wants to build script listening to events (boot, reboot, migrate)? Basic examples are in Xen API/SDK documentation.

If you like to pimp available information in XenCenter you can
add ip adresses into the Networking tab in XenCenter: set the operating system name and version: just don't forget to tell the XenServer that you updated meta data after each change: kudos to http://lists.xen.org/archives/html/xen- ... 00015.html