[admin@namai] /xen> make-routeros-image file-name=ros.img file-size=48 action timed out - try again, if error continues contact MikroTik support and send a supout file (13) [admin@namai] /xen> /file print # NAME TYPE SIZE CREATION-TIME 0 MikroTik-01062008-0559.backup backup 311474 jun/01/2008 05:59:51 1 MikroTik-01072008-0559.backup backup 427426 jul/01/2008 05:59:50 2 ros.img .img file 50331648 jul/09/2008 23:07:15 [admin@namai] /xen> /system resource print uptime: 5m2s version: "3.11" free-memory: 23872kB total-memory: 47640kB cpu: "Pentium" cpu-count: 1 cpu-frequency: 448MHz cpu-load: 7 free-hdd-space: 152768kB total-hdd-space: 242442kB write-sect-since-reboot: 175240 write-sect-total: 1049908 architecture-name: "x86" board-name: "x86"
[admin@MikroTik] /xen> make-routeros-image file-name="rosss" file-size=36MiB [admin@MikroTik] /xen> make-routeros-image file-name="rossss" file-size=36
[admin@MikroTik] /xen> /system package print Flags: X - disabled # NAME VERSION SCHEDULED 0 X mpls 3.11 1 option 3.11 2 xen 3.11 3 routeros-x86 3.11 4 ipv6 3.11 5 routerboard 3.11 6 wireless 3.11 7 hotspot 3.11 8 dhcp 3.11 9 routing 3.11 10 ppp 3.11 11 security 3.11 12 advanced-tools 3.11 13 multicast 3.11 14 system 3.11
Starting... Checking disk integrity... No errors found. hwclock: Could not access RTC: No such file or directory Starting services... Demo license expired! Please reinstall the router. connect failed (errno=2) Shutting down... Stopping services... connect failed (errno=2) hwclock: Could not access RTC: No such file or directory System halted.
and - about how slow hardware we are talking where you get the errors?
my testbed is 3GHz C2D (45nm) with 2GB RAM 80GB HDD
on what hardware you installed the xen package and what you see on the display (when rebooting) when you attach it to the hardware?I wanted to give the xen package a test. After installing it on a pcengines Board (i know this wasn't powerful enough for virtualisation - but i had it in spare ;o) ) and rebooting, the board starts to permantly reboot in an endless loop. No chance to get it up working again.
A feature or boot option to start without xen would be great to not loose all former settings if accindently installed...
But overall: Great work folks!
PCEngines - miniATX with AMD Geode 500MHz CPU - 256 MB RAM. I know this isn't powerful enough and it hasn't VT but it is 386based ;o)on what hardware you installed the xen package and what you see on the display (when rebooting) when you attach it to the hardware?
Problem is: the PCengines Board supports booting from LAN but won't boot from netinstall.If all else fails do a netinstall keeping the old config without uploading the XEN package...
VT is not required as all guests run paravirtualized
xen add console-telnet-port=64002 cpu-count=1 disk-images=hda:centos.img initrd=centos.initrd.rgz kernel=vmlinuz-2.6.18-53.el5xen kernel-cmdline="root=/dev/hda1" memory=256MiB name=centos weight=256
[admin@MikroTik] /xen> console centos [Ctrl-A is the prefix key] CentOS release 5 (Final) Kernel 2.6.18-53.el5xen on an i686 centos login:
[admin@MikroTik] > xen print Flags: X - disabled, C - configuration-changed # NAME MEMORY WEIGHT STATE 0 X clark 1024MiB 256 disabled 1 xROS 128MiB 256 running 2 centos 256MiB 256 running
I did exactly the same thing Fortunatley I keep a backup when doing such thingsPCEngines - miniATX with AMD Geode 500MHz CPU - 256 MB RAM. I know this isn't powerful enough and it hasn't VT but it is 386based ;o)on what hardware you installed the xen package and what you see on the display (when rebooting) when you attach it to the hardware?
You see ROS coming up something like "booting xen hypervisor" - than black screen and reboot.