On 05/21/2015 07:03 PM, Cole Robinson wrote: > qemu 2.3.0 added support for enabling armv7l VMs to run on aarch64 hosts > with KVM. First patch handles the special command line bit, last two > patches are about advertising things in virsh capabilities. > > After these patches, 'virt-install --arch armv7l ...' on an aarch64 > host with new enough qemu will automatically use KVM and generate a > working config. > > Cole Robinson (3): > qemu: command: Support arm 32-on-64 KVM with -cpu aarch64=off > qemu: caps: qemu-system-aarch64 supports armv7l > qemu: caps: Advertise arm 32-on-64 KVM option > > src/qemu/qemu_capabilities.c | 57 ++++++++++++++-------- > src/qemu/qemu_capabilities.h | 1 + > src/qemu/qemu_command.c | 13 +++++ > .../qemuxml2argv-aarch64-kvm-32-on-64.args | 10 ++++ > .../qemuxml2argv-aarch64-kvm-32-on-64.xml | 35 +++++++++++++ > tests/qemuxml2argvtest.c | 9 ++++ > 6 files changed, 105 insertions(+), 20 deletions(-) > create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-aarch64-kvm-32-on-64.args > create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-aarch64-kvm-32-on-64.xml > Perhaps lost by having the tweak dir perms handling patch sneak in... Seems reasonable to me (ACK)... Should there be some way to document how this would be added/usable in the passthrough description in formatdomain? Or somewhere else? Not sure how anyone would know the magic incantation to define/use this... Even though this was posted before freeze, not 100% clear whether it's push-able for this release cycle. John -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list