We now use ipxe by default, which doesn't have this bug.
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/648228
Title:
boot
Yup, I can reproduce this locally.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
boot ordering broken: does not try next boot device
https://bugs.launchpad.net/bugs/648228
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Oops, sorry - I hadn't noticed that virt-manager had un-connected
the cdrom. In fact, I can NOT reproduce this. When I hit 'q' to quit
attempting network boot, it proceeds to boot the installation cdrom.
Do you still have this problem in the latest maverick versions?
** Changed in: qemu-kvm
Well, pressing 'q' indeed makes it proceed with the installation cdrom.
However, it doesn't do so non-interactively.
In my setup, I configure both VMs and physical machines to boot via PXE,
but by default have them boot locally. Only in case they require
maintenance, the PXE configuration is
Looking around the intertubez a bit, I see it being claimed that that is
supported by
gpxe, but not etherboot. I'm going to investigate switching to gpxe for natty.
However
I see no chances of such a large change being accepted for SRU into lucid, so
if this
is something you rely on, you can
Yup, I can reproduce this locally.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
boot ordering broken: does not try next boot device
https://bugs.launchpad.net/bugs/648228
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Oops, sorry - I hadn't noticed that virt-manager had un-connected
the cdrom. In fact, I can NOT reproduce this. When I hit 'q' to quit
attempting network boot, it proceeds to boot the installation cdrom.
Do you still have this problem in the latest maverick versions?
** Changed in: qemu-kvm
Well, pressing 'q' indeed makes it proceed with the installation cdrom.
However, it doesn't do so non-interactively.
In my setup, I configure both VMs and physical machines to boot via PXE,
but by default have them boot locally. Only in case they require
maintenance, the PXE configuration is
Looking around the intertubez a bit, I see it being claimed that that is
supported by
gpxe, but not etherboot. I'm going to investigate switching to gpxe for natty.
However
I see no chances of such a large change being accepted for SRU into lucid, so
if this
is something you rely on, you can
sorry for the delay, here is the xml
** Attachment added: debtest.xml
https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/648228/+attachment/1673373/+files/debtest.xml
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
--
boot ordering broken: does not try next boot
used versions:
ii libvirt-bin 0.8.3-1ubuntu14 the programs for the
libvirt library
ii virt-manager0.8.4-7ubuntu1 desktop application for
managing virtual machines
--
boot ordering broken: does not try next boot device
sorry for the delay, here is the xml
** Attachment added: debtest.xml
https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/648228/+attachment/1673373/+files/debtest.xml
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
--
boot ordering broken: does not try next boot
used versions:
ii libvirt-bin 0.8.3-1ubuntu14 the programs for the
libvirt library
ii virt-manager0.8.4-7ubuntu1 desktop application for
managing virtual machines
--
boot ordering broken: does not try next boot device
On Di, Sep 28, 2010 at 00:07:32 (CEST), C de-Avillez wrote:
Hi Reinhard,
What version of the packages are you running?
current maverick from the day I've reported the issue.
Also can you attach the XML for the VM?
will do later today.
--
Gruesse/greetings,
Reinhard Tartler, KeyID
On Di, Sep 28, 2010 at 00:07:32 (CEST), C de-Avillez wrote:
Hi Reinhard,
What version of the packages are you running?
current maverick from the day I've reported the issue.
Also can you attach the XML for the VM?
will do later today.
--
Gruesse/greetings,
Reinhard Tartler, KeyID
Hi Reinhard,
What version of the packages are you running? Also can you attach the
XML for the VM?
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
boot ordering broken: does not try next boot device
Hi Reinhard,
What version of the packages are you running? Also can you attach the
XML for the VM?
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
boot ordering broken: does not try next boot device
This issue may or may not be related to bug #551545
--
boot ordering broken: does not try next boot device
https://bugs.launchpad.net/bugs/648228
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs
This issue may or may not be related to bug #551545
--
boot ordering broken: does not try next boot device
https://bugs.launchpad.net/bugs/648228
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
19 matches
Mail list logo