From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: network boot always enabled with 0.15.0 Date: Thu, 11 Aug 2011 13:26:25 +0300 Message-ID: <20110811102625.GX4404@redhat.com> References: <24E144B8C0207547AD09C467A8259F7537776084@lisa.maurer-it.com> <20110811090522.GU4404@redhat.com> <24E144B8C0207547AD09C467A8259F75377760F0@lisa.maurer-it.com> <20110811093856.GV4404@redhat.com> <24E144B8C0207547AD09C467A8259F7537777253@lisa.maurer-it.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "kvm@vger.kernel.org" To: Dietmar Maurer Return-path: Received: from mx1.redhat.com ([209.132.183.28]:32557 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755015Ab1HKK02 (ORCPT ); Thu, 11 Aug 2011 06:26:28 -0400 Content-Disposition: inline In-Reply-To: <24E144B8C0207547AD09C467A8259F7537777253@lisa.maurer-it.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Aug 11, 2011 at 10:13:15AM +0000, Dietmar Maurer wrote: > > Then it is expected (as in "this is how code works currently"). Why would you > > want to disable network boot if other method failed? > > If I start kvm with: > > # kvm -boot order=cad > > The it tries to boot: cdrom, net, disk, floppy (dnca) > That looks like a bug. > So the boot order is completely wrong! > > But the order is correct with kvm 0.14.1 > > - Dietmar > -- Gleb.