I couldn't trivially reproduce this on Trusty, using cloud image 20140724 on amd64.
Steps I followed (from memory): sudo apt-get update sudo apt-get install -y libvirt-bin uvtool newgrp libvirtd uvt-simplestreams-libvirt sync release=trusty arch=amd64 uvt-kvm create foo virsh autostart foo sudo reboot After reboot, "virsh list" shows "foo" as running. (uvtool/uvt-* is just a wrapper to set up a libvirt domain quickly; it shouldn't affect this test) I wonder if there is some interaction with your bridge setup here, but /etc/init/libvirt-bin.conf only starts the libvirt-bin job on entering runlevel 2. Is the bridge guaranteed set up by this point? Dropping this to Medium, as it only appears to affect a non-default case. ** Changed in: libvirt (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350727 Title: Domains created and managed via libvirt/virsh fail to autostart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1350727/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
