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
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 o
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
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 subs
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 equivalen
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
A
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/m
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
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 compatibil
** 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
** 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:
** 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 se
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-syste
13 matches
Mail list logo
