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 618788 - device-assignment hangs with kvm_run: Bad address
Summary: device-assignment hangs with kvm_run: Bad address
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Alex Williamson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 619989 (view as bug list)
Depends On:
Blocks: 611715
TreeView+ depends on / blocked
 
Reported: 2010-07-27 18:06 UTC by Alex Williamson
Modified: 2013-01-09 22:57 UTC (History)
10 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.106.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 21:27:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alex Williamson 2010-07-27 18:06:53 UTC 
Description of problem:
Assigning a device with an option ROM on kernel 2.6.32-52.el6.x86_64 results in:

kvm_run: Bad address
kvm_run returned -14

and the guest stops

Version-Release number of selected component (if applicable):
kernel-2.6.32-52.el6.x86_64
qemu-kvm-0.12.1.2-2.99.el6.bz617463.x86_64

How reproducible:
100%

Steps to Reproduce:
1. assign dev with option ROM
2.
3.
  
Actual results:
hang

Expected results:
boot

Additional info:
Comment 1 Dor Laor 2010-07-28 09:37:05 UTC 
Alex, can you please provide the use case where this error is found?
I'm trying to better qualify it as a blocker, so use case of 'this specific nic device assignment failed' is desired.
Comment 2 Alex Williamson 2010-07-28 13:03:53 UTC 
Dor, any device with an option rom will generate the bad address error and cause the guest to hang, whether the option rom is needed by the guest drivers or not.  This includes things like kawela and niantic physical functions, nearly any nic that supports pxe boot on the host, and various other cards.  Device assignment is nearly unusable without this change.  This change is only now necessary because the -52 kernel included this change from kvm.git:

commit b4f8c24994f8fd8fedb304dc6aa23557fdced21c
Author: Gleb Natapov <gleb>
Date:   Wed Jul 7 20:16:45 2010 +0300

    KVM: Return EFAULT from kvm ioctl when guest accesses bad area
    
    Currently if guest access address that belongs to memory slot but is not
    backed up by page or page is read only KVM treats it like MMIO access.
    Remove that capability. It was never part of the interface and should
    not be relied upon.
    
    Signed-off-by: Gleb Natapov <gleb>
    Signed-off-by: Avi Kivity <avi>
Comment 5 Chris Wright 2010-07-31 17:54:46 UTC 
*** Bug 619989 has been marked as a duplicate of this bug. ***
Comment 6 Shirley Zhou 2010-08-03 05:42:39 UTC 
Reporduced on qemu-kvm-0.12.1.2-2.96.el6

Verified on qemu-kvm-0.12.1.2-2.106.el6

hw info :
28:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)

CLI:
/usr/libexec/qemu-kvm -S -M rhel6.0.0 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name pci-6.64 -uuid 74b17311-f33f-8b6c-f1e5-f12f9fcd4909 -nodefconfig -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/pci-6.64.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=utc -no-reboot -boot c -kernel /var/lib/libvirt/boot/virtinst-vmlinuz.S15PWj -initrd /var/lib/libvirt/boot/virtinst-initrd.img.j5yEXp -append method=http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL6.0-20100722.0/6.0/Server/x86_64/os -drive file=/home/images/pci-assignment.img,if=none,id=drive-virtio-disk0,boot=on,format=raw,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -vga cirrus -device AC97,id=sound0,bus=pci.0,addr=0x5 -device pci-assign,host=28:00.0,id=hostdev0,configfd=18,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3

The guest can install successfully. Change status to verified.
Comment 7 releng-rhel@redhat.com 2010-11-10 21:27:00 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.