virtio-net and virtio-scsi driver didn't work on PowerPC64 due to an endianess problem on Device Configuration Space area. This area was assumed to be in same endianess as the guest OS, but virtio-1.x spec says:

2.3 Device Configuration Space
Device configuration space is generally used for rarely-changing or initialization-time parameters. Where configuration fields are optional, their existence is indicated by feature bits: Future versions of this specification will likely extend the device configuration space by adding extra fields at the tail. Note: The device configuration space uses the little-endian format for multi-byte fields.

This patch fixes the endianess on Big Endian platforms such as PowerPC64 and enables it on default kernel configuration.

Reference: http://docs.oasis-open.org/virtio/virtio/v1.0/cs04/virtio-v1.0-cs04.html#x1-170003

Check virtio-net and virtio-scsi on PowerPC64 elfv2 kernel, on QEMU using the following parameters:

qemu-system-ppc64 -name guest=alfredo3 -m 4096 -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd -drive if=none,id=hd,file=vdisks/vm3-disk1.qcow2,format=qcow2 -device virtio-net-pci,netdev=vneta0,disable-legacy=off,disable-modern=off -netdev tap,id=vneta0 -nographic -vga none -cpu POWER8E -smp 8 -enable-kvm -machine pseries-3.0,accel=kvm,cap-cfpc=broken,cap-sbbc=broken,cap-ibs=broken,cap-hpt-max-page-size=16M -mem-prealloc -mem-path /dev/hugepages