Getting images

The images from INRIA can be downloaded from https://transfert.inria.fr.

KVM

KVM: Get virtual machine images

Links for downloading 2.1 XOS images, their checksums and their virsh configuration files:

• Core node
• Core node image checksum: MD5(xos-core.img)= bf3b90440229bee1d98829b80f08467c
• Core node configuration

• Resource node1 image
• Resource node1 image checksum: MD5(xos-node1.img)= 81cc3078ab2d3670484dc6afc95544c9
• Resource node1 configuration

• Resource node2 image
• Resource node2 image checksum: MD5(xos-node2.img)= d4734d62cadae3ce3b1dbb547db65b07
• Resource node2 configuration

• Resource node3 image
• Resource node3 image checksum: MD5(xos-node3.img)= 939e5880973d42f11aeb3ab242c4c09f
• Resource node3 configuration

The first 3 images have been built using 2.1 iso and xos-node3 using 2.1.1 iso.
The image files are of type qcow2 (using raw format ends with file-system corruption on my Ubuntu 9.10).
You need to install at least the xos-core image as it supports all core services of XtreemOS.

KVM: Configure the network

For these images, the default KVM network is configured as follow (file /var/lib/libvirt/network/default.xml on my ubuntu):



Using this configuration, KVM provides IP addresses and network configuration through DHCP. KVM also forwards access to DNS through the guest, extended with the guest /etc/hosts file.
So, you should add the following lines to the guest /etc/hosts file.

KVM: Extract the images

Extract the images (it will take about 10min):



Beware that the decompressed img files can be quite big (10+GB). However, these files are sparse so you can save lots of disk space using the following commands instead:

KVM: Configure the virtual machines

Then edit xos-core.xml and xos-node1.xml: provide correct pathname for xos-core.img and xos-node1.img.
You must enter the image localizations in their XML files — in the <disk> tag. For example, by replacing this path /VM/xos-node1.img' by the right path.

KVM: Start the core node

The following command should start the core node.



Alternative:



Please check the virsh documentations if necessary. Note that it also possible to manage virtual machines using the virt-manager GUI.

KVM: Preconfigured users

Unix accounts: yvon and root

• All passwords are xtreemos

KVM: Log in the xos-core

As you have already started the xos-core, you can log in through a normal (non virtual) terminal as follows. Remember that yvon's password is xtreemos.



You can also use the core node host name if it has been entered in the guest /etc/hosts file.



Same procedures for other nodes. Note that the configuration of the VMs does not allow root to connect directly on the nodes using a password: the ssh key is mandatory. If you want to allow ditect connection for root, you should first transfer your ssh public key with scp using account yvon, connect as yvon, become root using su and install your ssh public key in /root/.ssh/authorized_keys2.

KVM: Re-configuration of nodes

These virtual machine are already configured using the xosautoconfig tool. However, if you modify some configuration parameters, the node IP addresses for instance, it is necessary to report these modifications XtreemOS configuration files. In the general case, running command xosautoconfig as root should automatically update these files. If you want to change the hostname and/or IP, you can either edit the /var/lib/libvirt/network/default.xml and /etc/hosts of the guest or provide a /etc/hosts file on all hosts. If you install this file in /etc/xos/xosautoconfig/conf/etc/hosts, xosautoconfig will automatically replicate it in /etc/hosts.

KVM: Problem with expired user certificate

The virtual machines come with already installed service and user certificates. As the validy of user certificates is 1 month by default, those installed in the images might be obsolete. If you have one of the following errors when you run xps, you need to regenerate the user certificate.





Use the following request to renew the certificate:



(note that it seems necessary to provide the -k option to get-xos-cert also no new key is generated)

VitrualBox

The VirtualBox? VM's were created on VirtualBox? 3.1.4 and 3.1.6. It is our experience the VirtualBox? packages on recent Ubuntu are problematic and installing the latest packages provided at http://virtualbox.org are more reliable.

The images can be downloaded as follows:
https://transfert.inria.fr/fichiers/d300fdfd52056772b6adee3a8b224fe5/2.1core-32bit.7z

https://transfert.inria.fr/fichiers/4ae6c65ef8533d12d7de2b978f43a789/2.1.1.64core.7z

https://transfert.inria.fr/fichiers/0ab1628fbe1e9a925bbac369d9c70962/2.1.1.64resource.7z

SHA1SUMS


To minimize download time, I have compressed them with lzma compression, so to
extract you need 7zip, which can be downloaded from: http://www.7-zip.org/
Tools exist for almost every platform. If you use a Debian-based distibution, those should be the packages to install:

Installation

Under VirtualBox?

Once Imported, I recommend giving the VM 512Mb or more of ram for the resource
node and 768Mb of ram for the coreservices node.

VirtualBox? may fail to run the image if hardware virtualization (VT-x/AMD-V under system/acceleration) is not selected.
On some systems VT-x/AMD-V also has to be enabled in the BIOS for it to work.

Configuration

The core node can be used alone: it is also a resource node.
For the resource node installation, use the same procedure.

32 Bit Machines

The network configuration of the images are static and use private IP addresses:
192.168.56.101 coredemo.xtreemos.eu
192.168.56.102 demonode1.xtreemos.eu

64 Bit Machines

192.168.56.102 xos-core.xtreemos.eu
192.168.56.103 xos-node1.xtreemos.eu

These nodes are configured using host only networking, thus if you need to access the internet, it is best to enable eth1 (the second network card) in VirtualBox?, run the internet tasks and then ifdown eth1, before running XtreemOS jobs.

If you change the networking to NAT VirtualBox? will automatically assign 10.0.0.x to VMs, so you may need to change IP's within the configuration if running more than one node.

Known problems

Sometime, it seems that the dixi of the resource node is not connected to the core node. grep ERR /var/log/xosd/xosd to check that everything is OK. If not, restart xosd.

Preconfigured users

Unix accounts: xtreemos and xuser

• All passwords are xtreemos

Note: Installing virsh

Let's use the virsh to help us when managing images. To install virsh in Debian-based distributions, you should just install the libvirt-bin package. As follows, we do it by using aptitude:

Configuring virsh (libvirt)

In our case, we use NAT forwarding (aka virtual networks). So follow this page .

If you have a problem as the following one:



...sttoping dnsmasq should solve it:




Now, let's run the virsh terminal:



So, you can play with virsh commands. For example, listing the virtual machines:

Support

Do not hesitate to join us on IRC #xtreemos-dev on irc.freenode.net if you
need help.


Good luck.