From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cnplH-0003kK-E7 for qemu-devel@nongnu.org; Tue, 14 Mar 2017 12:57:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cnplE-00023X-D2 for qemu-devel@nongnu.org; Tue, 14 Mar 2017 12:57:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39042) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cnplE-00022V-7A for qemu-devel@nongnu.org; Tue, 14 Mar 2017 12:57:24 -0400 Message-ID: <1489510640.8844.18.camel@redhat.com> From: Gerd Hoffmann Date: Tue, 14 Mar 2017 17:57:20 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Janne Huttunen Cc: qemu-devel@nongnu.org Hi, > - Does this approach make sense? Any better ideas? What is the use case? Sometimes I'm wondering why we actually need the "once" thing. Looks like people use it for installs, but I fail to see why. I usually configure my guests with hard disk as bootindex=3D1 and install media (cdrom or net) as bootindex=3D2. In case the hard disk is blank it automatically falls back to the second and boots the installer, and when the installer is finished the hard disk isn't blank any more and the just installed system gets booted ... cheers, Gerd