All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Target vs architecture for QEMU binary
Date: Tue, 8 Sep 2015 15:37:02 +0100	[thread overview]
Message-ID: <20150908143702.GG4307@redhat.com> (raw)
In-Reply-To: <1441718858.14506.1.camel@redhat.com>

On Tue, Sep 08, 2015 at 03:27:38PM +0200, Andrea Bolognani wrote:
> Hi,
> 
> at the moment, libvirt is using some ad-hoc logic to allow
> i686 guests to run on qemu-system-x86_64 (by using the CPU
> model qemu32); in all other cases, it's assumed that a $arch
> guest needs qemu-system-$arch to run.
> 
> This is causing a problem right now with ppc64le guests
> because, even though qemu-system-ppc64 is perfectly capable
> of running them, libvirt will refuse to.

Is there a bug report somewhere for that, because libvirt
already has code in virQEMUCapsFindBinaryForArch() which
forces it to look at qemu-system-ppc64 when asked to use
ppc64le, so I'd expect it to already work.

> We want to change the logic so that it reflects the actual
> capabilities of the QEMU binary, but AFAICT there isn't eg.
> a QMP command we can use to query the binary for the list
> of architectures it implements.
> 
> Am I missing something? Is such an interface available?

We have a bit of a chicken and egg problem, because to query
QEMU for capabilities, you already have to know what system
emulator binary is required for the architeture you want to
run.

> Failing that, we'll have to map QEMU targets with implemented
> guest architectures inside libvirt, in which case it would be
> great if you could point me towards either some up-to-date
> documentation or a reliable way to extract the information
> myself.

The various rules in virQEMUCapsFindBinaryForArch() already
try todo a suitable mapping

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2015-09-08 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 13:27 [Qemu-devel] Target vs architecture for QEMU binary Andrea Bolognani
2015-09-08 14:37 ` Daniel P. Berrange [this message]
2015-09-08 15:34   ` Andrea Bolognani
2015-09-08 15:47     ` Daniel P. Berrange
2015-09-09  8:17       ` Andrea Bolognani
2015-09-09 14:43         ` Daniel P. Berrange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150908143702.GG4307@redhat.com \
    --to=berrange@redhat.com \
    --cc=abologna@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.