qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 4/8] Revert "vl: Fix to create migration object before block backends again"
Date: Tue,  2 Apr 2019 15:01:08 +0200	[thread overview]
Message-ID: <20190402130112.15142-5-armbru@redhat.com> (raw)
In-Reply-To: <20190402130112.15142-1-armbru@redhat.com>

This reverts commit e60483f2f8498ae08ae79ca4c6fb03a3317f5e1e.

Recent commit cda4aa9a5a0 moved block backend creation before machine
property evaluation.  This broke block backends registering migration
blockers.  Commit e60483f2f84 fixed it by moving migration object
creation before block backend creation.  This broke migration with
Xen.  Turns out we need to configure the accelerator before we create
the migration object so that Xen's accelerator compat properties get
applied.  Revert the flawed commit.  This fixes the Xen regression,
but brings back the block backend regression.  The next commits will
fix it again.

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20190401090827.20793-2-armbru@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
---
 vl.c | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/vl.c b/vl.c
index 24572de0bd..9b215341a3 100644
--- a/vl.c
+++ b/vl.c
@@ -4277,17 +4277,10 @@ int main(int argc, char **argv, char **envp)
         exit(0);
     }
 
-    /*
-     * Migration object can only be created after global properties
-     * are applied correctly.
-     */
-    migration_object_init();
-
     /*
      * Note: we need to create block backends before
      * machine_set_property(), so machine properties can refer to
-     * them, and after migration_object_init(), so we can create
-     * migration blockers.
+     * them.
      */
     configure_blockdev(&bdo_queue, machine_class, snapshot);
 
@@ -4305,6 +4298,12 @@ int main(int argc, char **argv, char **envp)
                      machine_class->name, machine_class->deprecation_reason);
     }
 
+    /*
+     * Migration object can only be created after global properties
+     * are applied correctly.
+     */
+    migration_object_init();
+
     if (qtest_chrdev) {
         qtest_init(qtest_chrdev, qtest_log, &error_fatal);
     }
-- 
2.17.2

  parent reply	other threads:[~2019-04-02 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 13:01 [Qemu-devel] [PULL 0/8] Miscellaneous patches for 2019-04-02 Markus Armbruster
2019-04-02 13:01 ` [Qemu-devel] [PULL 1/8] vl: Fix error location of positional arguments Markus Armbruster
2019-04-02 13:01 ` [Qemu-devel] [PULL 2/8] qapi/migration.json: Fix ColoStatus member last_mode's version Markus Armbruster
2019-04-02 13:01 ` [Qemu-devel] [PULL 3/8] qapi/migration.json: Rename COLOStatus last_mode to last-mode Markus Armbruster
2019-04-02 13:01 ` Markus Armbruster [this message]
2019-04-02 13:01 ` [Qemu-devel] [PULL 5/8] Revert "migration: move only_migratable to MigrationState" Markus Armbruster
2019-04-02 13:01 ` [Qemu-devel] [PULL 6/8] migration: Support adding migration blockers earlier Markus Armbruster
2019-04-02 13:01 ` [Qemu-devel] [PULL 7/8] vl: Document dependencies hiding in global and compat props Markus Armbruster
2019-04-02 13:01 ` [Qemu-devel] [PULL 8/8] accel: Unbreak accelerator fallback Markus Armbruster
2019-04-02 13:56 ` [Qemu-devel] [PULL 0/8] Miscellaneous patches for 2019-04-02 Peter Maydell

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=20190402130112.15142-5-armbru@redhat.com \
    --to=armbru@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 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).