Description of problem: qemu-system-arm has an annoying bug since forever where the -help output mentioned -no-hpet, but if you actually use this flag, qemu helpfully prints: Option no-hpet not supported for this target If you use the libvirt XML on an ARM guest: <timer name=hpet present=no> meaning "don't include an HPET device", then libvirt adds -no-hpet to the command line, and qemu-system-arm won't start up. Of course ARM has never had a High Precision Timer, and in any case we're asking not to include one. I have worked around this in libguestfs by not including this XML fragment on ARM, but this still looks like it is a bug in libvirt (and qemu of course). Version-Release number of selected component (if applicable): libvirt from git today How reproducible: 100% Steps to Reproduce: 1. Compile libvirt from git on ARM. 2. Run: ~/d/libvirt/run libguestfs-test-tool Actual results: Original error from libvirt: internal error: process exited while connecting to monitor: Option no-hpet not supported for this target [code=1 domain=10] libguestfs-test-tool: failed to launch appliance Expected results: Should probably ignore this. Additional info:
*** Bug 1066524 has been marked as a duplicate of this bug. ***
Affects multiple architectures, both arm and ppc, probably all non-x86 archs in fact.
(In reply to Richard W.M. Jones from comment #0) > I have worked around this in libguestfs by not including this > XML fragment on ARM, but this still looks like it is a bug in > libvirt (and qemu of course). I still see this problem after compiling from libguestfs-1.25.37.tar.gz on Ubuntu Trusty. Should the workaround be present in that release?
(In reply to Daniel Lipsitt from comment #3) > (In reply to Richard W.M. Jones from comment #0) > > > I have worked around this in libguestfs by not including this > > XML fragment on ARM, but this still looks like it is a bug in > > libvirt (and qemu of course). > > I still see this problem after compiling from libguestfs-1.25.37.tar.gz on > Ubuntu Trusty. Should the workaround be present in that release? The workaround is present in current libguestfs, so a newer version should be OK.
Upstream patch posted: https://www.redhat.com/archives/libvir-list/2014-April/msg00730.html
Fixed upstream: commit c3725db8d0c1035dc550959c93f8b9aeb78ec1bf Author: Ján Tomko <jtomko> CommitDate: 2014-04-18 15:01:27 +0200 Only set QEMU_CAPS_NO_HPET on x86 QEMU only supports it on x86, but we've been assuming it for all QEMUs when doing QMP capability detection. https://bugzilla.redhat.com/show_bug.cgi?id=1066145 git describe: v1.2.3-138-gc3725db Backported to v1.1.3-maint: v1.1.3.4-19-ga91c1f1