From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCHv4 15/15] Pass boot device list to firmware. Date: Thu, 18 Nov 2010 15:12:02 +0200 Message-ID: <20101118131202.GA8247@redhat.com> References: <20101116190246.GA27851@redhat.com> <20101118101827.GC7948@redhat.com> <20101118113831.GD31261@redhat.com> <20101118114504.GI7948@redhat.com> <20101118115230.GE31261@redhat.com> <20101118121605.GK7948@redhat.com> <20101118122320.GC31987@redhat.com> <20101118123708.GN7948@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Blue Swirl , qemu-devel@nongnu.org, kvm@vger.kernel.org, armbru@redhat.com, alex.williamson@redhat.com, kevin@koconnor.net To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:41076 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756849Ab0KRNMS (ORCPT ); Thu, 18 Nov 2010 08:12:18 -0500 Content-Disposition: inline In-Reply-To: <20101118123708.GN7948@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Nov 18, 2010 at 02:37:08PM +0200, Gleb Natapov wrote: > > So that's unavoidable if we think paths are correct. > > But if we know they are wrong, we are better off > > correcting them first IMO. > > > They are correct for x86. My patch set does not even tries to cover all > HW. If sparc want to use them to it better be fixed. Or if there is enough > info in the path to determine device it may choose to use it as is. Fair enough I guess. > > > But the problem exists only if migration happens in a short window > > > between start of the boot process and BIOS reading boot order string. > > > After reboot new qemu should have new BIOS. > > > > That makes it even more nasty, doesn't it? > No. Nasty as in hard to reproduce. -- MST