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:
watching libvirt log, I see lots of messaged like the following:
3:22:29.840: info : qemudDispatchSignalEvent:397 : Received unexpected signal
it appears after I open vnc connection to the guest machine, or, start new guest.
when I start new guest, I see it printed 4 times:
13:26:07.045: info : qemudDispatchSignalEvent:397 : Received unexpected signal 17 │
Au│13:26:07.146: info : qemudDispatchSignalEvent:397 : Received unexpected signal 17 │ec
to│13:26:07.170: info : qemudDispatchSignalEvent:397 : Received unexpected signal 17 │
Th│13:26:07.279: info : qemudDispatchSignalEvent:397 : Received unexpected signal 17
is it a problem ? why does is mean ? why its presented as unexpended ?
1) start vm
or
1) open vnc console to vm
2.6.32-59.1.el6.x86_64
libvirt-0.8.1-23.el6.x86_64
vdsm-4.9-12.3.x86_64
device-mapper-multipath-0.4.9-25.el6.x86_64
lvm2-2.02.72-4.el6.x86_64
qemu-kvm-0.12.1.2-2.109.el6.x86_64
Comment 2RHEL Program Management
2010-08-16 10:58:37 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Rechecked it on the following test environment according to comment 6. No any "Received unexpected signal" can be found again.
It is passed.
Test environment:
libvirt-0.8.7-5.el6
qemu-kvm-0.12.1.2-2.144.el6
kernel-2.6.32-94.el6
I'm not sure what you want me to confirm. The bug is about removing "Received unexpected signal". If you don't see when starting a domain, than it's fixed.
(In reply to comment #10)
> I'm not sure what you want me to confirm. The bug is about removing "Received
> unexpected signal". If you don't see when starting a domain, than it's fixed.
Verified this issue in plain libvirt and just want to know if it is necessary to be verified again in VDSM environment.
Don't see any information like description in plain libvirt.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0596.html