From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Nested SVM and migration Date: Sat, 20 Feb 2010 09:14:06 -1000 Message-ID: <4B80347E.7000003@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: Joerg Roedel , Avi Kivity , kvm Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4165 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754207Ab0BTTOK (ORCPT ); Sat, 20 Feb 2010 14:14:10 -0500 Sender: kvm-owner@vger.kernel.org List-ID: Perhaps I am misunderstanding, but I don't see how nested SVM instances can be properly migrated. How does one extract and rebuild the nested hsave control block? If it isn't done already, one possible way to add it as an extension might be to represent the data as additional MSRs which are saved and restored with migration. Actually, looking deeper, there doesn't even appear to be any way to export the nested CPU data at all, meaning basic features like suspending and restoring the VM are not possible. Is there any plan to make it work in the near future? I'm not complaining; if my understanding is correct, this actually makes my current task easier. Thanks, Zach