Bug#558792: [Pkg-libvirt-maintainers] Bug#558792: please undefine old guest after migration

2009-12-02 Thread Harald Dunkel
Guido Günther wrote: The guest should be powered off but still defined - that's the correct behaviour. Undefining the vm is out of question since you'd lose the configuration data then. I don't see this. The data has been migrated to the new host. What would we loose? IMHO having 2 virtual

Bug#558792: [Pkg-libvirt-maintainers] Bug#558792: please undefine old guest after migration

2009-12-01 Thread Harald Dunkel
Sorry, but I a not sure that I got you correctly. I just select the guest in the virt-manager gui, click on migrate, and select the new host. I do not know whats happening inside, but I have to assume that it is using libvirt. Do you think this is a problem of virt-manager? Regards Harri

Bug#558792: [Pkg-libvirt-maintainers] Bug#558792: please undefine old guest after migration

2009-12-01 Thread Guido Günther
On Tue, Dec 01, 2009 at 01:18:36PM +0100, Harald Dunkel wrote: Sorry, but I a not sure that I got you correctly. I just select the guest in the virt-manager gui, click on migrate, and select the new host. I do not know whats happening inside, but I have to assume that it is using libvirt.

Bug#558792: [Pkg-libvirt-maintainers] Bug#558792: please undefine old guest after migration

2009-11-30 Thread Guido Günther
On Mon, Nov 30, 2009 at 04:48:59PM +0100, Harald Dunkel wrote: Package: libvirt0 Version: 0.7.2-3 After the migration the guest is defined on both old and new host. Esp. when you are dealing with a large set of hosts there is a high risk that you activate both guests by accident,