[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Tuning of exported VM template files (XCP 1.1)
Hello,How can I modify exported VM template (s. attachment) to fit particular requirements? I would like to install them again after modifications for creating of new VMs. Exported VM templates are binary files (kind of DB). Are there any tools to edit such VM template files? I have to use xe CLI / Linux tools (can't use XenCenter). Another possibility would be to export a template from already modified installed VM. How? I didn't find any useful information in docs or on the net about this topic. Thank you in advance for any hints. regards, Mark -- ms@xxxxxxxxxxxxxxxxxxxxxx ps. Example of VM structure # --- [root@xcp11db02 ~]# xe vm-list name-label=ubuntu11dbrt20 params= uuid ( RO) : 4133031a-e064-38e7-416d-72e1eb0a9118 name-label ( RW): ubuntu11dbrt20 name-description ( RW): Installed via xe CLI user-version ( RW): 1 is-a-template ( RW): false is-a-snapshot ( RO): false snapshot-of ( RO):<not in database> snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): 7c3081c0-5d69-5d9b-3c41-c162ded416ee children ( RO): is-control-domain ( RO): false power-state ( RO): running memory-actual ( RO): 8589848576 memory-target ( RO):<expensive field> memory-overhead ( RO): 77594624 memory-static-max ( RW): 8589934592 memory-dynamic-max ( RW): 8589934592 memory-dynamic-min ( RW): 2147483648 memory-static-min ( RW): 134217728 suspend-VDI-uuid ( RO):<not in database> VCPUs-params (MRW): VCPUs-max ( RW): 8 VCPUs-at-startup ( RW): 4 actions-after-shutdown ( RW): Destroy actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): bd4b277b-6941-7111-7b24-6579ada555ca platform (MRW): timeoffset: 0; nx: false; acpi: true; apic: true; pae: true; viridian: true allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_shutdown; pause; snapshot current-operations (SRO): blocked-operations (MRW): allowed-VBD-devices (SRO):<expensive field> allowed-VIF-devices (SRO):<expensive field> possible-hosts ( RO):<expensive field> HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): order: dc HVM-shadow-multiplier ( RW): 1.000 PV-kernel ( RW): PV-ramdisk ( RW): PV-args ( RW): PV-legacy-args ( RW): PV-bootloader ( RW): PV-bootloader-args ( RW): last-boot-CPU-flags ( RO): last-boot-record ( RO):<expensive field> resident-on ( RO): 280e2816-2d45-4217-881e-e2ad4b423159 affinity ( RW):<not in database> other-config (MRW): last_shutdown_time: 20111025T18:32:09Z; last_shutdown_action: Restart; last_shutdown_initiator: external; last_shutdown_reason: rebooted; mac_seed: a507ca72-1a89-e83d-a1b1-1ee749e6088f; install-methods: cdrom dom-id ( RO): 6 recommendations ( RO):<restrictions><restriction field="memory-static-max" max="34359738368" /><restriction field="vcpus-max" max="8" /><restriction property="number-of-vbds" max="7" /><restriction property="number-of-vifs" max="7" /></restrictions> xenstore-data (MRW): ha-always-run ( RW): false ha-restart-priority ( RW): blobs ( RO): start-time ( RO): 20111025T18:32:29Z install-time ( RO): 20111024T17:22:55Z VCPUs-number ( RO): 4 VCPUs-utilisation (MRO):<expensive field> os-version (MRO):<not in database> PV-drivers-version (MRO):<not in database> PV-drivers-up-to-date ( RO):<not in database> memory (MRO):<not in database> disks (MRO):<not in database> networks (MRO):<not in database> other (MRO):<not in database> live ( RO):<not in database> guest-metrics-last-updated ( RO):<not in database> cooperative ( RO):<expensive field> protection-policy ( RW):<not in database> is-snapshot-from-vmpp ( RO): false tags (SRW): Attachment:
Other-linux-template _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |