Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When attempting to close the guest window (using SPICE), the VM is being shutdown, when libvirt fails to parse JSON
Version-Release number of selected component (if applicable):
RHEVM Version ic114
spice-server-0.8.0-1.el6.x86_64
libvirt-client-0.8.7-16.el6.x86_64
libvirt-0.8.7-16.el6.x86_64
libvirt-python-0.8.7-16.el6.x86_64
qemu-kvm-0.12.1.2-2.158.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Open the guest SPICE window
2. Attempt to close that window (using X button in the right side of the screen)
Actual results:
VM is being shut down, getting an ERROR message on WPF GUI:
"VM is down. Exit message lost connection with kvm process."
libvirtd.logs:
": "55292", "family": "ipv4", "host": "10.35.70.3"}}}]
12:14:09.078: 31122: debug : virJSONValueFromString:933 : string={"timestamp": {"seconds": 1303118049, "microseconds":
78667}, "event": "SPI{"timestamp": {"seconds": 1303118049, "microseconds": 78667}, "event": "__com.redhat_SPICEt": "5
5292", "family": "ipv4", "host": "10.35.70.3"}}}
Expected results:
VM Should stay in UP state
Additional info:
** Please see attached libvirtd.log
** Please see attached VDSM.log
(In reply to comment #4)
> The bug was created twice.
> Closing the bug.
>
> *** This bug has been marked as a duplicate of bug 497441 ***
just kindly reminder,should be duplicate of bug 697441
[Bug 697441] QEMU-KVM - VM is being shutdown when closing SPICE window
*** This bug has been marked as a duplicate of bug 697441 ***
Description of problem: When attempting to close the guest window (using SPICE), the VM is being shutdown, when libvirt fails to parse JSON Version-Release number of selected component (if applicable): RHEVM Version ic114 spice-server-0.8.0-1.el6.x86_64 libvirt-client-0.8.7-16.el6.x86_64 libvirt-0.8.7-16.el6.x86_64 libvirt-python-0.8.7-16.el6.x86_64 qemu-kvm-0.12.1.2-2.158.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Open the guest SPICE window 2. Attempt to close that window (using X button in the right side of the screen) Actual results: VM is being shut down, getting an ERROR message on WPF GUI: "VM is down. Exit message lost connection with kvm process." libvirtd.logs: ": "55292", "family": "ipv4", "host": "10.35.70.3"}}}] 12:14:09.078: 31122: debug : virJSONValueFromString:933 : string={"timestamp": {"seconds": 1303118049, "microseconds": 78667}, "event": "SPI{"timestamp": {"seconds": 1303118049, "microseconds": 78667}, "event": "__com.redhat_SPICEt": "5 5292", "family": "ipv4", "host": "10.35.70.3"}}} Expected results: VM Should stay in UP state Additional info: ** Please see attached libvirtd.log ** Please see attached VDSM.log