With a gdb attached I got the following backtrace:
Program received signal SIGABRT, Aborted.
0x75f5eff0 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x75f5eff0 in raise () at /lib64/libc.so.6
#1 0x75f6136c in abort () at /lib64/libc.so.6
#2 0x1009e704 in
Yeah, the problem looks like in virtio-pci-net. This is the output when
running in a Power 9
host:
sudo ./qemu-system-ppc64 -nographic -vga none -m 4G -M pseries,accel=kvm
-netdev type=user,id=net0 -device virtio-net-pci,netdev=net0
SLOF
On Tue, Jan 23, 2018 at 01:05:28AM -0200, jos...@linux.vnet.ibm.com wrote:
> Hello people!
>
> I'm not able to boot any guest that sets a virtio block device like:
> (branch master)
>
> [PPC64]
> qemu-system-ppc64 -cpu POWER8 -nographic -vga none -m 4G -M
> pseries,accel=kvm,kvm-type=PR -drive
Hello people!
I'm not able to boot any guest that sets a virtio block device like:
(branch master)
[PPC64]
qemu-system-ppc64 -cpu POWER8 -nographic -vga none -m 4G -M
pseries,accel=kvm,kvm-type=PR -drive file=disk.qcow2,if=virtio
QEMU Starting
Build Date = Dec 18 2017 13:08:00
FW Version =
