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 1138122 - forbid invalid address type for panic device
Summary: forbid invalid address type for panic device
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.6
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Erik Skultety
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1138125
TreeView+ depends on / blocked
 
Reported: 2014-09-04 06:30 UTC by Jincheng Miao
Modified: 2015-01-27 09:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1138125 (view as bug list)
Environment:
Last Closed: 2015-01-27 09:05:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jincheng Miao 2014-09-04 06:30:56 UTC 
Description of problem:
panic device only could specify isa type address with iobase(ioport).
libvirt should forbid other address type for panic device in order to avoid confusion from users.


Version-Release number of selected component (if applicable):
libvirt-0.10.2-43.el6.x86_64
qemu-kvm-0.12.1.2-2.439.el6.x86_64


How reproducible:
100%

Steps to Reproduce:
1. add panic device to guest, which address is same with memballoon
# virsh edit r7
...
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </memballoon>
    <panic>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </panic>
...

2. start it
# virsh start r7
Domain r7 started

# ps -ef | grep qemu
qemu     12136     1 13 02:26 ?        00:00:00 /usr/libexec/qemu-kvm -name r7 -S -M rhel6.6.0 -enable-kvm -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=2,threads=1 -uuid 5a85c12d-6004-7c04-e2d2-55f723d977f4 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/r7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/r7.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:07:f9:ca,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -device pvpanic -msg timestamp=on

Expect result:
in step 1, report an error.
Comment 1 Erik Skultety 2014-09-10 11:29:12 UTC 
Fixed upstream:

commit afb4c6b6634e16beb5ddbca3f1113c615e10e7e4
Author: Erik Skultety <eskultet>
Date:   Mon Sep 8 12:27:23 2014 +0200

    qemu: panic device: check for invalid address type
    
    qemu now checks for invalid address type for a panic device, which is
    currently implemented only to use ISA address type, thus rejecting
    any other options, except for leaving XML attributes blank, in that case,
    defaults are used (this behaviour remains the same from earlier verions).
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1138125
    
    Signed-off-by: Martin Kletzander <mkletzan>

v1.2.8-53-gafb4c6b
Note You need to log in before you can comment on or make changes to this bug.