Be able to edit configuration of running VM (to be applied next reboot/shutdown)

[blop]

Feature request ;-)

It would be nice to be able to edit the configuration of a running vm, and schedule it to be applied at next reboot or shutdown.

It should show the current running configuration (read only) like now,
plus another tab/link to a "scheduled" configuration that we could edit/reedit or even revert to the original running one.

[johann8384]

This would be a great feature, I haven't spent a lot of time in this code yet but does anyone have a suggestion about how this might be done? What are the roadblocks to implementing something like this?

[Nowaker]

@johann8384 I just investigated this thing for you and I figured out that these libvirt API calls are likely to do the thing:

virDomainGetXMLDesc

Provide an XML description of the domain. The description may be reused later to relaunch the domain with virDomainCreateXML().

(...) If @flags includes VIR_DOMAIN_XML_INACTIVE, then the XML represents the configuration that will be used on the next boot of a persistent domain; otherwise, the configuration represents the currently running domain.`

So by this switch you are able to fetch current and to-be-applied configuration.

virDomainDefineXML

Hope this helps you getting this crucial feature done. Thanks.

[Nowaker]

@CyrilPeponnet @primalmotion Any chances to get this feature #accepted? This is quite essential, I'd say.

[CyrilPeponnet]

If it's still open that mean it's pending :) We have to check the
consequences on both agent and UI. A lot of features are essential too. For
the record with some hypervisors you can't change the config while the vm
is running.

Le 2 nov. 2013 à 22:38, Damian Nowak notifications@github.com a écrit :

@CyrilPeponnet https://github.com/CyrilPeponnet
@primalmotionhttps://github.com/primalmotionAny chances to get this
feature #accepted? This is quite essential, I'd say.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/238#issuecomment-27633192
.

[Nowaker]

Funny thing: because my Archipel-handled production environment grows, ejabberd started taking more resources. I just wanted to increase number of CPUs and memory for this VM but realized that Archipel can't do that while VM is running. And Archipel won't work when the VM is off, as ejabberd will be down. ;-)