[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2019-07-26 Thread Launchpad Bug Tracker
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1585533 Title:

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2019-05-27 Thread Marc Brothier
I'm not able to test that issue anymore, you can close the ticket. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1585533 Title: cache-miss-rate / Invalid JSON Status in QEMU: Incomplete Bug

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2019-05-27 Thread Thomas Huth
Is there still something to be done for upstream QEMU here? ... otherwise, I assume we can close this bug now? ** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2016-06-07 Thread Marc Brothier
Well, to make this work we updated the libvirt code to correct such invalid value and put a "0" in that case for the "cache-miss-rate" value. Can someone confirm that it putting a "0" is a valid choice, or shall we have something else? Thanks -- You received this bug notification because you

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2016-06-01 Thread Marc Brothier
I didn't look properly, it's the same error with the patch applied. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1585533 Title: cache-miss-rate / Invalid JSON Status in QEMU: New Bug

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2016-05-31 Thread Marc Brothier
We tried to migrate a VM, and now we have a new error: error : virNetClientProgramDispatchError:177 : internal error: info migration reply was missing return status :( -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2016-05-26 Thread Marc Brothier
We're using Ubuntu, and we manually patched the version 2.3 with the fix referenced. It will be soon deployed and I'll see if that fixes the problem. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2016-05-25 Thread Paolo Bonzini
Marc, what distro are you running on? QEMU 2.3 is not maintained anymore upstream, so unless you are running on Ubuntu (and then we can reuse this bug tracker) you'll have to reopen the bug in your distro. -- You received this bug notification because you are a member of qemu- devel-ml, which

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2016-05-25 Thread Marc Brothier
Also found a patch in qemu 2.4.0 (?) which fix a zero division: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg01173.html which might be the source of the problem. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2016-05-25 Thread Marc Brothier
Ok, then I'll reopen the bug with a request to fix JSON output in qemu. ** Changed in: qemu Status: Invalid => New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1585533 Title:

[Qemu-devel] [Bug 1585533] Re: cache-miss-rate / Invalid JSON

2016-05-25 Thread Marc Brothier
Sorry, the bug is in libvirt -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1585533 Title: cache-miss-rate / Invalid JSON Status in QEMU: Invalid Bug description: Hi, We have VMs which