Q:By 'one timer', do you mean it has only happened one time? A:Yes, until now.
Q:A that level it could just as well be a bug in the guest kernel, or guest upstart, or some upstart job which never finished on shutdown. A:Agree, but not easy to decide. Q:I currently have a job running where an upstart job in guest does "some stuff" then shutdown -h, while the host constantly re-starts the guest. It has not failed to shutdown yet. A:That makes hope that this is not wide spread. Q:If you are at liberty to play with that host and guest, could you add an upstart job to the guest which starts on runlevel [2345] and does shutdown -h now, and then on the host start the guest (through virsh start) in a loop, waiting for it to shutdown, and print a message if the guest has not shtu down after a 5 minute timeout? If you are at liberty to do so, I can write up the scripts to use if you like. A:Properly not. But may be in the next week. Do not know if I come to this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981658 Title: ubuntu12.04 guest kernel 3.2.14 ubuntu flavour is not able to shotdown succesfully To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/981658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
