Bug 1614959 - Jansson can not always parse QEMU's JSON: failed to parse JSON: too big integer near '18446744073709551615'
Summary: Jansson can not always parse QEMU's JSON: failed to parse JSON: too big inte...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-10 20:53 UTC by Mikhail
Modified: 2018-09-27 10:49 UTC (History)
11 users (show)

Fixed In Version: libvirt-4.7.0-1.fc29
Clone Of:
Environment:
Last Closed: 2018-09-27 10:49:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
screenshot (59.75 KB, image/png)
2018-08-10 20:53 UTC, Mikhail 		no flags Details
dmesg (133.96 KB, text/plain)
2018-08-10 21:12 UTC, Mikhail 		no flags Details
View All

Description Mikhail 2018-08-10 20:53:27 UTC 
Created attachment 1475160 [details]
screenshot

Description of problem:
When I tries connected to graphical console I get error message:
Error connecting to graphical console:
internal error: failed to parse JSON 1:63: too big integer near '18446744073709551615'

Version-Release number of selected component (if applicable):
# rpm -q virt-manager
virt-manager-1.6.0-0.3.git3bc7ff24c.fc29.noarch
Comment 1 Mikhail 2018-08-10 21:12:13 UTC 
Created attachment 1475161 [details]
dmesg
Comment 2 Cole Robinson 2018-08-11 17:39:02 UTC 
This is due to libvirt's switch from yajl to jansson. There's an upstream bug tracking it. Only option in the meantime is to downgrade libvirt*

https://bugzilla.redhat.com/show_bug.cgi?id=1614569
Comment 3 Jan Kurik 2018-08-14 08:37:09 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
Comment 4 Pavel Hrdina 2018-09-27 10:49:43 UTC 
The latest build libvirt-4.7.0-1.fc29 should fix the issue, the jansson switch was reverted.
Note You need to log in before you can comment on or make changes to this bug.