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:
This happens for me when resuming paused Windows 10 guest in which
I run CDK, ie. Vagrant controlled Virtualbox machine with RHEL 7.2.
So this is nested virtualization setup:
L0 = this RHEL 7.2 host
L1 = Windows 10 Enterprise
L2 = RHEL 7.2 with Virtualbox 5.0.16 as hypervisor (controlled by Vagrant)
It happened to me several times, not sure whether always.
Factor could be that between pause/resume of L1 I also suspended L0
(it is my notebook I carry around).
Can try to reproduce again if needed - what more debug data would you like?
Version-Release number of selected component:
qemu-kvm-rhev-2.1.2-23.el7_1.6
Additional info:
reporter: libreport-2.1.11
backtrace_rating: 4
cmdline: /usr/libexec/qemu-kvm -name win10ent -S -machine pc-i440fx-rhel7.1.0,accel=kvm,usb=off -cpu SandyBridge,+erms,+smep,+fsgsbase,+rdrand,+f16c,+osxsave,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -mem-prealloc -mem-path /dev/hugepages/libvirt/qemu -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 3c9e2ed3-2c04-403d-82d3-9628bbce70ed -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-win10ent/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/win10ent-1.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/home/dkutalek/install/en_windows_10_enterprise_2015_ltsb_x64_dvd_6848446.iso,if=none,id=drive-ide0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive file=/home/dkutalek/install/virtio-win-0.1.113.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:39:ba:37,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 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
crash_function: spice_chr_add_watch
executable: /usr/libexec/qemu-kvm
global_pid: 16474
kernel: 3.10.0-327.10.1.el7.x86_64
runlevel: N 5
type: CCpp
uid: 107
Truncated backtrace:
Thread no. 1 (10 frames)
#4 spice_chr_add_watch at spice-qemu-char.c:173
#5 qemu_chr_fe_add_watch at qemu-char.c:3671
#6 usbredir_write at hw/usb/redirect.c:293
#7 usbredirparser_do_write at /lib64/libusbredirparser.so.1
#8 vm_state_notify at vl.c:1714
#9 vm_start at vl.c:751
#10 qmp_cont at qmp.c:177
#11 qmp_marshal_input_cont at qmp-marshal.c:3025
#12 qmp_call_cmd at /usr/src/debug/qemu-2.1.2/monitor.c:5038
#13 handle_qmp_command at /usr/src/debug/qemu-2.1.2/monitor.c:5104
> L0 = this RHEL 7.2 host> Version-Release number of selected component:
> qemu-kvm-rhev-2.1.2-23.el7_1.6
^^^^^^^
This appears to be the RHEL-7.1 version, not RHEL-7.2.
Please update qemu, try again and report back.
High chance to be a bug 1128992 duplicate,
should be fixed in qemu-kvm-rhev-2.3.0-20.el7 and newer.
(In reply to Gerd Hoffmann from comment #14)
> > L0 = this RHEL 7.2 host
>
> > Version-Release number of selected component:
> > qemu-kvm-rhev-2.1.2-23.el7_1.6
> ^^^^^^^
>
> This appears to be the RHEL-7.1 version, not RHEL-7.2.
> Please update qemu, try again and report back.
>
> High chance to be a bug 1128992 duplicate,
> should be fixed in qemu-kvm-rhev-2.3.0-20.el7 and newer.
Thanks for hint, I updated the package and crash occurs no more.
The problem was hidden in having updated RHEL 7.2
mixed with non updated Openstack source.
*** This bug has been marked as a duplicate of bug 1128992 ***