Thanks for the prompt reply. I create the VMs in virt-manager by pointing to previous images (raw, qcow2 -- both work) I have on my disk --all works as expected.
The VMs are consistent acrosss different "virt-manager" sessions i.e. if I exit then re-enter virt-manager VM is still there (but w/o rebooting) Creation and deletion of VMs in virt-manager (tested as above) works fine. It's just that across reboots the only thing I have left ( is an "orphaned" XML file of the (old) VM in "/etc/libvirt/qemu" directory. virt-manager doesn't show the VM, nor "virsh list --all" finds it. In the mean time I find a (temporary work around) that seems to work across reboots: 1) Create "VM" as above 2) Copy the "VM.xml" definition to another file e.g "VM-new.xml" 3) Edit "VM-new.xml" and change <name>VM</name> to <name>VM-new</name> 4) virsh define VM-new.xml (outputs an innocent error message wrt the domain) After that, the "VM-new" is persistent across reboots, but shown with the old name (i.e. "VM") in virt-manager,. Also, if I try in virsh to do virsh define OprhanedVM.xml (for an "OrphanedVM" -- VM orphaned as per above sequence), I get: error: Failed to define domain from OrphanedVM.xml error: (domain_definition):4: Comment not terminated <!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES virsh edit OrphanedVM.qcow2 -------------------------^ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999681 Title: Afer upgrading "libvirt-bin" to 0.9.8-2ubuntu17.1 to virsh cannot identify machine after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/999681/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
