Does anyone have a quick overview of $SUBJECT?
In particular:
I cannot get any Fedora kernels to boot on the latest qemu, unless I use -M vexpress-a{9,15}. Has support for -M versatilepb been dropped?
vexpress-a{9,15} doesn't support PCI, which means it doesn't support virtio (especially virtio-serial) which makes it useless for libguestfs. Does any qemu model support virtio-serial? Does any qemu model support PCI? What, if anything, is the status of virt-mmio?
Can't we just add PCI to the qemu vexpress model, even if the real hardware doesn't have it? (And does it matter what real hardware supports? Can't we just define an uber-ARM-qemu-model that supports everything?)
Rich.
I don't know if this will help. Last time I ran arm on a vm, you had to run a script to actually get it to work, which parsed out and remapped a few things then it broke on F17. I have been meaning to try again. I really like the 9p stuff, btw. :)
Some of the newer cortex A-15's have serial/pci-e support. Here is the "howto" for the freescale QorIQ platform.
http://www.freescale.com/infocenter/index.jsp?topic=%2FQORIQSDK%2F2888263.ht...
You will probably have to reroll it though (which isn't exactly what you are looking for..)
________________________________ From: Richard W.M. Jones rjones@redhat.com To: arm@lists.fedoraproject.org Sent: Thursday, December 27, 2012 3:17 PM Subject: [fedora-arm] Booting Fedora kernels on qemu, and the current state of emulated virtio/PCI
Does anyone have a quick overview of $SUBJECT?
In particular:
I cannot get any Fedora kernels to boot on the latest qemu, unless I use -M vexpress-a{9,15}. Has support for -M versatilepb been dropped?
vexpress-a{9,15} doesn't support PCI, which means it doesn't support virtio (especially virtio-serial) which makes it useless for libguestfs. Does any qemu model support virtio-serial? Does any qemu model support PCI? What, if anything, is the status of virt-mmio?
Can't we just add PCI to the qemu vexpress model, even if the real hardware doesn't have it? (And does it matter what real hardware supports? Can't we just define an uber-ARM-qemu-model that supports everything?)
Rich.
Just reporting, Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-arm Importing GPG key 0xA4D647E9: Userid : "Fedora Secondary Arch (18) fedora@fedoraproject.org" Fingerprint: 62d6 986a 2639 cf2e 3790 ee45 68dc d160 a4d6 47e9 Package : fedora-release-18-0.8.noarch (@anaconda-0) From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-arm Is this ok [y/N]: y
Package libgudev1-195-13.fc18.armv5tel.rpm is not signed [root@kirkwood-f18-v5tel boot]#
On Sat, Dec 29, 2012 at 3:16 AM, Sean Omalley omalley_s@rocketmail.com wrote:
Just reporting, Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-arm Importing GPG key 0xA4D647E9: Userid : "Fedora Secondary Arch (18) fedora@fedoraproject.org" Fingerprint: 62d6 986a 2639 cf2e 3790 ee45 68dc d160 a4d6 47e9 Package : fedora-release-18-0.8.noarch (@anaconda-0) From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-arm Is this ok [y/N]: y
Package libgudev1-195-13.fc18.armv5tel.rpm is not signed [root@kirkwood-f18-v5tel boot]#
It's not unusual, package signing is a manual process that requires someone to unlock a signing key so we sometimes autopush without signing all packages to get updates out, you can either use --nogpg or exclude the offending packages until the signing gets caught up.
Peter
Hi Richard,
There are older models of "versatile" that are not the same, which is the cause of the macbine selection oddity. I see your points on PCI and will followup next year.
Jon.
-
Jon Masters -
Peter Robinson -
Richard W.M. Jones -
Sean Omalley