Hi Michael,
On Thu, Sep 05, 2013 at 09:40:38AM +0400, Michael Tokarev wrote:
> 03.09.2013 20:12, Toni Mueller wrote:
> >On Mon, Sep 02, 2013 at 08:50:11AM +0400, Michael Tokarev wrote:
> >restart the VM for the change to take effect. Then I restart the VM, log
> >in and then run rejoin-stack.sh,
03.09.2013 20:12, Toni Mueller wrote:
Hi Michael,
Hello!
On Mon, Sep 02, 2013 at 08:50:11AM +0400, Michael Tokarev wrote:
[]
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 th
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
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 amo
4 matches
Mail list logo