Control: retitle -1 VM becomes unresponsive - soft lockup, RCU stall Control: severity -1 important Control: reassign -1 src:linux Control: tag -1 moreinfo On Tue, 2014-12-09 at 14:53 +0000, Toni Mueller wrote: > severity 771661 grave > thanks Sorry, no, you've only seen one broken VM. Also, this is assigned to linux-image-3.16-0.bpo.3-686-pae but the screenshot you attached shows that package being newly installed. Therefore it is not the kernel you were running at the time you first saw this problem. Did you subsequently boot into that kernel? > Hi, > > I guess the same would apply to #771602, but I would like to not go > the extra five miles to reproduce it there. In any case, a kernel > that maxes out the CPU immediately after start while doing nothing > is not entirely production quality (although I have very good > experiences with it in other settings). > > I'd likely be happy to produce more evidence if you can give me > useful directions. We would need a more complete kernel log. You could use an emulated serial console to get this. How much memory does this VM have? Does it have a swap file? > Oh, as a side note: The VM thus maxed out cannot be shut down with > > $ virsh shutdown nameofvm > > but only with killing the kvm process. That's a graceful shutdown, which is expected to fail if the guest OS has become unresponsive. You should use the 'virsh destroy' command to forcefully shut down a VM. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less.
Attachment:
signature.asc
Description: This is a digitally signed message part