maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as Won't Fix.
** Changed in: qemu-kvm (Ubuntu Maverick)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
** Tags added: testcase
--
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
To manage notifications about this bug go to:
** Tags removed: verification-done
--
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
This bug was fixed in the package qemu-kvm - 0.12.3+noroms-0ubuntu9.6
---
qemu-kvm (0.12.3+noroms-0ubuntu9.6) lucid-proposed; urgency=low
* Pull in changes to vl.c from upstream to fix 'boot once=x'.
(LP: #719448)
-- Serge Hallyn serge.hal...@ubuntu.com Mon, 02 May 2011
Excerpts from Deric Sullivan's message of Fri May 13 13:52:58 UTC 2011:
Martin, thanks for the clarification on how/when the fixed package moves from
-proposed to -updates.
But is there anything else needed? I waited 10 days to be safe, and still
the package is not in -updates. It's also
Martin, thanks for the clarification on how/when the fixed package moves from
-proposed to -updates.
But is there anything else needed? I waited 10 days to be safe, and still the
package is not in -updates. It's also still listed on the Pending Ubuntu
stable release updates web page.
Thanks,
Serge Hallyn [2011-05-06 15:52 -]:
The package will be moved to lucid-updates 7 days after this bug
was marked verification-done.
More precisely, it will be moved to -updates after 7 days of being in
-proposed if it is verified at that time. The 7 days period is for
having a time to catch
Hi,
I'm trying to figure out if there is anything else that I'm supposed to
do to get this fix into lucid-updates.
When I look at the web page for Pending Ubuntu stable release updates
(at http://people.canonical.com/~ubuntu-archive/pending-sru.html;) I
see, in the lucid section, that
Hi Deric,
First, thank you for testing! Your help is much appreciated. The reason you
are seeing both verification-done and verification-needed tags is because the
Launchpad ticket is only partially tested. This is common when the same fix
has been committed for multiple distributions.
Quoting Deric Sullivan (deric.sulli...@ec.gc.ca):
Hi,
I'm trying to figure out if there is anything else that I'm supposed to
do to get this fix into lucid-updates.
I don't think so. The fix has not been verified for maverick, but it
has for lucid. And there are no other deltas between
The package will be moved to lucid-updates 7 days after this bug
was marked verification-done.
--
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
Thanks again.
Deric
On 05/06/11 15:52, Serge Hallyn wrote:
The package will be moved to lucid-updates 7 days after this bug
was marked verification-done.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
** Branch linked: lp:ubuntu/maverick-proposed/qemu-kvm
** Branch linked: lp:ubuntu/lucid-proposed/qemu-kvm
--
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
I installed the lucid proposed qemu-kvm package and the bug is fixed.
Thanks,
Deric
On 05/03/11 05:40, Martin Pitt wrote:
Accepted qemu-kvm into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
** Tags added: verification-done
--
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
Great. Thanks.
Deric
On 04/30/11 15:16, Clint Byrum wrote:
No it was not denied. I've gone ahead and accepted the bug for
lucid/maverick SRU.
** Also affects: qemu-kvm (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Maverick)
Accepted qemu-kvm into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: qemu-kvm (Ubuntu Lucid)
No it was not denied. I've gone ahead and accepted the bug for
lucid/maverick SRU.
** Also affects: qemu-kvm (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu Lucid)
Hi Serge,
Was the SRU for lucid to fix the once bug in qemu-kvm denied?
I've seen an update since you requested the SRU but it doesn't seem to
include the fix for the once bug.
Thanks,
Deric
On 02/17/11 20:41, Serge Hallyn wrote:
Quoting Deric Sullivan (deric.sulli...@ec.gc.ca):
Hm,
on a fresh install of 10.04.2 server, I did:
kvm -hda natty.img -cdrom natty-server-amd64.iso -m 1024M -smp 2 -vnc :1
-boot once=d
It proceeded to install, reboot, and then boot from hard disk.
I wonder whether this is particular to net-booting.
--
You received this bug notification
Ah, I see. If there is a valid OS on the hard drive, then it will boot
from the hard drive and ignore the 'once='.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Does not happen in natty.
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Low
** Changed in: qemu-kvm (Ubuntu)
Importance: Low = High
** Changed in: qemu-kvm (Ubuntu)
Importance: High = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I waffled on priority because I was uncertain about a good workaround.
However,
-boot priority=cn
seems to do the trick, so marking this low priority (unless I hear of a
reason why that workaround is insufficient).
--
You received this bug notification because you are a member of Ubuntu
Server
** Branch linked: lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/fix-boot-once
--
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
--
With the tree at
https://code.launchpad.net/~serge-hallyn/ubuntu/lucid/qemu-kvm/fix-boot-once/
'boot once=d' works correctly for me. The package is building at ppa
:serge-hallyn/virt.
I'm pushing the amd64 debs to the bug here. If you're on amd64, please
test and let me know if they also work
** 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
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Natty version is unaffected, so marking fix released for there.
** Changed in: qemu-kvm (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
Please forget about the ppa and just test the packages in the tarball,
thank.
--
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
Hi Serge,
Thanks for looking into this.
I am using amd64 so I'll try out the fix.
Using once did not work for me even if there wasn't a valid OS on
the hard drive.
I'm OK with an importance of low, I was using the workaround of
simply stopping the qemu-kvm after the first
Thanks, that fixed the problem. Will that fix make it into lucid-
updates?
Deric
On 02/17/11 18:40, Deric Sullivan wrote:
Hi Serge,
Thanks for looking into this.
I am using amd64 so I'll try out the fix.
Using once did not work for me even if there wasn't a valid OS
on the
Quoting Deric Sullivan (deric.sulli...@ec.gc.ca):
Thanks, that fixed the problem. Will that fix make it into lucid-
updates?
Great, thanks for testing. Yes, I'll request the SRU.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
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
32 matches
Mail list logo
