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 1136288

Summary: PPC64: qemu segfault at startup on VM with virtio channels
Product: Red Hat Enterprise Linux 7 Reporter: Francesco Romani <fromani>
Component: qemu-kvmAssignee: David Gibson <dgibson>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: hannsj_uhl, hhuang, juzhang, knoel, michal.skrivanek, michen, rbalakri, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: ppc64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-24 11:54:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1122979    
Attachments:
Description Flags
libvirt domain XML of the failing VM none

Description Francesco Romani 2014-09-02 09:39:53 UTC 
Created attachment 933669 [details]
libvirt domain XML of the failing VM

Description of problem:
While trying to workaround https://bugzilla.redhat.com/show_bug.cgi?id=1136227 ,
I tried to boot up a VM with no network configured, using the oVirt stack
(VDSM, libvirt, qemu).

Without a network configured, qemu just segfaults at startup


Version-Release number of selected component (if applicable):


How reproducible:
qemu-1.6.0-2

Steps to Reproduce:
1. run QEMU as root using the provided configuration
2.
3.

Actual results:
QEMU segfaults


Expected results:
QEMU starts up.
In the case the config is broken (but it shouldn't), qemu should report it without segfaulting

Additional info:
QEMU command line:

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name networkless -S -machine pseries,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d9e6a842-ea6f-4bae-ace5-0b0c6d0701ba -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/networkless.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-09-02T09:31:16,driftfix=slew -no-shutdown -device pci-ohci,id=usb,bus=pci.0,addr=0x2 -device spapr-vscsi,id=scsi0,reg=0x2000 -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x1 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-scsi0-0-0-0,readonly=on,format=raw,serial= -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0 -drive file=/rhev/data-center/e61eb449-6f83-4127-8938-9ab620159d9b/d44dacb7-596d-4939-bb7d-2e2c262bb603/images/5c4ad930-08c4-4203-a84b-4c621edd1715/97e391ec-e3ee-4d8b-b77e-4796198bfecc,if=none,id=drive-virtio-disk0,format=raw,serial=5c4ad930-08c4-4203-a84b-4c621edd1715,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d9e6a842-ea6f-4bae-ace5-0b0c6d0701ba.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d9e6a842-ea6f-4bae-ace5-0b0c6d0701ba.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0 -device usb-kbd,id=input1 -device usb-mouse,id=input2 -vnc 0:0,password -k en-us -device VGA,id=video0,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -usbdevice keyboard
Comment 2 Francesco Romani 2014-09-03 13:11:01 UTC 
*** Bug 1136227 has been marked as a duplicate of this bug. ***
Comment 3 Francesco Romani 2014-09-04 15:32:20 UTC 
It seems the issue is actually related to virtio channels more than network.

If I run this script:

----[ cut here ]----
#!/bin/bash

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 \
        -name networkless \
        -S \
        -machine pseries,accel=kvm,usb=off \
        -m 1024 \
        -realtime mlock=off \
        -smp 1,sockets=1,cores=1,threads=1 \
        -uuid d9e6a842-ea6f-4bae-ace5-0b0c6d0701ba \
        -no-user-config \
        -nodefaults \
        -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/networkless.monitor,server,nowait \
        -mon chardev=charmonitor,id=monitor,mode=control \
        -rtc base=2014-09-02T09:31:16,driftfix=slew \
        -no-shutdown \
        -device pci-ohci,id=usb,bus=pci.0,addr=0x2 \
        -device spapr-vscsi,id=scsi0,reg=0x2000 \
        -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x1 \
        -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \
        -drive if=none,id=drive-scsi0-0-0-0,readonly=on,format=raw,serial= \
        -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0 \
        -device usb-tablet,id=input0 \
        -device usb-kbd,id=input1 \
        -device usb-mouse,id=input2 \
        -vnc 0:0,password \
        -k en-us \
        -device VGA,id=video0,bus=pci.0,addr=0x6 \
        -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 \
        -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d9e6a842-ea6f-4bae-ace5-0b0c6d0701ba.com.redhat.rhevm.vdsm,server,nowait \
        -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm \
        -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d9e6a842-ea6f-4bae-ace5-0b0c6d0701ba.org.qemu.guest_agent.0,server,nowait \
        -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 \
        -usbdevice keyboard
----[ cut here ]----

QEMU segfaults on startup. However, if I drop these four options

        -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d9e6a842-ea6f-4bae-ace5-0b0c6d0701ba.com.redhat.rhevm.vdsm,server,nowait \
        -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm \
        -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d9e6a842-ea6f-4bae-ace5-0b0c6d0701ba.org.qemu.guest_agent.0,server,nowait \
        -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 \

QEMU starts correctly.
Comment 5 David Gibson 2014-11-13 22:37:06 UTC 
I'm assuming this actually occurred with a PowerKVM host?  In which case this is misfiled against RHEL.

We're working on getting a proper bugzilla component for the PowerKVM hypervisor.

In the meantime, if this is fixed in current PowerKVM, can we close as CURRENTRELEASE?
Comment 6 Michal Skrivanek 2014-11-24 11:54:21 UTC 
Fixed in PowerKVM's QEMU as of "RHEV for Power" GA version.