On Wed, 2018-11-28 at 13:25 +0100, Andrea Bolognani wrote:
On Tue, 2018-11-27 at 20:37 +0100, infos(a)nafets.de wrote:
> I use:
> - Arch Linux ARM
http://os.archlinuxarm.org/os/ArchLinuxARM-rpi-latest.tar.gz
> - Kernel
https://github.com/dhruvvyas90/qemu-rpi-kernel/blob/master/kernel-qemu-4....
> - dtb
https://github.com/dhruvvyas90/qemu-rpi-kernel/blob/master/versatile-pb.d...
> with
> virt-install --name vPiBuildTest --virt-type qemu --memory 256 --vcpus=1 --import
--disk /data/test/pibuild/vPiBuildTest-sys.raw,format=raw,bus=scsi --events
on_crash=restart --noautoconsole --noreboot --net none --arch armv6l --cpu arm1176
--machine versatilepb --boot
"kernel=/data/test/pibuild/kernel-qemu-4.14.50-stretch,dtb=/data/test/pibuild/versatile-pb.dtb,kernel_args=root=/dev/sda2
panic=1 rootfstype=ext4 rw console=ttyAMA0,115200"
Okay, I'll give it a try.
I tried the above but using the latest Raspbian Stretch Lite image
instead of Arch: the guest comes up with no issues and offers serial
console access, so that part works nicely.
However, I notice that you are using '--network none' and so of
course there is no network connectivity inside the guest. My own
attempts at fixing this were unsuccessful, in that I can get a PCI
device such as rtl8139 or even virtio-net-pci to be detected by the
guest, but the corresponding drivers are not included in the kernel
downloaded from the GitHub repository linked above; the versatilepb
board's own integrated network device (smc91c111), on the other hand,
seems not to support instantiation via -device and is thus not usable
without adding hacks to libvirt. Did you manage to get network
functionality working some other way?
Since you already need a custom kernel to boot the image with QEMU,
and you also use an approximation of the actual hardware rather than
a faithful reproduction, I think it would make sense to go one step
further and include VirtIO drivers in the kernel image.
--
Andrea Bolognani / Red Hat / Virtualization