Activity log for bug #719448

Date Who What changed Old value New value Message
2011-02-15 17:17:30 Deric Sullivan bug added bug
2011-02-17 16:57:49 Serge Hallyn qemu-kvm (Ubuntu): status New Confirmed
2011-02-17 17:03:24 Serge Hallyn qemu-kvm (Ubuntu): importance Undecided Low
2011-02-17 17:04:46 Serge Hallyn qemu-kvm (Ubuntu): importance Low High
2011-02-17 17:06:25 Serge Hallyn qemu-kvm (Ubuntu): importance High Low
2011-02-17 17:51:31 Serge Hallyn branch linked lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/fix-boot-once
2011-02-17 17:57:16 Serge Hallyn qemu-kvm (Ubuntu): status Confirmed In Progress
2011-02-17 17:57:22 Serge Hallyn qemu-kvm (Ubuntu): assignee Serge Hallyn (serge-hallyn)
2011-02-17 18:04:23 Serge Hallyn attachment added Tarfile containing amd64 debs of proposed package fixing this bug https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/719448/+attachment/1856408/+files/debs.tgz
2011-02-17 18:05:30 Serge Hallyn qemu-kvm (Ubuntu): status In Progress Fix Released
2011-02-17 18:05:52 Serge Hallyn nominated for series Ubuntu Lucid
2011-02-17 21:14:44 Serge Hallyn description 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 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.
2011-02-17 21:20:19 Serge Hallyn nominated for series Ubuntu Maverick
2011-02-17 21:21:29 Serge Hallyn description 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. 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.
2011-02-17 21:22:29 Serge Hallyn description 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. 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 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.
2011-02-17 21:22:51 Serge Hallyn bug added subscriber Serge Hallyn
2011-02-17 21:23:06 Serge Hallyn bug added subscriber Ubuntu Stable Release Updates Team
2011-04-30 15:15:48 Clint Byrum bug task added qemu-kvm (Ubuntu Lucid)
2011-04-30 15:15:58 Clint Byrum bug task added qemu-kvm (Ubuntu Maverick)
2011-04-30 15:16:10 Clint Byrum qemu-kvm (Ubuntu Lucid): status New Confirmed
2011-04-30 15:16:13 Clint Byrum qemu-kvm (Ubuntu Maverick): status New Confirmed
2011-05-03 05:39:56 Martin Pitt qemu-kvm (Ubuntu Lucid): status Confirmed Fix Committed
2011-05-03 05:39:59 Martin Pitt bug added subscriber SRU Verification
2011-05-03 05:40:03 Martin Pitt tags verification-needed
2011-05-03 05:42:10 Martin Pitt qemu-kvm (Ubuntu Maverick): status Confirmed Fix Committed
2011-05-03 06:27:18 Launchpad Janitor branch linked lp:ubuntu/maverick-proposed/qemu-kvm
2011-05-03 06:27:21 Launchpad Janitor branch linked lp:ubuntu/lucid-proposed/qemu-kvm
2011-05-04 05:37:58 Martin Pitt tags verification-needed verification-done verification-needed
2011-05-17 04:42:29 Launchpad Janitor qemu-kvm (Ubuntu Lucid): status Fix Committed Fix Released
2011-05-17 07:29:23 Martin Pitt tags verification-done verification-needed verification-needed
2011-09-19 21:46:12 Ubuntu Foundations Team Bug Bot tags verification-needed testcase verification-needed
2014-12-03 08:17:35 Rolf Leggewie qemu-kvm (Ubuntu Maverick): status Fix Committed Won't Fix