]>
Commit | Line | Data |
---|---|---|
1e3baf05 DM |
1 | #!/usr/bin/perl -w |
2 | ||
3 | package main; | |
4 | ||
5 | use strict; | |
6 | use PVE::Tools; | |
7 | use PVE::Cluster; | |
8 | use PVE::PodParser; | |
9 | use PVE::QemuServer; | |
10 | ||
11 | my $prop = PVE::QemuServer::json_config_properties(); | |
12 | my $format = PVE::PodParser::dump_properties($prop); | |
13 | ||
14 | my $parser = PVE::PodParser->new(); | |
15 | $parser->{include}->{format} = $format; | |
16 | $parser->parse_from_file($0); | |
17 | ||
18 | exit 0; | |
19 | ||
20 | __END__ | |
21 | ||
22 | =head1 NAME | |
23 | ||
24 | vm.conf - Proxmox VE virtual machine (qemu/kvm) configuration files. | |
25 | ||
26 | =head1 SYNOPSYS | |
27 | ||
28 | The F</etc/pve/qemu-server/C<VMID>.conf> files stores VM | |
29 | configuration, where C<VMID> is the numeric ID of the given VM. Note | |
30 | that C<VMID <= 100> are reserved for internal purposes. | |
31 | ||
32 | =head1 FILE FORMAT | |
33 | ||
34 | Configuration file use a simple colon separated key/value format. Each | |
35 | line has the following format: | |
36 | ||
37 | OPTION: value | |
38 | ||
39 | Blank lines in the file are ignored, and lines starting with a C<#> | |
40 | character are treated as comments and are also ignored. | |
41 | ||
42 | One can use the F<qm> command to generate and modify those files. | |
43 | ||
44 | =head1 OPTIONS | |
45 | ||
46 | =include format | |
47 | ||
48 | =include pve_copyright |