| Line 14... |
Line 14... |
| 14 |
virsh start domainname # virsh way
|
14 |
virsh start domainname # virsh way
|
| 15 |
havirt domain start domainname nodename
|
15 |
havirt domain start domainname nodename
|
| 16 |
|
16 |
|
| 17 |
These will both start domainname. The virsh command will start it on the
|
17 |
These will both start domainname. The virsh command will start it on the
|
| 18 |
node you are currently logged into. The havirt command will first verify
|
18 |
node you are currently logged into. The havirt command will first verify
|
| 19 |
domainname is not running on any node, then start it on nodename (or the
|
19 |
domainname is not running on any node, verify the target node has enough
|
| 20 |
current node, if nodename not specified) and modify it's state file to
|
20 |
resources, then start it on nodename (or the current node, if nodename not
|
| 21 |
reflect the status change.
|
21 |
specified) and modify it's state file to reflect the status change.
|
| 22 |
|
22 |
|
| 23 |
The other difference is that the virsh command uses the configuration
|
23 |
The other difference is that the virsh command uses the configuration
|
| 24 |
domainname.xml stored in /etc/virtlib/qemu, while havirt does a 'virsh
|
24 |
domainname.xml stored in /etc/virtlib/qemu, while havirt does a 'virsh
|
| 25 |
create' using the domainname.xml stored in installdir/conf.
|
25 |
create' using the domainname.xml stored in installdir/conf.
|
| 26 |
|
26 |
|
| Line 29... |
Line 29... |
| 29 |
|
29 |
|
| 30 |
havirt creates two subdirectories, installdir/conf/ and installdir/var/ if
|
30 |
havirt creates two subdirectories, installdir/conf/ and installdir/var/ if
|
| 31 |
they don't exist. conf/ stores the xml configuration of all domains, while
|
31 |
they don't exist. conf/ stores the xml configuration of all domains, while
|
| 32 |
var/ stores the state file (yaml) and some temporary files.
|
32 |
var/ stores the state file (yaml) and some temporary files.
|
| 33 |
|
33 |
|
| 34 |
|
- |
|
| - |
|
34 |
havirt also creates a configuration file (config.yaml) in the executables
|
| - |
|
35 |
directory. This allows you to modify the default behaviour of the program
|
| - |
|
36 |
more easily. See config.sample.yaml if you want to manually create it,
|
| - |
|
37 |
or for documentation on what can be modified.
|