Alcatel Unleashed

Hi all!

Great news everyone!

As of 7750 SR-OS 12.0.R4 Alcatel Lucent provide you with a Virtual Machine download for the SR-OS.
TiMOS-SR-12.0.R4-vm.zip

The archive contains a .qcow2 (QEMU) disc image.

I create this post so we can collect all our experiences with this in on topic.

I am currently trying to boot it in a Virtual Box environment.
What I have done so far, is to convert the disk image from qcow2 to vdi as I would like to run it in VirtualBox on Windows rather then on Linux.
Its not up and running yet, but I will update as soon as I have a working environment

Please share your experiences here.

Fingers crossed for GNS3 1.0 support as soon as possible!

--Christoffer

After several different attempts, I cannot get the image to boot in a VM on Windows.
I guess this is because the SR-OS image runs on SYSLINUX, and creates a VM where the SR-OS runs.
Guest-OS on Guest-OS, or nested virtualization is not possible on my laptop, and I dont have any pure linux systems available at the moment.

As soon as pure Linux environment is ready, the system SHALL boot

Good luck to all

I already try with KVM Linux, it is still stuck in booting...
it just shows up
" SYSLINUX 5.00 EDD 2012-12-06 Copyright (c) 1994-2012 ......"
"Booting.."

I suspect,I need a better processor feature and a better RAM.
btw I used 12R2 version,...I'll try for a newer one

Regards,
Agung Aryo

I got the same on Ubuntu with KVM.
Now I'm trying with CentOS 6.5 and Virtual Machine Manager.
I guess it runs KVM / QEMU somewhere in the lower layers, but here I'm stuck with "Disk image is not bootable"..

How did you attempt this with 12.0.R2?

Stuck, but haven't given up

--Christoffer

Regarding 12.0.R2 VM, i found it on ALU download pages as well..
Will try it also..

I managed to get CentOS to get to Booting stage.
When importing the image in VMM, you have to change disktype from RAW to qcow2 afterwards.

But still no cigar.. Its just... "booting"..

I had exactly the same experience, had to edit the vmx file or something as it defaults to raw versus qcow2. Doesn't really line up with 'we're releasing this as qcow2 for an easy installation' line.
Like everyone else I get stuck at boot stage.

It's not a RAM issue, I have an ESXi machine running 16GB and the recommendation is 8GB with 4GB per VM.

It's a shame the documentation is limited.

Tried with R2 and R3 as well with no luck.

Great news everyone!
I did it!

OK, so here is what I did.

I installed Virtual Machine Manager on CentOS 6.5
http://virt-manager.org/

I created a VM with the following settings:
Import existing disk image
Point it to the .qcow2 image
Memory 4096, CPUs 1
-Forward.
This will attempt to boot the image, but it will not boot.
Go to Virtual Machine details, and edit the following parameters:
Memory; ensure 512-4096 is available.
IDE Disk -> Advanced options: Storage format: qcow2

You can now start the VM.
It will try PXE boot before it stops with SYSLinux -> SROS VM -> Booting ...

It seems nothing happens.
Open a terminal.

[root@centos ~]# virsh list
Id Name State
----------------------------------------------------
19 SR120R4 running
21 TEST running


[root@centos ~]# virsh console TEST
Connected to domain TEST
Escape character is ^]

Login: admin
Password:

This simulation software is the property of Alcatel. It may not
be sold, leased, loaned or licensed to any non-Alcatel entity.
A:vRR#

On a other terminal:

[root@centos qemu]# virsh console SR120R4
Connected to domain SR120R4
Escape character is ^]

Login:
Login: admin
Password:

This simulation software is the property of Alcatel. It may not
be sold, leased, loaned or licensed to any non-Alcatel entity.
A:vRR#

[root@centos qemu]# virsh console SR120R4
Connected to domain SR120R4
Escape character is ^]

Login:
Login: admin
Password:

This simulation software is the property of Alcatel. It may not
be sold, leased, loaned or licensed to any non-Alcatel entity.
A:vRR#

[root@centos qemu]# virsh console SR120R4
Connected to domain SR120R4
Escape character is ^]

Login:
Login: admin
Password:

This simulation software is the property of Alcatel. It may not
be sold, leased, loaned or licensed to any non-Alcatel entity.
A:vRR#

Next step will be to try to get networking up as well.

Edit; Enable at least 2 CPU cores for the system.
It did complain about dual core software in single core setup, and no x64 with only one core.

It stopped nagging when I allocated 2 cores for the VM.

Eugh I'm not having a good time with this. Keeps suffering from a system crash before it gets to CLI prompt, just before when it references IPv4 DNS etc.

Interestingly my VMM doesn't allow me change raw to qcow2 in the GUI, I have to do it on linux CLI:

virsh -c qemu:///session dumpxml $your_vm_name$ > $your_vm_name$.xml
vi $your_vm_name$.xml
#edit the line that says
<driver name='qemu' type='raw' cache='none'/>
#and change it to
<driver name='qemu' type='qcow2' cache='none'/>
#If youre not a vi person use x to delete raw then press i to insert and type qcow2 then press esc followed by :wq and return (:q to leave without making changes)
#then do
virsh -c qemu:///session define $your_vm_name$.xml
#once done you can
virsh console $your_vm_name$