Re: network boot always enabled with 0.15.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 11, 2011 at 11:57:28AM +0000, Dietmar Maurer wrote:
> > Agree. noboot sounds optimal, but also requires more codding that other
> > options (sigh, isn't it always this way?). But how do we have it for disks?
> 
> -drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]
>        [,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off]
>        [,cache=writethrough|writeback|none|unsafe][,format=f]
>        [,serial=s][,addr=A][,id=name][,aio=threads|native]
>        [,readonly=on|off][,boot=on|off]
> 
> I thought 'boot=off' would do exactly that.
> 

No, this boot= option is deprecated too. AFAIK boot=off does (and always
did) nothing.  boot=on tells qemu to boot from the disk using extboot
option rom. This was needed to boot from virtio disks. Now SeaBIOS can
boot from virtio disk natively, so extboot no longer needed. But due
to the ways BIOS boot specification is written only one disk can be
bootable in the system, so if one disk has bootindex specified other
disks will not participate in the boot even if the disk with bootindex
specified is not bootable.

--
			Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux