qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Don Slutz <dslutz@verizon.com>
Cc: xen-devel@lists.xensource.com,
	"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, "Anthony Liguori" <aliguori@amazon.com>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v5 2/3] pc & q35: Add new machine opt max-ram-below-4g
Date: Wed, 18 Jun 2014 11:52:42 +0200	[thread overview]
Message-ID: <1403085162.13406.1.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <53A0800B.2070107@terremark.com>

  Hi,

> > IMO xen should use a versioned machine type to make live migration more
> > reliable.  IIRC this was discussed anyway for other reasons (see
> > xen-platform-pci discussions, picking pc-i440fx-1.6 IIRC).
> 
> That is happening as far as I know and does not directly impact this
> patch set.
> 
> >    That should
> > also make qemu use the memory layout expected by old xen.
> 
> Currently xen just ignores the memory layout that QEMU sets up
> and does it's own way.  So no, this does not make QEMU use the
> memory layout expected by old xen.

Why?  "-M pc-i440fx-1.6" will make qemu use the same memory layout it
used to have before gbalign support was added.  And that should match
what old xen versions are setting up ...

cheers,
  Gerd

  reply	other threads:[~2014-06-18  9:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 17:52 [Qemu-devel] [PATCH v5 0/3] Add max-ram-below-4g (was Add pci_hole_min_size machine option) Don Slutz
2014-06-06 17:52 ` [Qemu-devel] [PATCH v5 1/3] xen-hvm: Fix xen_hvm_init() to adjust pc memory layout Don Slutz
2014-06-06 17:52 ` [Qemu-devel] [PATCH v5 2/3] pc & q35: Add new machine opt max-ram-below-4g Don Slutz
2014-06-08 15:40   ` Michael S. Tsirkin
2014-06-09 14:20     ` Don Slutz
2014-06-09 14:38       ` Michael S. Tsirkin
2014-06-09 15:10         ` Marcel Apfelbaum
2014-06-09 15:37           ` Igor Mammedov
2014-06-09 17:33             ` Marcel Apfelbaum
2014-06-09 20:03               ` Don Slutz
2014-06-09 19:13         ` Don Slutz
2014-06-10  7:36           ` Gerd Hoffmann
2014-06-17 17:51             ` Don Slutz
2014-06-18  9:52               ` Gerd Hoffmann [this message]
2014-06-17 18:22   ` Michael S. Tsirkin
2014-06-17 18:44     ` Don Slutz
2014-06-17 19:43       ` Michael S. Tsirkin
2014-06-17 20:05         ` Michael S. Tsirkin
2014-06-17 20:08         ` [Qemu-devel] [Xen-devel] " Konrad Rzeszutek Wilk
2014-06-17 20:17           ` Michael S. Tsirkin
2014-06-18 13:28             ` Slutz, Donald Christopher
2014-06-17 20:35           ` Pasi Kärkkäinen
2014-06-06 17:52 ` [Qemu-devel] [PATCH v5 3/3] xen-hvm: Pass is_default to xen_hvm_init Don Slutz
2014-06-08 15:24   ` Michael S. Tsirkin
2014-06-09 14:25     ` Don Slutz
2014-06-09 14:39       ` Michael S. Tsirkin
2014-06-08 15:42   ` Michael S. Tsirkin

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=1403085162.13406.1.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=dslutz@verizon.com \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.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).