Home > Hardware Error > Hardware Error Register_ioport_write Invalid Opaque

Hardware Error Register_ioport_write Invalid Opaque

A: No, we don't support mult-func hotplug in rhel6. It seems ioports were repeatedly registered until no enough resource. It does nothing anyway (other than occupying an I/O port the guest doesn't know about, which leads to this bug as the guest probably tries to map an pci bar to For information on the advisory, and where to find the updated files, follow the link below. weblink

Comment 15 Amos Kong 2013-06-25 02:47:32 EDT (In reply to chayang from comment #14) > Hi, Amos, > Can you take a look at above complaint? multiple-function hotplug isn't supported by us, so close this bug as WONTFIX. For internal issue in Comment #0, it's not caused by ioeventfds exhausted. host info: kernel-2.6.32-377.el6.x86_64 qemu-kvm-0.12.1.2-2.370.el6.x86_64 guest info: kernel-2.6.32-377.el6.x86_64 Steps: 1.start guest. # /usr/libexec/qemu-kvm -S -M rhel6.5.0 -cpu host -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -no-kvm-pit-reinjection -name sluo-test -uuid a51eb497-bfd7-47c0-8b5b-0853716e3ce5 -rtc base=localtime,clock=host,driftfix=slew -drive file=/home/RHEL-Server-6.4-64-virtio.qcow2.bk,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial=QEMU-DISK1 https://bugzilla.redhat.com/show_bug.cgi?id=1142078

Will debug later. (gdb) bt #0 0x00007ffff50888a5 in raise () from /lib64/libc.so.6 #1 0x00007ffff508a085 in abort () from /lib64/libc.so.6 #2 0x00007ffff7e4ee9d in kvm_io_ioeventfd_add (listener=0x7ffff83064c0, section=0x7ffff2ed05b0, match_data=true, data=0, e=0x7ffffc202280) at /home/devel/qemu/kvm-all.c:788 #3 What do > > > uname -a > > > ident /usr/src/sys/sys/param.h > > > ident /usr/include/sys/param.h > > > grep define.__FreeBSD_version /usr/include/sys/param.h > > > (cd /usr/ports/emulators/kqemu-kmod-devel && make -V If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1553.html Note You need to log in before you can comment on or make changes to this bug. I > created the image with: > > qemu-img create -f qcow2 xp.img 100G qemu -cdrom /dev/acd0 -hda xp.img -m > 256 -boot d > > I get this error: > Have you tried it without the printk buffer enabled? I have posted a patch to fix error note: [qemu-devel][PATCH] kvm: add detail error message when fail to add ioeventfd.

after guest boots up, run a script to keep on hot plugging disks into guest: cat hotplug_disk.sh #!/bin/bash for i in `seq 4 9` a b c d e f 11 Finished adding all disks into guest specified in script mentioned in step 2, no SIGABRT happened. Comment 6 Gerd Hoffmann 2013-05-28 01:52:53 EDT Looks good, acpi_dbg_writel can go away. https://groups.google.com/d/topic/bifferboard/Wuqfs-VsMgQ I don't know much about OpenBIOS, but I'm happy to help if it looks like the resource allocation is breaking it.

THank you for your help, it is greatly appreciated. :) but when I try to read directly from the disk to install the OS: On Sun, Apr 12, 2009 at 11:50 The following patch can fix internal issue. I can successfully hotplug 0x4~0x18 slots, fail to hotplug 0x19 slot. Show must go on ! Вернуться к началу Alex Keda стреляли... Сообщения: 34718 Зарегистрирован: 2004-10-18 14:25:19 Откуда: Made in USSR Контактная информация: Контактная информация пользователя Alex Keda ICQ Сайт Re: QEMU:

Qemu-kvm crashed during hot adding disks into guest. (gdb) r -M rhel6.4.0 -enable-kvm -m 2048 -smp 2,sockets=1,cores=2,threads=1 -drive file=/home/rhel6.4.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,serial=f82002eb-520c-469b-90c2-663277e90437,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -net none -nodefaults -spice port=8000,disable-ticketing -k en-us -vga qxl -global Mein KontoSucheMapsYouTubePlayNewsGmailDriveKalenderGoogle+ÜbersetzerFotosMehrShoppingDocsBooksBloggerKontakteHangoutsNoch mehr von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen cannot get kqemu to load with kldload Juergen Lock nox at jelal.kn-bremen.de Sun Apr 12 19:40:01 UTC 2009 Previous message: Comment 16 Chao Yang 2013-06-25 02:56:32 EDT This bug has been fixed correctly as per Comment #13, #14 and #15. Have you rebuilt qemu after you upgraded your world?

Comment 8 Sibiao Luo 2013-05-30 01:03:16 EDT Reproduce this issue on qemu-kvm-0.12.1.2-2.370.el6.x86_64, hot-plugging many multi-fun devices to guest, it caused qemu crash. have a peek at these guys The IO address range is > only 16 bits from 0-64K. > > I guess we'll have to get more information from qemu so we know which > port address is Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Um Google Thanks, Myles Previous message: [coreboot] SVN Coreboot-v3 with SVN OpenBIOS payload panics on boot with qemu Next message: [coreboot] SVN Coreboot-v3 with SVN OpenBIOS payload panics on boot with qemu Messages

what's I can do: Q: increase ioeventfd resource in host? Comment 20 errata-xmlrpc 2013-11-21 01:48:07 EST Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. Status: CLOSED ERRATA Aliases: None Product: Red Hat Enterprise Linux 6 Classification: Red Hat Component: qemu-kvm (Show other bugs) Sub Component: --- Version: 6.4 Hardware: Unspecified Unspecified Priority unspecified Severity unspecified check over here Red Hat Bugzilla – Bug952240 hot-plugging multi-func devices caused: qemu: hardware error: register_ioport_write: invalid opaque Last modified: 2015-05-24 20:07:15 EDT Home | New | Search | [?] | Reports |

Current process is abort() without nice error message, I can fix it in upstream. Fallback to a userspace (slower). diff --git a/hw/acpi.c b/hw/acpi.c index f824b8e..ddbbda7 100644 --- a/hw/acpi.c +++ b/hw/acpi.c @@ -34,8 +34,6 @@ /* i82731AB (PIIX4) compatible power management function */ #define PM_FREQ 3579545 -#define ACPI_DBG_IO_ADDR 0xb044 - #define

do we need to fix this in RHEL6?

Is it another bug? I checked out 7.2 about a week > or > > so ago. qemu: hardware error: register_ioport_write: invalid opaque If I only add less (2) slots, it works Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.356.el6.x86_64 guest Kernel: 2.6.32-343.el6.x86_64 How reproducible: always Steps to start guest: (gdb) r -monitor unix:/tmp/m,nowait,server -vnc :2 /images/RHEL-Server-6.4-64-virtio.qcow2 -m 1000 2.

The complaint is normal/expected, we don't have enough ioeventfd in host kernel. I am > > starting to wonder if that is the root cause of all the trouble. > > Very likely, kqemu uses which in this case seems to > Comment 14 Chao Yang 2013-06-25 02:41:16 EDT Hi, Amos, Can you take a look at above complaint? this content warning: the debug information found in "/usr/lib/debug/usr/lib64/libspice-server.so.1.5.0.debug" does not match "/usr/lib64/libspice-server.so.1" (CRC mismatch). [New Thread 0x7ffff348d700 (LWP 20081)] [New Thread 0x7ffff288b700 (LWP 20082)] [Thread 0x7ffff348d700 (LWP 20081) exited] [New Thread 0x7ffff348d700

HTH, Juergen Previous message: cannot get kqemu to load with kldload Next message: cannot get kqemu to load with kldload Messages sorted by: [ date ] [ thread ] [ subject execute radd.sh to hot-add disks Actual results: qemu crash Additional info: radd.sh =================== for i in `seq 3 9` a b c d e f 11 12 13 14 15 16 boot eax = 0x2badb002 boot ebx = 0xf0000 boot arg = 0x2 That doesn't look good. 0x2badb002 instead of 0x100060 in the working log. But qemu-kvm complained: qemu-kvm: virtio_pci_set_host_notifier_internal: unable to map ioeventfd: -28 qemu-kvm: virtio_pci_start_ioeventfd: failed.

Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results. Here's the output you asked for: > > > > cinema# uname -a > > FreeBSD cinema.distantsoil.org 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0: > Sat > > Apr 11 19:32:34 PDT 2009 > Comment 7 Amos Kong 2013-05-28 22:07:32 EDT Re-open this bug, worth to fix this qemu crash. Is it another bug?

Comment 3 Amos Kong 2013-05-22 02:03:32 EDT Internal issue in comment #0, can be reproduced with qemu-kvm-0.12.1.2-2.180.el6 (multifunction option was introduced in that version). I've never seen that one... KVM does not * support SMM mode. */ Comment 5 Amos Kong 2013-05-22 04:00:18 EDT Hi Gerd, Is my fix in last comment right? When did you checkout/c(v)sup > /usr/src > > > and which branch/tag was it?

Comment 4 Amos Kong 2013-05-22 03:58:59 EDT Upstream fixed this problem in commit 8385b173a0ca4c2345434104e6cc2a7259adc4b9 ACPI_DBG_IO_ADDR already takes the ioport, it could not be re-allocate to hot-plugged pci device. I can see some hardware enumeration but before the > OpenBIOS prompt appears, qemu puts out the following message on the console: > > qemu: hardware error: register_ioport_write: invalid opaque > VirtualBox, QEMU, ESX/ESXi и прочия Правила форума Убедительная просьба юзать теги [code] при оформлении листингов.Сообщения не оформленные должным образом имеют все шансы быть незамеченными. Ответить Отправить тему по email Версия для This problem doesn't exist in latest upstream.

I created the image with: qemu-img create -f qcow2 xp.img 100G qemu -cdrom /dev/acd0 -hda xp.img -m 256 -boot d I get this error: qemu: hardware error: register_ioport_write: invalid opaque CPU If we use pci-bridge, ioeventfd can also be exhausted. launch a guest by: /usr/libexec/qemu-kvm -M rhel6.5.0 -enable-kvm -m 2048 -smp 2,sockets=1,cores=2,threads=1 -drive file=/home/rhel6.4.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,serial=f82002eb-520c-469b-90c2-663277e90437,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -net none -nodefaults -spice port=8000,disable-ticketing -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -monitor unix:/tmp/test,server,nowait 2. Or maybe try doing that again now that you've built kqemu against the proper kernel tree... > > I'm going to try copying the install cd to disk first with dd