I've been trying this out every time a new version of Ubuntu is coming up for release, and it has never worked! However, this is the most promising result that I have seen to date. Maverick version of virt-manager seems to be able to correctly save the running state to a file, however it prompts you for a save location. It does not default to the location down /var/lib/libvirt. However, there appears to be no way to restore the VM through virt-manager on maverick. Despite this, I could successfully restore via virsh as follows:
$ virsh restore debian.save In this case, the console springs to life inside virt-manager - with the VM in the running state that I saved. This is the behaviour I would expect to see. In terms of reproducibility, I have a Fedora and Debian guest. Neither are restorable on natty. They both simply start booting from scratch on restore. I am very encouraged by the how good things are looking on the virtualisation front on natty. As I was saying, this is the closest that I have come seeing this work seamlessly since libvirt and virt-manager were included. I suspect there is an issue with this particular version of libvirt. If I get some time I'll try rebuilding the 0.8.8 package with the 0.9.0 source and put it in my PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771227 Title: Domain save/restore does not work (kvm) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
