Bryan Kearney wrote: >> Actually the nature of the virt-image format is that you shouldn't >> need to do any xml surgery, it is (ideally) completely portable. Specific >> things like memory amounts and mac addresses are specified at the time >> virt-image is called: see virt-image --help for all the goodies that >> can be specified. >> tools > But ideally, the initial virt image xml would contain the memory and cpu > settings from the source system.. since that is as close to a template > as we have. > > -- bk > Oh, yes that's true. I forgot that mem and vcpu recommendations can be in the image xml. Thankfully though the virt-image removes any need to manually alter xml. - Cole _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
