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.

Bug 1068288

Summary: [abrt] qemu-kvm: BN_num_bits(): qemu-kvm killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Peter Kotvan <pkotvan>
Component: spiceAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: acathrow, cfergeau, dblechte, hhuang, juzhang, marcandre.lureau, pkotvan, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:dabd5a0ef8b8d9fc6a99fe7fce023d871245cf8b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-04 11:04:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: sosreport.tar.xz
none
my_appliance kickstart none

Description Peter Kotvan 2014-02-21 12:56:15 UTC
Description of problem:
I have installed lorax, libvirt, virt-install, qemu-kvm. Generated appliance using lorax command:
livemedia-creator --make-appliance --app-name=my_appliance --app-file=my_appliance.xml --app-image=my_appliance.img --iso /var/lib/libvirt/images/boot.iso --ks <path-to-ks>
Appliance was succesfully generated. After that I've issued command:
virt-image my_appliance.xml
and got this report.

Version-Release number of selected component:
qemu-kvm-1.5.3-49.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/qemu-kvm -name my_appliance -S -enable-fips -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid a48ab4be-0a20-4eaa-8c60-83f6457e8e02 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/my_appliance.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/var/tmp/my_appliance.img,if=none,id=drive-ide0-0-0,format=raw,cache=none -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=23,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:5f:bc:87,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
crash_function: BN_num_bits
executable:     /usr/libexec/qemu-kvm
fips_enabled:   1
kernel:         3.10.0-89.el7.x86_64
runlevel:       N 5
sosreport-unused-4-159.brq.redhat.com-20140221072423.tar.xz.sha256: 8296a0a4c8fd0384c19a89b1552fa81eb8e39b8a03422362d9d0ba7f5468e0f0
type:           CCpp
uid:            107

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 BN_num_bits at /lib64/libcrypto.so.10
 #1 RSA_size at /lib64/libcrypto.so.10
 #2 reds_handle_read_link_done at /lib64/libspice-server.so.1
 #3 spice_server_add_client at /lib64/libspice-server.so.1
 #4 reds_accept at /lib64/libspice-server.so.1
 #5 qemu_iohandler_poll
 #6 main_loop_wait

Comment 1 Peter Kotvan 2014-02-21 12:56:21 UTC
Created attachment 865981 [details]
File: backtrace

Comment 2 Peter Kotvan 2014-02-21 12:56:24 UTC
Created attachment 865982 [details]
File: cgroup

Comment 3 Peter Kotvan 2014-02-21 12:56:27 UTC
Created attachment 865984 [details]
File: core_backtrace

Comment 4 Peter Kotvan 2014-02-21 12:56:29 UTC
Created attachment 865985 [details]
File: dso_list

Comment 5 Peter Kotvan 2014-02-21 12:56:33 UTC
Created attachment 865986 [details]
File: environ

Comment 6 Peter Kotvan 2014-02-21 12:56:37 UTC
Created attachment 865987 [details]
File: exploitable

Comment 7 Peter Kotvan 2014-02-21 12:56:40 UTC
Created attachment 865988 [details]
File: limits

Comment 8 Peter Kotvan 2014-02-21 12:56:42 UTC
Created attachment 865989 [details]
File: maps

Comment 9 Peter Kotvan 2014-02-21 12:56:45 UTC
Created attachment 865990 [details]
File: open_fds

Comment 10 Peter Kotvan 2014-02-21 12:56:47 UTC
Created attachment 865991 [details]
File: proc_pid_status

Comment 11 Peter Kotvan 2014-02-21 12:56:49 UTC
Created attachment 865992 [details]
File: var_log_messages

Comment 12 Peter Kotvan 2014-02-21 12:57:01 UTC
Created attachment 865993 [details]
File: sosreport.tar.xz

Comment 13 Peter Kotvan 2014-02-21 12:59:05 UTC
Created attachment 866004 [details]
my_appliance kickstart

Comment 15 Christophe Fergeau 2014-02-25 10:20:11 UTC
(In reply to Peter Kotvan from comment #0)
> Description of problem:
> I have installed lorax, libvirt, virt-install, qemu-kvm. Generated appliance
> using lorax command:
> livemedia-creator --make-appliance --app-name=my_appliance
> --app-file=my_appliance.xml --app-image=my_appliance.img --iso
> /var/lib/libvirt/images/boot.iso --ks <path-to-ks>

I wanted to give this a try, but RHEL7/f20 lorax do not have "--app-image", am I missing something?
When the crash happened, was there a client connected to the VM?
What spice-server, spice-gtk and virt-viewer versions were you using?

Comment 16 Peter Kotvan 2014-02-26 13:45:59 UTC
I did not realize that RHEL7 does not have "--app-image" however livmedia-creator created appliance without errors.

At first there was no client connected to VM. But after first few tries (I have tried to start VM but it immediately stopped and abrt reported the crash) I have opened the the spice client, but it made no difference. The VM died immediately after it started.

Versions of programs you requested.
spice-server-0.12.4-5.el7
spice-gtk3-0.20-8.el7
virt-viewer-0.5.7-7.el7

I tried this with: "sudo livemedia-creator --make-appliance --app-name my_appliance --app-file=my_appliance.xml --image-name=my_appliance.img --iso boot.iso --ks ks"
and everything went OK. And it is probably worth to mention that virt-image will be dropped from RHEL-7 bug 1061913 .

Comment 17 Christophe Fergeau 2014-02-28 16:39:28 UTC
By any chance, are you running in fips mode? (fips=1 on kernel command line). You can also check the value of /proc/sys/crypto/fips_enabled.

Comment 18 Peter Kotvan 2014-03-03 11:24:08 UTC
I do not have that system installed, but it was default installation so it should have fips=0.

Comment 19 RHEL Program Management 2014-03-22 05:58:19 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 20 Marc-Andre Lureau 2014-07-04 11:04:54 UTC
Even though Peter said "it should have fips=0", qemu had -enable-fips. Did it have OPENSSL_FORCE_FIPS_MODE=1 ? Setting this environment variable is enough to get the exact same crash.

I think this is the same bug as 1071176 and can be closed as duplicate.

*** This bug has been marked as a duplicate of bug 1071176 ***