Serge, We'd have to go back a ways to get the logs you need. What kind of "oopses" did you have in mind?
I think most of it is explained above, i.e.: 1) An update to some component of libvirt and/or kvm was part of an update to the VM _host_. 2) Upon installing the update, the update process itself killed off the running kvm's (two of them). I watched it happen before my eyes. 3) The kvm's you see listed _were_ after I restarted them manually. They did not auto-restart after the update. My whole point in arguing that this is a serious "bug" is that messing with VM's is a whole new class of issue for updating server environments. It's one thing to have some update programs know how to stop/restart some process (such as a relatively time-insensitive SMTP server) but it's a whole 'nother thing when you take down a complete VM!!! The host simply cannot know what all the dependencies are on the running VM. Hence, this is _really_ important! I'll include the term.log and dpkg.log files from the relevant time window. If there is something else you need, I can uplink it. STK -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/767218 Title: Guest machines crashed during apt-get update/upgrade on Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
