|
1
|
LibVirt XML Format with annotations
|
|
2
|
-----------------------------------
|
|
3
|
|
|
4
|
<domain>
|
|
5
|
=<name></name> --> one-0 ;)
|
|
6
|
<os>
|
|
7
|
= <type></type> --> type of operating system to be booted in the virtual machine. ** NOT SURE HOW TO CALL IT OR IF NEEDED
|
|
8
|
VALUES: hvm (fully virtualized), linux (Xen 3 hypervisor guest ABI)
|
|
9
|
ATTRIBUTES: arch (CPU arch), machine (machine type http://libvirt.org/formatcaps.html)
|
|
10
|
= <loader></loader> --> For fully virtualized xen (/usr/lib/xen/boot/hvmloader) ** NOT SURE HOW TO CALL IT
|
|
11
|
= <kernel></kernel> --> full path to kernel in HostOS
|
|
12
|
= <initrd></initrd> --> full path to initrd in HostOS
|
|
13
|
= <cmdline></cmdline> --> arguments for the kernel at boottime. ** Esto lo incluiría dentro de KERNEL como un atributo.
|
|
14
|
= <boot/> --> ATTRIBUTES: dev --> set the boot device sequence. Can be repeated
|
|
15
|
</os>
|
|
16
|
|
|
17
|
<bootloader></bootloader> --> ** NOT THAT SURE WE NEED THEM!!
|
|
18
|
<bootloader_args></bootloader_args> In sort: define the bootlader in HostOS used to select kernel in Guest OS
|
|
19
|
|
|
20
|
= <on_poweroff></on_poweroff> --> destroy|restart|preserve|rename-restart
|
|
21
|
= <on_reboot></on_reboot>
|
|
22
|
= <on_crash></on_crash>
|
|
23
|
|
|
24
|
* <features> --> Features of the hypervisor :: Put them as values of features
|
|
25
|
* <pae/> --> allows guest >4Gb RAM
|
|
26
|
* <acpi/> --> allows KVM guest for graceful shutdown
|
|
27
|
* </features>
|
|
28
|
|
|
29
|
= <clock/> --> ATTRIBUTES: sync = {localtime, utc}
|
|
30
|
|
|
31
|
<devices>
|
|
32
|
<emulator></emulator> --> Path to the emulator binary, depends on Driver. ** This ONE wee don't need. Freegle!!!.
|
|
33
|
* <disk> --> ATTRIBUTES type = {file|block}, device={floppy,disk(default),cdrom}
|
|
34
|
* <driver/> --> For selecting different drivers for the disk if the hypervisor supports it. ATTRIBUTES: name (e.g. "tap"), type (e.g. "aio")
|
|
35
|
* <source/> -->ATTRIBUTES: dev (if DISK type=block), file (if DISK type=file)
|
|
36
|
* <target/> --> ATTRIBUTES: dev (e.g. hda-->doesn't promise a correct mapping, more like ordering for mapping), bus={ide,scsi,virtio,xen}
|
|
37
|
* <readonly/> --> Can be there or no, no more and no less
|
|
38
|
* </disk>
|
|
39
|
|
|
40
|
* <interface> --> ATTRIBUTES: type={network,ethernet,bridge,user,mcast,server,client} see http://libvirt.org/formatdomain.html#elementsNICS
|
|
41
|
* <source/> --> ATTRIBUTES: network (name of the source network), bridge (name of the source bridge), (address,port) when defining client,servers and multicast.
|
|
42
|
* <target/> --> ATTRIBUTES: dev --> name for the GuestOS network device being defined here.
|
|
43
|
* <mac/> --> ATTRIBUTES: address (obvious, right?)
|
|
44
|
* <script/> --> ATTRIBUTES: path --> path-to-script to set network in HostOS
|
|
45
|
* </interface>
|
|
46
|
|
|
47
|
= <input/> --> Input for graphical iface. ATTRIBUTES: type={mouse,tablet} bus={xen,ps2,usb}
|
|
48
|
|
|
49
|
= <graphics/> --> ATTRIBUTES: type={sdl,vnc}, port='XXXX', listen='IP-to-listen-on', password='for-VNC-server'
|
|
50
|
|
|
51
|
<!-- Paravirtualized consoles, serial ports and parallel ports are all classed as character devices and so represented using the same syntax. -->
|
|
52
|
|
|
53
|
* <parallel> --> Parallel port ATTRIBUTES=type={stdio, file, vc, null,udp} ** NOT SURE, could (probably) be the same list as serial
|
|
54
|
* <source/> --> ATTRIBUTES path to HostOS parallel port
|
|
55
|
* <target/> --> 0, 1 or 2 parallel devices. ATTRIBUTES port='0' parallel port number in the GuestOS
|
|
56
|
* </parallel>
|
|
57
|
|
|
58
|
* <serial> --> Serial port ATTRIBUTES type={stdio (This disables all input on the character device, and sends output into the virtual machine's logfile), file (all data sent to file), vc (send to graphical virtual console Ctrl+Alt+3), null (all data is discarded), pty (source=/dev/pts/3, target_port=1), dev (The character device is passed through to the underlying physical character device. The device types must match, eg the emulated serial port should only be connected to a host serial port - dont connect a serial port to a parallel port.), tcp, udp, unix (The character device acts as a UNIX domain socket server, accepting connections from local clients. )}
|
|
59
|
* <source/> --> ATTRIBUTES path to HostOS serial port, or log file, .... When serial_type=tcp,udp --> mode={bind,connect} host='IP' service="port number".
|
|
60
|
* <target/> --> 0, 1 or 2 serial devices. ATTRIBUTES port='0' serial port number in the GuestOS
|
|
61
|
* <wiremode/> --> When serial_type=tcp,udp. ATTRIBUTES type='telnet'
|
|
62
|
* </serial>
|
|
63
|
|
|
64
|
* <console> --> Represents the primary console. This can be the paravirtualized console with Xen guests, or duplicates the primary serial port for fully virtualized guests without a paravirtualized console. ATTRIBUTES type={stdio, file, vc, null} ** NOT SURE, could (probably) be the same list as serial
|
|
65
|
* <target/> --> There is usually only one console device. ATTRIBUTES port='0' parallel port number in the GuestOS
|
|
66
|
* </console>
|
|
67
|
</devices>
|
|
68
|
</domain>
|
|
69
|
|
|
70
|
|
|
71
|
|
|
72
|
|
|
73
|
|
|
74
|
|
|
75
|
|
|
76
|
|
|
77
|
|
|
78
|
|
|
79
|
|
|
80
|
|
|
81
|
|
|
82
|
|