[opensuse-virtual] how to update the config for a xen domu
Assume something along these lines - 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 ? -- Per Jessen, Zürich (2.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
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'. Olaf -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
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? -- Per Jessen, Zürich (3.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
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: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Am 29.02.2016 um 09:48 schrieb Per Jessen <per@opensuse.org>:
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?
Yes, exactly that. Norman -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
participants (4)
-
Jim Fehlig -
Olaf Hering -
Per Jessen -
Rieß Norman