From: Gleb Natapov <gleb@redhat.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: network boot always enabled with 0.15.0
Date: Thu, 11 Aug 2011 13:50:45 +0300 [thread overview]
Message-ID: <20110811105045.GY4404@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F753777727D@lisa.maurer-it.com>
On Thu, Aug 11, 2011 at 10:33:47AM +0000, Dietmar Maurer wrote:
> > > Also, I think the behavior was different with earlier versions.
> > Yes, it was. The behaviour changed when bootindex was introduced. I think it
> > should be easy to switch it back to what it was for -boot option, but -boot
> > is/should be deprecated in favor of bootindex anyway.
> > Implementing opt out from boot process for bootindex is doable but more
> > involving.
>
> But I found no way to disable booting a network device using bootindex - you can
> just set the order with that.
>
Yes. It has to be implemented. Currently BIOS assigns default boot
priority for all devices that do not have bootindex specified. So
bootindex only influence the order in which BIOS will try devices
for booting. This way if you have 10 devices you want BIOS to try to boot
from in no particular order and one device that you want it to try first
you do not need to specify 11 bootindex parameters, but only one (or if
you do not care about the order you don't need to specify anything). We
can change BIOS to only boot from devices that has bootindex, but then
you will have to always specify it for all/most devices, or we can
add noboot device property, but that will require changes on qemu side
too.
> > > For example, if I set 'boot order=d' (boot from cdrom) and there is no cdrom in
> > the drive slot. Then the VM will boot from the network an our windows
> > installation server (RIS/WDS) will automatically trash all data on the VM disk.
> > That is quite dangerous.
> > >
> > One can argue that having such brokenly configured server in your network is
> > dangerous anyway. What about physical computer that can be trashed before
> > you even realize you had to disable network booting in the BIOS?
>
> All hardware I know does not boot from network if I have disabled it - that's exactly the point!
With RIS/WDS server like above you may find out that you had to disable
network booting to later. I am not arguing that you can't disable network
booting on real HW, I am claiming that having such server in the network
is not good idea regardless.
> I want to disable network boot, so how can I do that?
>
The only way you can do that currently is to use bios.bin from qemu-0.14.
The problem is mostly in the BIOS, not qemu.
--
Gleb.
next prev parent reply other threads:[~2011-08-11 10:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 8:55 network boot always enabled with 0.15.0 Dietmar Maurer
2011-08-11 9:05 ` Gleb Natapov
2011-08-11 9:12 ` Dietmar Maurer
2011-08-11 9:38 ` Gleb Natapov
2011-08-11 9:56 ` Dietmar Maurer
2011-08-11 10:25 ` Gleb Natapov
2011-08-11 10:33 ` Dietmar Maurer
2011-08-11 10:50 ` Gleb Natapov [this message]
2011-08-11 11:29 ` Dietmar Maurer
2011-08-11 11:48 ` Gleb Natapov
2011-08-11 11:57 ` Dietmar Maurer
2011-08-11 12:06 ` Gleb Natapov
2011-08-11 13:57 ` Dietmar Maurer
2011-08-11 13:59 ` Gleb Natapov
2011-08-11 21:37 ` Michael Tokarev
2011-08-11 16:59 ` Gerd Hoffmann
2011-08-12 5:08 ` Dietmar Maurer
2011-08-12 7:10 ` Dietmar Maurer
2011-08-11 10:13 ` Dietmar Maurer
2011-08-11 10:26 ` Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110811105045.GY4404@redhat.com \
--to=gleb@redhat.com \
--cc=dietmar@proxmox.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.