qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: stefano.stabellini@eu.citrix.com
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] xen: make xen-platform a default device
Date: Fri, 23 May 2014 15:03:45 +0200	[thread overview]
Message-ID: <537F4731.20702@m2r.biz> (raw)

> One issue is that -M pc didn't always work with Xen. Now it does and we
> are already relying on it in libxl since
> 2bc047635b51abd41c917aa2b813211ee0de2c38. It is safe because all QEMU
> releases from 1.6 onward work well with Xen and -M pc. Older QEMU
> releases are considered ancient and unmaintained. This is what I was
> referring to in my last reply. I really meant "we should move away from
> xenfv and use a pc.* machine that does not create xen-platform by
> default".
>
> As you say the other issue is the version of the pc machine, especially
> in relation to save/restore. However since:
>
> commit 2bc047635b51abd41c917aa2b813211ee0de2c38
> Author: Anthony PERARD <address@hidden>
> Date:   Wed Nov 27 18:21:34 2013 +0000
>
>      libxl: Handle xen_platform_pci=0 case with qemu-xen.
>
> we are simply calling QEMU with -M pc if xen_platform_pci=0. I think we
> should change that too and backport the patch to 4.4. pc-i440fx-1.6
> seems like a good choice to me.

Use "-M pc" as default seems a good idea.
Use specific version maybe too.
This way the base hardware should stay the same even if updating qemu, 
is right? If yes, this should also solve possible problem like windows 
reactivation request for different hardware, right?
How about create also xl parameter to select the "pc" model?

Thanks for any reply and sorry for my bad english.

             reply	other threads:[~2014-05-23 13:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 13:03 Fabio Fantoni [this message]
2014-05-23 14:30 ` [Qemu-devel] [PATCH] xen: make xen-platform a default device Stefano Stabellini
2014-05-23 15:02   ` Fabio Fantoni
  -- strict thread matches above, loose matches on Subject: below --
2014-05-22  7:20 Gerd Hoffmann
2014-05-22  7:21 ` Michael S. Tsirkin
2014-05-22 10:57   ` Chen, Tiejun
2014-05-22 10:59     ` Michael S. Tsirkin
2014-05-22 12:11 ` Stefano Stabellini
2014-05-22 12:35   ` Michael S. Tsirkin
2014-05-22 12:53     ` Gerd Hoffmann
2014-05-22 14:00       ` Michael S. Tsirkin
2014-05-22 12:45   ` Gerd Hoffmann
2014-05-22 13:49     ` Stefano Stabellini
2014-05-22 12:50   ` Paolo Bonzini
2014-05-22 13:22     ` Gerd Hoffmann
2014-05-22 13:56       ` Stefano Stabellini
2014-05-23 10:08         ` Paul Durrant
2014-05-23 10:11           ` Stefano Stabellini
2014-05-23 10:18             ` Paul Durrant
2014-05-23 11:36               ` Stefano Stabellini
2014-05-23 11:51                 ` Paul Durrant
2014-05-22 13:55     ` Stefano Stabellini
2014-05-22 14:03       ` Paolo Bonzini

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=537F4731.20702@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=anthony.perard@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).