Hi Michael, On Mon, Sep 02, 2013 at 08:50:11AM +0400, Michael Tokarev wrote: > Control: tag -1 + moreinfo > > 26.08.2013 05:56, Toni Mueller wrote: > >Package: qemu-kvm > >Version: 1.1.2+dfsg-6 > >Severity: normal > > > >Dear Maintainer, > > > >I found that I am able to provoke a "cpu lockup" in the guest, while the > >process on the host consumes 100% cpu. If I restore the memory to the > >original amount, the VM does not lock up. In my case, I originally used > >1550 MB of RAM, then tried 1024 MB of RAM. > > > >How to reproduce: > > > > * create a VM with X amount of memory > > * install devstack > > * shut the VM down > > * resize memory, so that the new amount of memory is less > > * restart the VM > > * restart devstack (./rejoin-stack.sh) > > Hmm. Are you saying that the lockup happens when you _restart_ > the VM with the new settings, instead of changing the amount of > memory dynamically?
when I change the amount of memory, I get a message that I need to restart the VM for the change to take effect. Then I restart the VM, log in and then run rejoin-stack.sh, and then the problem happens. > Also, you haven't provided any details about the VM you're using. The VM has originally 1550MB of RAM, usese virtio for disk and networking, and has some 50GB of disk space (mostly empty). > And, is devstack the one on devstack.org? Yes. > And one more thing: how this relates to #720633 you filed 2 days > before this bug? I have closed that bug on August 26th, as it somehow missed the actual error description. I don't quite know how this happened, but that bug report was certainly a user error on my behalf - maybe I was too tired, or something, and it was, at that moment, much easier to file a new report, than to amend the other. Otherwise, this is the same problem. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
