LibVirt XML Format with annotations ----------------------------------- = --> one-0 ;) = --> type of operating system to be booted in the virtual machine. ** NOT SURE HOW TO CALL IT OR IF NEEDED VALUES: hvm (fully virtualized), linux (Xen 3 hypervisor guest ABI) ATTRIBUTES: arch (CPU arch), machine (machine type http://libvirt.org/formatcaps.html) = --> For fully virtualized xen (/usr/lib/xen/boot/hvmloader) ** NOT SURE HOW TO CALL IT = --> full path to kernel in HostOS = --> full path to initrd in HostOS = --> arguments for the kernel at boottime. ** Esto lo incluiría dentro de KERNEL como un atributo. = --> ATTRIBUTES: dev --> set the boot device sequence. Can be repeated --> ** NOT THAT SURE WE NEED THEM!! In sort: define the bootlader in HostOS used to select kernel in Guest OS = --> destroy|restart|preserve|rename-restart = = * --> Features of the hypervisor :: Put them as values of features * --> allows guest >4Gb RAM * --> allows KVM guest for graceful shutdown * = --> ATTRIBUTES: sync = {localtime, utc} --> Path to the emulator binary, depends on Driver. ** This ONE wee don't need. Freegle!!!. * --> ATTRIBUTES type = {file|block}, device={floppy,disk(default),cdrom} * --> For selecting different drivers for the disk if the hypervisor supports it. ATTRIBUTES: name (e.g. "tap"), type (e.g. "aio") * -->ATTRIBUTES: dev (if DISK type=block), file (if DISK type=file) * --> ATTRIBUTES: dev (e.g. hda-->doesn't promise a correct mapping, more like ordering for mapping), bus={ide,scsi,virtio,xen} * --> Can be there or no, no more and no less * * --> ATTRIBUTES: type={network,ethernet,bridge,user,mcast,server,client} see http://libvirt.org/formatdomain.html#elementsNICS * --> ATTRIBUTES: network (name of the source network), bridge (name of the source bridge), (address,port) when defining client,servers and multicast. * --> ATTRIBUTES: dev --> name for the GuestOS network device being defined here. * --> ATTRIBUTES: address (obvious, right?) *