From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm Date: Sun, 17 Aug 2014 10:44:29 +0200 Message-ID: <53F06B6D.7050103@redhat.com> References: <20140812191723.GI12871@thunk.org> <53EB1859.6030800@zytor.com> <20140813143209.GD6437@thunk.org> <53EBA435.3020207@zytor.com> <20140813182219.GE6437@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To: Andy Lutomirski , Theodore Ts'o , "H. Peter Anvin" , kvm list , "linux-kernel@vger.kernel.org" , Kees Cook , X86 ML , Daniel Borkmann , Srivatsa Vaddagiri , Raghavendra K T , Gleb Natapov , Bandan Das , Andrew Honig , KY Srinivasan Return-path: Received: from mail-wg0-f51.google.com ([74.125.82.51]:42569 "EHLO mail-wg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751092AbaHQIog (ORCPT ); Sun, 17 Aug 2014 04:44:36 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Il 13/08/2014 20:33, Andy Lutomirski ha scritto: > As for doing arch_random_init after clone/migration, I think we'll > need another KVM extension for that, since, AFAIK, we don't actually > get notified that we were cloned or migrated. That will be > nontrivial. Maybe we can figure that out at KS, too. Migration doesn't need an arch_random_init, only cloning does. MS has an ACPI-based specification for this they call the "VM Generation ID", which QEMU should be implementing it sooner rather than later. In Linux we could add a generic notifier, and an x86 platform driver that implements the VM Generation ID specification and invokes the notifier. http://go.microsoft.com/fwlink/p/?LinkID=260709 (warning, .docx ahead) KY, would you be interested in looking at this? Paolo