|
This is the most simple example you can build using VNUML. It just starts one virtual machine named "host1" without any virtual network. It can be used to test and tune the kernel and root filesystem you plan to use in a simulation. The example has been updated from 1.3 to 1.6 thanks to Esteban Martín.It is always recomended to first test kernel and filesystems in your machine using a simple scenario like this before using them in more complex scenarios. That will save you a lot of time, allowing to detect and correct typical problems related to the virtual machines boot process.Once the simulation is started, you can access the virtual machine using several methods (see the [../../1.6/reference/index.html#vm_mgmt <vm_mgmt>] tag):
- Using the xterm console started by default (see line "<con0>xterm</con0>" in VNUML spec). In this case, the simulation has to be started from an X terminal. NOTE: if you are experiencing problems with the conventional xterm, we recommend you to uncomment the [../../1.6/reference/index.html#xterm <xterm>] tag in each virtual machine, in order to use gnome-terminal, that seems to be more stable. Of course, you will need the gnome-terminal installed in your system.
- Through a pseudo tty (pts) using "screen" application (or any other terminal emulation application). In this case you have to:
- change "xterm" by "pts"
- start the simulation using: "vnuml -t simple.xml -e screen.cfg"
- access the console using: "screen -c screen.cfg"
- Through the management interface using SSH. For example: "slogin 192.168.0.2" (if you add the [../../1.6/reference/index.html#host_mapping <host_mapping>] tag to global section you can use the virtual machine name: "slogin host1"). The first and second methods are recomended, because they allow you to see all log messages showed by the virtual machine when starting, as well as to access it even if the management interface has not been started correctly.You can download the simulation file from [simple.xml here].
|
