Public bug reported:
Hi all,
First a bit of disclaimer. I'm a bit of newcomer to libvirt-bin / qemu
etc. so appologies if this is not as crisp / clear as it may need to.
TIA for your patience.
My problem: I normally use "virt-manager" to manage my VMs. After
installing Ubuntu 12.04 and performing the suggested upgrade of
"libvirt-bin" to version "0.9.8-2ubuntu17.1" I just discovered the
VMs "disappear" after a reboot. "virt-manager" is at version
0.9.1-1ubuntu5
The connection in virt-manager / URI in virsh is "qemu:///system"
After further investigation it seems that the XML file for the VM is
indeed still present in "/etc/libvirt/qemu" but a "virsh list --all"
does not identify the machine.
All processes are run as roon. Not exactly sure how/why that VM
definition is lost during a reboot. Cannot say what the behavior was
prior to upgrading "libvirt-bin" i.e. in vanilla 12.04
Thanks,
Florian
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
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
