I am also seeing this problem (or something very similar).
If I restore a saved VM from virsh, virt-manager still sees it as
shutdown. This happens even if the VM was saved via virt-manager.
I havn't tested this as root but I can repeat it over and over as a user
who has KVM and libvirt group membership.
aptitude show virt-manager
Package: virt-manager
New: yes
State: installed
Automatically installed: no
Version: 0.7.0-3ubuntu1
Priority: optional
Section: admin
Maintainer: Ubuntu Core Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Uncompressed Size: 4,379k
Depends: libatk1.0-0 (>= 1.20.0), libc6 (>= 2.2.5), libcairo2 (>= 1.2.4),
libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libglib2.0-0 (>=
2.16.0), libgtk2.0-0 (>= 2.17.0), libpango1.0-0 (>= 1.14.0),
libpython2.6
(>= 2.6), gconf2 (>= 2.10.1-2), python-gtk2, python-glade2aptitude
show libvirt-bin
Package: libvirt-bin
New: yes
State: installed
Automatically installed: no
Version: 0.7.0-1ubuntu13.1
Priority: optional
Section: devel
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Uncompressed Size: 1,393k
Depends: libapparmor1, libavahi-client3 (>= 0.6.16), libavahi-common3 (>=
0.6.16),
libc6 (>= 2.8), libdbus-1-3 (>= 1.1.1), libdevmapper1.02.1 (>=
2:1.02.20),
libgcrypt11 (>= 1.4.2), libgnutls26 (>= 2.7.14-0), libhal1 (>=
0.5.8.1),
libparted1.8-12 (>= 1.8.8.git.2009.06.03-1ubuntu5), libpolkit-dbus2 (>=
0.7), libpolkit2 (>= 0.7), libreadline5 (>= 5.2), libsasl2-2,
libselinux1
(>= 2.0.85), libtasn1-3 (>= 1.6-0), libuuid1 (>= 2.16-1), libvirt0 (=
0.7.0-1ubuntu13.1), libxen3, libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4),
adduser, logrotate, bridge-utils, dnsmasq-base, netcat-openbsd,
iptables
Recommends: kvm
Suggests: policykit, apparmor (>= 2.3+1289-0ubuntu14)
, python-gnome2,
python-dbus, python-urlgrabber, python-vte, librsvg2-common,
python-libvirt
(>= 0.4.6), python-virtinst (>= 0.400.1), python-gtk-vnc (>= 0.3.8)
Recommends: hal, libvirt-bin (>= 0.4.6)
Suggests: virt-viewer
aptitude show qemu-kvm
Package: qemu-kvm
New: yes
State: installed
Automatically installed: no
Version: 0.11.0-0ubuntu6.3
Priority: optional
Section: misc
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Uncompressed Size: 7,852k
Depends: libasound2 (> 1.0.18), libc6 (>= 2.10), libcurl3-gnutls (>= 7.16.2-1),
libgnutls26 (>= 2.7.14-0), libncurses5 (>= 5.6+20071006-3), libpci3,
libpulse0 (>= 0.9.19), libsdl1.2debian (>= 1.2.10-1), libx11-6, zlib1g
(>=
1:1.1.4), python, iproute, bridge-utils, adduser
Suggests: ubuntu-vm-builder, kvm-pxe, uml-utilities, qemu-kvm-extras
Conflicts: kvm (< 1:84+dfsg-0ubuntu16+0.11.0), kvm-data, qemu (<
0.11.0-0ubuntu5)
Breaks: udev (< 136-1)
Replaces: kvm (< 1:84+dfsg-0ubuntu16+0.11.0), kvm-data, qemu
Provides: kvm, qemu
I would say this is a pretty significant bug in virt-manager.
--
VM started with virsh but not marked started in virt-manager
https://bugs.launchpad.net/bugs/234938
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
