On 15 Oct 2013, at 15:21, Peter Maydell <peter.maydell@xxxxxxxxxx> wrote: > On 12 September 2013 11:17, Peter Maydell <peter.maydell@xxxxxxxxxx> wrote: >> This patch series adds a 'virt' platform which uses the >> kernel's mach-virt (fully device-tree driven) support >> to create a simple minimalist platform intended for >> use for KVM VM guests. >> >> The major change here is that I've added a PL011 UART. >> >> Sample command line: >> >> qemu-system-arm -machine type=virt -display none \ >> -kernel zImage \ >> -append 'root=/dev/vda rw console=ttyAMA0 rootwait' >> -cpu cortex-a15 \ >> -device virtio-blk-device,drive=foo \ >> -drive if=none,file=arm-wheezy.img,id=foo \ >> -m 2048 -serial stdio >> >> Note that there is no earlyprintk via the PL011 because >> there's no defined device tree binding for "hey, here >> is your earlyprintk UART". > > Last call: anybody got any comments on mach-virt? > Otherwise I'm planning to put it into a pull request > and it'll go into qemu 1.7 as an "experimental" status > platform. > > -- PMM > Thumbs up from me testing on Arndale. My only issue is that virt and vexpress-a15 add virtio-mmio devices in the opposite order to each other, for the same set of -device command line arguments. It would avoid future headaches if we could have these behave the same. My preference would be for the virt behaviour, as the -device order matches the order in which the guest Linux kernel adds them to /dev (for virtio-blk-devices at least). Cheers, Tom _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
