[Bug 1856834] Re: PCI broken in qemu ppc e500 in v2.12.0 and other versions
Thanks for all the help Laurent! I'm new to git so not surre how to 'properly' revert a previous commit on top of master, so I'll google, but if you have some a good link please do send. Also, I've heard of the term "bisect" for figuring out at which commit something breaks and if there were some good documentation to spell out the steps to do that for users that aren't, well advanced kernel gurus :D , I'm sure we'd be happy to save you smarter guys time with any mundane testing steps when possible :) thx! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: PCI broken in qemu ppc e500 in v2.12.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
Sorry for the delay, I have sent you a private message/email with the actual kernel image. thx! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
With some precautionary measures I think I can provide it. Not sure what of our drivers may already be compiled in etc so I need to send it to you privately so only you have access for testing etc after which you would delete it once issue fixed or discovered etc. Is it possible to send you private message on here with such a link or better email? thanks -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
Hope you enjoyed the Holidays, Happy 2020! I would really appreciate if you could confirm for me if virtio works fine for you with ppc -M mpc8544ds with older Linux guest kernels like 2.6.32 thanks! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
fyi from what I recall guest kernel was built using mpc85xx_defconfig with some additions like virtio etc. If virtio is working for you just fine using same command as mine, then perhaps its some peculiarity to do with my specific guest kernel or kernel version? (uImage is about 3.4M with equivalent vmlinux about 72M) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
Thanks I tried with: /root/QEMU/qemu-git-4.2.0rc4/qemu/build/ppc-softmmu/qemu-system-ppc -M mpc8544ds -nographic -kernel /home/me/boot/uImage-2.6.32 -append "root=/dev/vda rw" -device virtio-blk-pci,drive=drive0,disable- modern=true -drive file=/home/me/mmcblk0p2.dd,if=none,id=drive0,format=raw And again it worked with qemu 2.8.1 but failed with the above 4.2.0rc4 on the same x86_64 host. On another x86_64 host I confirmed that the below works with qemu 2.8.0 root@myserver:~# qemu-system-ppc -M mpc8544ds -nographic -kernel /home/me/boot/uImage-2.6.32 -append "root=/dev/vda rw" -device virtio- blk-pci,drive=drive0,disable-modern=true -drive file=/home/me/mmcblk0p2.dd,if=none,id=drive0,format=raw But again even on this system 4.2.0 failes with that same command: root@myserver:~# /root/QEMU/qemu-4.2.0/build/ppc-softmmu/qemu-system-ppc -M mpc8544ds -nographic -kernel /home/me/boot/uImage-2.6.32 -append "root=/dev/vda rw" -device virtio-blk-pci,drive=drive0,disable-modern=true -drive file=/home/me/mmcblk0p2.dd,if=none,id=drive0,format=raw Fails/freezes at the same vda: location. Running it from its installed location didn't help, the following still failed at vda: also. root@myserver:/opt/qemu4.2.0/bin# ./qemu-system-ppc -M mpc8544ds -nographic -kernel /home/me/boot/uImage-2.6.32 -append "root=/dev/vda rw" -device virtio-blk-pci,drive=drive0,disable-modern=true -drive file=/home/me/mmcblk0p2.dd,if=none,id=drive0,format=raw Although I didn't think its required for the softmmu qemu "emulation" only, ie not "kvm", I even enabled kvm as well as DMAR+IOMMU on the kernel and recompiled 4.2.0 but had same vda: failure. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
Did you try with just a basic virtio disk and it works for you? Because even a basic virtio drive addition fails for me, even this fails on higher than 2.8.1 For example: qemu-system-ppc -M mpc8544ds -nographic -kernel /home/me/boot/uImage-2.6.32 -append "root=/dev/vda rw" -drive file=/home/me/mmcblk0p2.dd,if=virtio The only thing I can think of, is if somehow vda fails due to me running the higher version qemu binaries from their build locations/paths without actually "installing" them in usual paths etc. But I ran the 2.8 version from build location I compiled it from and it worked from there, but perhaps the 2.8 version was also the distro installed default one so maybe it found dependencies it needed? Anyway I just now reconfigured 4.2.0 with --prefix /opt/qemu4.2.0 and ran it from installed dir: root@myserver:/opt/qemu4.2.0/bin# ./qemu-system-ppc -M mpc8544ds -nographic -kernel /home/me/boot/uImage-2.6.32 -append "root=/dev/vda rw" -drive file=/home/me/mmcblk0p2.dd,if=virtio But it still fails even after make install and running it from the /opt/qemu4.2.0/bin directory. Is it somehow conflicting with the other qemu version 2.8.. installed by usual apt-get install? Regardless of how I start them, version 3.1.0 and 4.2.0rc4 and some other 4.19git and 4.2.0final all fail/freeze at: " nbd: registered device at major 43 vda: " -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
Also tested on another system (Debian GNU/Linux 9 \n \l with kernel SMP Debian 3.16.56-1+deb8u1 (2018-05-08) x86_64) besides the previous Ubuntu 17.04 and confirmed even Qemu 2.8.1 is working but Qemu 3.1.10 and higher not working, virtio fails/freezes guest at vda as on the other system. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1596832] Re: e500 -bios/-kernel broken with big images
Curious: Is your guest kernel >=3.6 with qemu-ppce500 config ie qemu_ppce500 defined etc? In case u-boot loads/maps uImage format kernel differently have you tried uImage vs vmlinux? And are you able to boot ok with an mpc... machine instead of ppce500 by specifying a dtb file or dtb compatibility? Do you know if more recent qemu (2.8 or 3 or 4.2) has same issue for you? Oh wow I just noticed this is from 2016! It would be nice for such bugs to have follow-up, closure, or summary of solution/circumvention/workaround taken by those who posted them :) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1596832 Title: e500 -bios/-kernel broken with big images Status in QEMU: New Bug description: This is tested using qemu 2.4.1, but it looks like the code qemu/hw/ppc/e500.c has not changed since. This looks like the source of the problem: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=3812c71ffaa2cf733c3087792b859fef30b7545f What works: -- Basic invocation qemu-system-ppc -machine ppce500 -monitor stdio -bios u-boot.e500 works, I get the uboot prompt and this: (qemu) info roms addr=00f0 size=0x044b8c mem=ram name="phdr #0: .../qemu/share/qemu/u-boot.e500" addr=00f81000 size=0x006b00 mem=ram name="phdr #1: .../qemu/share/qemu/u-boot.e500" Passing u-boot.e500 image as kernel (-bios u-boot.e500 -kernel u-boot.e500) appears to work, $qemu_kernel_addr is filled in, though (as expected) uboot complains about the image format. (qemu) info roms addr=00f0 size=0x044b8c mem=ram name="phdr #0: .../qemu/share/qemu/u-boot.e500" addr=00f81000 size=0x006b00 mem=ram name="phdr #1: .../qemu/share/qemu/u-boot.e500" addr=0200 size=0x054e8c mem=ram name=".../qemu/share/qemu/u-boot.e500 What doesn't work: - However, once I try to load a big image (>=32 MiB), uboot doesn't even show anything: qemu-system-ppc -machine ppce500 -monitor stdio -bios u-boot.e500 -kernel boot/vmlinux -m 1024 (qemu) info roms addr=00f0 size=0x044b8c mem=ram name="phdr #0: .../qemu/share/qemu/u-boot.e500" addr=00f81000 size=0x006b00 mem=ram name="phdr #1: .../qemu/share/qemu/u-boot.e500" addr=0200 size=0x27aeedc mem=ram name="boot/vmlinux" ... (gdb) bt #0 0x00f2efcc in ?? () #1 0x00f31554 in ?? () #2 0x00f03f4c in ?? () #3 0x00f04458 in ?? () #4 0x00f028dc in ?? () #5 0x00f01080 in ?? () The thing is, this used to work +- before the commit, where I'd just pass the image as -kernel option, and it booted. If I do that now (w/o the -bios option, using the exact same image), the kernel gets loaded twice, only at different addresses (the cause is obvious from the commit), causing overlap error: qemu-system-ppc -machine ppce500 -monitor stdio -kernel boot/vmlinux -m 1024 QEMU 2.4.1 monitor - type 'help' for more information (qemu) rom: requested regions overlap (rom boot/vmlinux. free=0x027492fc, addr=0x0200) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1596832/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
** Tags added: ppc -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: Virtio broken in qemu ppc in 4.2.0 and other versions
** Summary changed: - softmmu qemu-system-ppc freezes at virtio vda + Virtio broken in qemu ppc in 4.2.0 and other versions ** Tags added: virtio ** Tags added: powerpc softmmu -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: Virtio broken in qemu ppc in 4.2.0 and other versions Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
[Bug 1856834] Re: softmmu qemu-system-ppc freezes at virtio vda
** Description changed: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 - vda: + vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) - In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files) + In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 tx - ecs + ecs ** Description changed: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) - In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 + In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: softmmu qemu-system-ppc freezes at virtio vda Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from
[Bug 1856834] [NEW] softmmu qemu-system-ppc freezes at virtio vda
Public bug reported: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1856834 Title: softmmu qemu-system-ppc freezes at virtio vda Status in QEMU: New Bug description: The same qemu -M mpc... command that works on qemu-system-ppc version 2.8.0 freezes guest on bootup and shows error for qemu-system-ppc version 4.2.0release and 4.19dirtygit: qemu-system-ppc: virtio-blk failed to set guest notifier (-24), ensure -accel kvm is set. qemu-system-ppc: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). ends/freezes at: nbd: registered device at major 43 vda: I'm using -drive file=/home/me/rawimage.dd,if=virtio and works fine in version 2.8.0 installed with apt-get install (Ubuntu 17.04) and also with 2.8.0 official release from git/github that I compiled/built myself. But both of the newer releases fail on the same exact machine same config. I also noticed that qemu-2.8.0 was fine with mtd but the newer ones I tried weren't, ie gave qemu-system-ppc: -drive if=mtd: machine type does not support if=mtd,bus=0,unit=0 (but I removed -drive if=mtd since wasn't using it anyway) I also tried on windows but I think virtio doesn't work on windows hosts at all? On windows host it fails the same way, even version 2.12 as well as 4.1.10... used: ./configure --prefix=/opt/... --enable-fdt --enable-kvm --enable-debug (basically all steps the same on same exact system same config, yet 2.8.0 works fine whether apt-get installed or built from source while the others I built, 4.19/4.2.0 or 2.12/4.1.10(win) don't.) In case newer qemu versions act weird on various kernels, I did try with both vmlinuz-4.10.0-19-generic and vmlinuz-4.13.12-041312-generic (I didn't compile them but I can provide config-..files. This is on Ubuntu 17.04 x86_64 host emulating e500v2 cpm guest, ie -M mpc... GUEST kernel 2.6.32.44 which is why I can't use -M ppce500 instead..) tx ecs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1856834/+subscriptions
