Skip to contentSkip to conversation

qemu-kvm 0.15.0 boot order not working

DISCUSSION Peter Lieven 3 participants 5 messages Aug 29, 2011 KVM

lore
Share & tools
lore
#0 lore raw

Hi,

when I specify something like

qemu -boot order=dc -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

or

qemu -boot order=n -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

with qemu-kvm 0.15.0

it will always directly boot from the hardrive and not from cdrom or network. is this on purpose? the behaviour was different in earlier versions.
If i omit the boot=yes in the drive specification the "-boot order" parameter is working as expected.

Peter

#1 lore raw
Quoted 10 lines · Peter Lieven

Hi,

when I specify something like

qemu -boot order=dc -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

or

qemu -boot order=n -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

Quoted 8 lines

with qemu-kvm 0.15.0

it will always directly boot from the hardrive and not from cdrom or network.
is this on purpose? the behaviour was different in earlier versions. If i omit the boot=yes in the drive specification the "-boot order" parameter is working
as expected.

This is the qemu doc file:
http://qemu.weilnetz.de/qemu-doc.html

and this is qemu-kvm man page:
http://linux.die.net/man/1/qemu-kvm

I have never seen the boot=yes as an option to the argument -drive. I have also checked on previous versions of qemu and I haven't seen it so I'm puzzled why it should have worked in the first instance.

[ BTW this question would be better suited to a qemu-users mailing list or forum... if there was one... ]

Signature · 7 lines
Ottavio


A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
#2 lore raw
Quoted 22 lines · Ottavio
Quoted 10 lines · Peter Lieven

Hi,

when I specify something like

qemu -boot order=dc -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

or

qemu -boot order=n -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

Quoted 8 lines

with qemu-kvm 0.15.0

it will always directly boot from the hardrive and not from cdrom or network.
is this on purpose? the behaviour was different in earlier versions. If i omit the boot=yes in the drive specification the "-boot order" parameter is working
as expected.

This is the qemu doc file:
http://qemu.weilnetz.de/qemu-doc.html

Quoted 6 lines

and this is qemu-kvm man page:
http://linux.die.net/man/1/qemu-kvm

I have never seen the boot=yes as an option to the argument -drive. I have also checked on previous versions of qemu and I haven't seen it so I'm puzzled why it should have worked in the first instance.

-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]
                use 'file' as a drive image

you cannot boot e.g. from a virtio_blk device without this flag.

it seems that the if the extboot option rom is loaded the specified boot order is ignored.

peter

Quoted 4 lines

[ BTW this question would be better suited to a qemu-users mailing list or forum... if there was one... ]

#3 lore raw
Quoted 29 lines · Peter Lieven
Quoted 22 lines · Ottavio
Quoted 10 lines · Peter Lieven

Hi,

when I specify something like

qemu -boot order=dc -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

or

qemu -boot order=n -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

Quoted 8 lines

with qemu-kvm 0.15.0

it will always directly boot from the hardrive and not from cdrom or network.
is this on purpose? the behaviour was different in earlier versions. If i omit the boot=yes in the drive specification the "-boot order" parameter is working
as expected.

This is the qemu doc file:
http://qemu.weilnetz.de/qemu-doc.html

Quoted 6 lines

and this is qemu-kvm man page:
http://linux.die.net/man/1/qemu-kvm

I have never seen the boot=yes as an option to the argument -drive. I have also checked on previous versions of qemu and I haven't seen it so I'm puzzled why it should have worked in the first instance.

Quoted 8 lines

-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]
                use 'file' as a drive image

you cannot boot e.g. from a virtio_blk device without this flag.

It is possible since 0.13 or 0.14. Actually it's seabios thing, it got real support for virtio drives awhile back, before it was indeed possible only using boot=on drive option.

Quoted 2 lines

it seems that the if the extboot option rom is loaded the specified boot order is ignored.

And yes this is the case. the -boot tells bios about normal boot order, and with extboot you overwrite that. That's how booting works for stuff which is not supported by bios.

/mjt

#4 lore raw
Quoted 42 lines · Michael Tokarev
Quoted 29 lines · Peter Lieven
Quoted 22 lines · Ottavio
Quoted 10 lines · Peter Lieven

Hi,

when I specify something like

qemu -boot order=dc -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

or

qemu -boot order=n -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

Quoted 8 lines

with qemu-kvm 0.15.0

it will always directly boot from the hardrive and not from cdrom or network.
is this on purpose? the behaviour was different in earlier versions. If i omit the boot=yes in the drive specification the "-boot order" parameter is working
as expected.

This is the qemu doc file:
http://qemu.weilnetz.de/qemu-doc.html

Quoted 6 lines

and this is qemu-kvm man page:
http://linux.die.net/man/1/qemu-kvm

I have never seen the boot=yes as an option to the argument -drive. I have also checked on previous versions of qemu and I haven't seen it so I'm puzzled why it should have worked in the first instance.

Quoted 8 lines

-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]
                 use 'file' as a drive image

you cannot boot e.g. from a virtio_blk device without this flag.

It is possible since 0.13 or 0.14. Actually it's seabios thing, it got real support for virtio drives awhile back, before it was indeed possible only using boot=on drive option.

Quoted 5 lines
Quoted 2 lines

it seems that the if the extboot option rom is loaded the specified boot order is ignored.

And yes this is the case. the -boot tells bios about normal boot order, and with extboot you overwrite that. That's how booting works for stuff which is not supported by bios.

i checked. it is working on qemu-kvm 0.12.5 if i take the seabios packaged with qemu 0.14.1. with this version i can boot from virtio and still use any bootorder. so there was some chance in seabios that broke this feature since in older version extboot.bin was obviously loaded when the bios tried to boot from hard drive...

peter

Quoted 2 lines

/mjt