On 02/29/2016 01:48 AM, Per Jessen wrote: > Olaf Hering wrote: > >> On Fri, Feb 26, Per Jessen wrote: >> >>> a xen domu is created from config-file on hostA, then migrated to >>> hostB. On hostB, a new disk is added with "xl block-attach", works >>> very well. However "xl list --long <domu>" doesn't reflect this >>> change. "xl config-update" seems to be a way to edit config files, >>> but once the domU has been migrated to hostB, the original file isn't >>> immediately available - what do I need to get the new block device >>> reflected in the config that goes with the domU ? >> I think that requires a newer libxl version which tracks the config in >> a separate JSON file. Until then the domU.cfg has to be adjusted along >> with the 'xl block-attach'. > Thanks Olaf, I suspected that too. > > Just wondering what other people do when you have multiple xen hosts and > you migrate domUs between them - do you keep the configs on NFS, shared > by all hosts?
If you don't mind another layer of tooling, you can use libvirt to manage your xen domains. It will take care of managing state/config for both transient and persistent domains. It will also transfer the current state when migrating the domain, optionally persisting the state/config on the target host when migration is invoked with the --persistent flag (virsh migrate ... --persistent). Regards, Jim -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
