1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
%%$Id: running.tex,v 1.22 2009-03-02 16:15:15 potyra Exp $
% Copyright (C) 2003-2009 FAUmachine Team <info@faumachine.org>.
% This program is free software. You can redistribute it and/or modify it
% under the terms of the GNU General Public License, either version 2 of
% the License, or (at your option) any later version. See COPYING.
This chapter describes how to start and interact with your virtual
machines.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Using the Launcher}
\label{s:running.launcher}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
The easiest way to start virtual machines is by using the \launcher.
Execute \binlauncher to start it.
Once you have configured your virtual machines (for example by using
the \wizard, see chapter \ref{s:configwizard} "\cconfigwizard"),
you sit down in front of your machine (virtually of course) by selecting
\GUIMenu{VM/Start}.
A new window will pop up, representing the virtual machine.
It will be described in detail in the next section.
If your virtual machines need network connectivity to your real network,
you have to start a network bridge, too.
To do so, select \GUIMenu{Network/connect}.
The \launcher is able to configure both virtual machines and network bridges.
Use the corresponding \GUIMenu{edit} menu item to get a dialog
box with configuration options.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Starting a Virtual Machine}
\label{s:running.node}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
You can start a virtual machine by using the \launcher (see previous section),
or by executing \binnode in the directory of the virual machine you wish to
start.
If you call \binnode yourself, you can pass some options on the command line:
\begin{description}
\item[\option{-B \replaceable{dir}}]{
Change to this directory before starting the virtual machine.
This directory must contain all the configuration files needed
for this virtual machine.
}
\item[\option{-D \replaceable{\#}}]{
Set debuglevel to \replaceable{\#}. Only really useful for
\package developers.
}
\item[\option{-d}]{Same as \option{-D 1}.}
\item[\option{-e}]{
This option is only useful for the Automatic Experiment
Controller.
}
\item[\option{-h}]{Display short usage information.
}
\item[\option{-p}]{
Automatic power on at startup.
This is equivalent to pressing \GUIButton{On} immediately.
Especially useful with \option{-X}, as there is no other way to
power on the machine without the GUI.
}
\item[\option{-o}]{
Automatic termination of the faum-node-pc,
if the power led changes from on to off.
}
\item[\option{-t}]{
Map an incoming sigterm to the frontend to a CTRL-ALT-DEL
into the virtual system.
}
\item[\option{-r}]{
Reuse TCP-ports with \function{bind} in case you messed
up everything during the last run, to avoid waiting
for timeout before the ports become reusable.
Don't forget to kill all pending \binnode and \binlauncher
processes!
}
\end{description}
The following option is only available to you, if you are running a specially
patched FAUmachine kernel on your real machine (see section
\ref{s:installbinary.requirements.sw} in chapter \ref{s:installbinary}
"\cinstallbinary"):
\begin{description}
\item[\option{-E \replaceable{n}}]{
If you run FAUmachine with an accelerated kernel, the default is to
use all acceleration methods which are supported by the real kernel. If
you don't want that, use \option{0} to run without any acceleration,
\option{1} to run only with signal-handler acceleration and
\option{2} to run with signal-handler and mmap acceleration.
}
\end{description}
When you start a virtual machine, a new window is displayed showing the console of your
virtual machine (unless you use \option{-X}, of course).
This window consists of a small toolbar and the big console display.
The toolbar contains the power-on, power-off and reset buttons as well as a
button to exit the simulator. The console display shows the contents of the
virtual monitor.
In addition to powering on and off and resetting the machine, the menu
\GUIMenu{Machine} allows you to change the virtual CD.
The menu \GUIMenu{Screenshot} lets you take a screenshot, which will be saved in
the virtual machine's directory. You can use these screenshots to automize
graphical user interfaces with Expect as described in chapter
\ref{s:testautomation} "\ctestautomation".
The menu \GUIMenu{Inject} lets you
inject errors (see section \ref{s:injectingfaults.gui} in chapter
\ref{s:injectingfaults} "\cinjectingfaults" for details).
Click on \GUIButton{On} to power-on your virtual machine. You should see the
bootscreen of the \package BIOS. It tries to boot from the CD-ROM and hard
disk.
To install an operating system in your virtual machine, you have to insert your
Install-CD. Use \GUIMenu{Machine/Change CD/Browse} to select a CD-image (often
named *.iso) or just select \GUIMenu{Machine/Use host CDROM} and insert a real
CD-ROM into your real drive (\Filename{/dev/cdrom} will be used).
The virtual machine should now boot from that CD, allowing you to install the
operating system as you would do on a real machine.
{\bf Please note:} Currently only {\em RedHat 8.0/9}, {\em SuSE 8.1/8.2} and
{\em Debian 3.0r1/r2} are supported out of the box.
\notgb{%% Leave this here for DBench cross-compilation!
I.e. if you try to install another operating system/Linux distribution, the
\launcher will output an error message and the virtual machine will not boot.
However, you can make them work by compiling a modified version of their
bootloader and kernel. See chapter \ref{s:buildfromsource} "\cbuildfromsource"
for details.
}%\notgb
If you want to interact with the virtual machine, move your mouse pointer
over the console display and click or press any key.
Now your mouse and keyboard is redirected to the virtual machine.
To stop that redirection, press \GUIButton{Ctrl+Alt+ESC}.
Now all mouse and keyboard presses are back to normal again.
|
