xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Steven Haigh <netwiz@crc.id.au>
Subject: Re: [BUG?] qemuu only built with i386-softmmu
Date: Tue, 9 Feb 2016 16:01:40 +0000	[thread overview]
Message-ID: <1455033700.19857.93.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1602091542110.27008@kaball.uk.xensource.com>

On Tue, 2016-02-09 at 15:49 +0000, Stefano Stabellini wrote:
> On Fri, 5 Feb 2016, Ian Campbell wrote:
> > On Fri, 2016-02-05 at 20:57 +1100, Steven Haigh wrote:
> > > 
> > > > On thing I was sure on (so didn't write) is whether the second
> > > > paragraph
> > > > could have an extra sentence:
> > > > 
> > > >     If you are using a distro supplied QEMU then the qemu-system-
> > > > x86_64
> > > >     could also be used, but it makes no practical difference to the
> > > >     functionality of the system.
> > > > 
> > > > I wasn't sure if that was true (I suspect it is) and in any case I
> > > > think
> > > > various bits of libxl etc will look for qemu-system-i386 in various
> > > > paths
> > > > so a user would need to try reasonably hard to do so by giving an
> > > > explicit
> > > > path and there is no real reason to do so maybe better not to muddy
> > > > the
> > > > waters?
> > > 
> > > Maybe go along the lines of:
> > > 
> > > "There is no practical difference between qemu-system-i386 and
> > > qemu-system-x86_64 therefore both can be interchanged freely."
> > 
> > Thanks, this is a good wording if it is indeed true (I'll wait for
> > confirmation of that before I write it on the wiki).
>  
> Although it is technically true, within QEMU they are two different
> build targets (i386-softmmu and x86_64-softmmu) and we only tests
> i386-softmmu in OSSTest. It is possible that qemu-system-x86_64 might
> break due to upstream changes while qemu-system-i386 could still work
> and we might not notice. 
> 
> I would write:
> 
> "There is no practical difference between qemu-system-i386 and
> qemu-system-x86_64, they should be interchangeable. However only
> qemu-system-i386 is regularly tested by OSSTest".

Done in the wiki as above but I said "...by XenProject (via osstest)".

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-02-09 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 21:09 [BUG?] qemuu only built with i386-softmmu Steven Haigh
2016-02-05  9:51 ` Ian Campbell
2016-02-05  9:57   ` Steven Haigh
2016-02-05 10:07     ` Ian Campbell
2016-02-09 15:49       ` Stefano Stabellini
2016-02-09 16:01         ` Ian Campbell [this message]

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=1455033700.19857.93.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=netwiz@crc.id.au \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).