For posterity - yes, 'priority' is not a valid option :) ** Description changed:
Binary package hint: qemu-kvm Package: qemu-kvm The "once" parameter does not seem to work with the "-boot" option. To reproduce: create an image file to be used as a hard disk: qemu-img create test-img 1G Starting a VM guest using "once" + "order" ignores the "once": /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot order=c,once=n Starting a VM guest using "once" ignores the "once": /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot once=n Starting a VM guest without "once" works fine: /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot order=n # lsb_release -rd Description: Ubuntu 10.04.2 LTS Release: 10.04 # apt-cache policy qemu-kvm qemu-kvm: - Installed: 0.12.3+noroms-0ubuntu9.3 - Candidate: 0.12.3+noroms-0ubuntu9.3 + Installed: 0.12.3+noroms-0ubuntu9.3 + Candidate: 0.12.3+noroms-0ubuntu9.3 + + Thanks for the help, Deric - Thanks for the help, Deric + SRU justification: + + Impact: users (and management software) cannot use a single qemu command + to boot the first time from install media (network or cdrom) and + afterward from hard disk. + + How addressed: the bug is fixed upstream. The relevant code was patched + to match the upstream code. + + Patch: see the associated bzr tree + + To reproduce: Install a valid OS, say lucid, on disk.img Download a + valid ISO, say natty-server-amd64.iso. Then run: + + kvm -hda disk.img -cdrom natty-server-amd64.so -boot once=d + + It will boot from hard disk + + 5. Regression potential: The code which was updated affects only the + 'once' and 'order' options to the '-boot' flag. Regressions could cause + advanced users to boot from the wrong device. For that matter, any + users who are mis-using these flags could end up with different + (correct) results. ** Description changed: Binary package hint: qemu-kvm Package: qemu-kvm The "once" parameter does not seem to work with the "-boot" option. To reproduce: create an image file to be used as a hard disk: qemu-img create test-img 1G Starting a VM guest using "once" + "order" ignores the "once": /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot order=c,once=n Starting a VM guest using "once" ignores the "once": /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot once=n Starting a VM guest without "once" works fine: /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot order=n # lsb_release -rd Description: Ubuntu 10.04.2 LTS Release: 10.04 # apt-cache policy qemu-kvm qemu-kvm: Installed: 0.12.3+noroms-0ubuntu9.3 Candidate: 0.12.3+noroms-0ubuntu9.3 Thanks for the help, Deric - SRU justification: Impact: users (and management software) cannot use a single qemu command to boot the first time from install media (network or cdrom) and afterward from hard disk. How addressed: the bug is fixed upstream. The relevant code was patched to match the upstream code. Patch: see the associated bzr tree To reproduce: Install a valid OS, say lucid, on disk.img Download a valid ISO, say natty-server-amd64.iso. Then run: kvm -hda disk.img -cdrom natty-server-amd64.so -boot once=d It will boot from hard disk 5. Regression potential: The code which was updated affects only the 'once' and 'order' options to the '-boot' flag. Regressions could cause advanced users to boot from the wrong device. For that matter, any users who are mis-using these flags could end up with different (correct) results. ** Description changed: Binary package hint: qemu-kvm Package: qemu-kvm The "once" parameter does not seem to work with the "-boot" option. To reproduce: create an image file to be used as a hard disk: qemu-img create test-img 1G Starting a VM guest using "once" + "order" ignores the "once": /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot order=c,once=n Starting a VM guest using "once" ignores the "once": /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot once=n Starting a VM guest without "once" works fine: /usr/bin/qemu-system-x86_64 -hda test-img -m 4G -smp 2 -enable-kvm -vnc 127.0.0.1:1 -name test-vm -boot order=n # lsb_release -rd Description: Ubuntu 10.04.2 LTS Release: 10.04 # apt-cache policy qemu-kvm qemu-kvm: Installed: 0.12.3+noroms-0ubuntu9.3 Candidate: 0.12.3+noroms-0ubuntu9.3 Thanks for the help, Deric + ================================= SRU justification: + ================================= Impact: users (and management software) cannot use a single qemu command to boot the first time from install media (network or cdrom) and afterward from hard disk. How addressed: the bug is fixed upstream. The relevant code was patched to match the upstream code. Patch: see the associated bzr tree - To reproduce: Install a valid OS, say lucid, on disk.img Download a - valid ISO, say natty-server-amd64.iso. Then run: + TEST CASE: Install a valid OS, say lucid, on disk.img Download a valid + ISO, say natty-server-amd64.iso. Then run: kvm -hda disk.img -cdrom natty-server-amd64.so -boot once=d It will boot from hard disk 5. Regression potential: The code which was updated affects only the 'once' and 'order' options to the '-boot' flag. Regressions could cause advanced users to boot from the wrong device. For that matter, any users who are mis-using these flags could end up with different (correct) results. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/719448 Title: The "once" parameter does not work with "-boot" -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs