From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rikiya Ayukawa Subject: [PATCH] Rename device backend value when xm save/migrate Date: Fri, 07 Aug 2009 12:01:49 +0900 Message-ID: <4A7B991D.6090500@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------040203010501020301070701" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --------------040203010501020301070701 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Hi all, The Xend has a problem that it often fails to restore/migrate a PV domain whose device backends are partly a driver domain. Because a checkpoint of the PV domain has device backend value as domain id, you can restore/migrate the PV domain only when a driver domain is the same id as device backend value in the checkpoint. I attached a patch to fix it by renaming device backend value in a checkpoint from domain id to domain name when xm save/migrate. This patch doesn't rename device backend value if the value is 0, which is Domain-0, so the checkpoint format is compatible if you use only Domain-0 as device backend. Signed-off-by: Rikiya Ayukawa Diffstat: XendCheckpoint.py | 14 ++++++++++++++ 1 file changed, 14 insertions(+) Best Regards, -- Rikiya Ayukawa --------------040203010501020301070701 Content-Type: text/plain; name="rename-device-backend-value.patch" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="rename-device-backend-value.patch" ZGlmZiAtciA2OGU4YjgzNzkyNDQgdG9vbHMvcHl0aG9uL3hlbi94ZW5kL1hlbmRDaGVja3Bv aW50LnB5Ci0tLSBhL3Rvb2xzL3B5dGhvbi94ZW4veGVuZC9YZW5kQ2hlY2twb2ludC5weQlT dW4gQXVnIDAyIDEzOjQzOjE1IDIwMDkgKzAxMDAKKysrIGIvdG9vbHMvcHl0aG9uL3hlbi94 ZW5kL1hlbmRDaGVja3BvaW50LnB5CVRodSBBdWcgMDYgMTc6MDI6MjMgMjAwOSArMDkwMApA QCAtNjYsNiArNjYsOCBAQAogCiAKIGRlZiBzYXZlKGZkLCBkb21pbmZvLCBuZXR3b3JrLCBs aXZlLCBkc3QsIGNoZWNrcG9pbnQ9RmFsc2UsIG5vZGU9LTEpOgorICAgIGZyb20geGVuLnhl bmQgaW1wb3J0IFhlbmREb21haW4KKwogICAgIHRyeToKICAgICAgICAgaWYgbm90IG9zLnBh dGguaXNkaXIoIi92YXIvbGliL3hlbiIpOgogICAgICAgICAgICAgb3MubWFrZWRpcnMoIi92 YXIvbGliL3hlbiIpCkBAIC04MCw2ICs4MiwxOCBAQAogICAgIGlmIG5vZGUgPiAtMToKICAg ICAgICAgaW5zZXJ0X2FmdGVyKHN4cHJlcCwndmNwdXMnLFsnbm9kZScsIHN0cihub2RlKV0p CiAKKyAgICBmb3IgZGV2aWNlX3N4cCBpbiBzeHAuY2hpbGRyZW4oc3hwcmVwLCAnZGV2aWNl Jyk6CisgICAgICAgIGJhY2tlbmQgPSBzeHAuY2hpbGQoZGV2aWNlX3N4cFsxXSwgJ2JhY2tl bmQnKQorICAgICAgICBpZiBiYWNrZW5kID09IE5vbmU6CisgICAgICAgICAgICBjb250aW51 ZQorICAgICAgICBia2RvbWluZm8gPSBYZW5kRG9tYWluLmluc3RhbmNlKCkuZG9tYWluX2xv b2t1cF9ucihiYWNrZW5kWzFdKQorICAgICAgICBpZiBia2RvbWluZm8gPT0gTm9uZToKKyAg ICAgICAgICAgIHJhaXNlIFhlbmRFcnJvcigiQ291bGQgbm90IGZpbmQgYmFja2VuZDogJXMi ICUgYmFja2VuZFsxXSkKKyAgICAgICAgaWYgYmtkb21pbmZvLmdldERvbWlkKCkgPT0gWGVu ZERvbWFpbi5ET00wX0lEOgorICAgICAgICAgICAgIyBTa2lwIGZvciBjb21wYXRpYmlsaXR5 IG9mIGNoZWNrcG9pbnQgZGF0YSBmb3JtYXQKKyAgICAgICAgICAgIGNvbnRpbnVlCisgICAg ICAgIGJhY2tlbmRbMV0gPSBia2RvbWluZm8uZ2V0TmFtZSgpCisgICAgICAgIAogICAgIGNv bmZpZyA9IHN4cC50b19zdHJpbmcoc3hwcmVwKQogCiAgICAgZG9tYWluX25hbWUgPSBkb21p bmZvLmdldE5hbWUoKQo= --------------040203010501020301070701 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --------------040203010501020301070701--