Launchpad has imported 37 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=472236.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
There hasn't been a reply to my question in the last comment within
months, so I assume this has been fixed in upstream, too. Closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Since it has been fixed in Precise ... I assume this has also been fixed
in upstream QEMU? Or is there still anything left to do here?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This issue should be fixed in the qemu-kvm version included in precise.
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
This issue should be fixed in the qemu-kvm version included in precise.
** 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/551545
Still a problem in Lucid, making automatic installation and deployment
of VMs (using Cobbler or Foreman) pretty much impossible without manual
intervention. This, of course, defeats the whole point of automatic
installation and deployment.
--
You received this bug notification because you are a
lucid-updates and lucid-proposed ship the same package and from the
changelog I cannot see what change would be related to this big.
I've just confirmed by testing that the bug still applies to the most
uptodate packages that are available for lucid.
** Changed in: qemu-kvm (Ubuntu)
lucid-updates and lucid-proposed ship the same package and from the
changelog I cannot see what change would be related to this big.
I've just confirmed by testing that the bug still applies to the most
uptodate packages that are available for lucid.
** Changed in: qemu-kvm (Ubuntu)
** Also affects: qemu
Importance: Undecided
Status: New
--
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/551545
Title:
PXE netboot not booting localboot from virtio-disk
Hi,
could you test whether you still have this problem with lucid-proposed?
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551545
Title:
PXE netboot not booting localboot from virtio-disk
--
ubuntu-bugs
Hi,
could you test whether you still have this problem with lucid-proposed?
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
this bug has nothing to do with VDE. It seems that ubuntu's current
version of libvirt/kvm-qemu does not implement boot ordering correctly.
this seems to be present in fedora as well:
https://bugzilla.redhat.com/show_bug.cgi?id=472236
** Bug watch added: Red Hat Bugzilla #472236
VDE is very great. I use it since many months and had NEVER any
problems. There is no better solution than cde. And I do not understand,
why you do not put it into main repo. Sayin: insecure is not a good
answer without telling where.
So does it mean, the wrapper vdekvm will be kicked in Lucid?
VDE is very great. I use it since many months and had NEVER any
problems. There is no better solution than cde. And I do not understand,
why you do not put it into main repo. Sayin: insecure is not a good
answer without telling where.
So does it mean, the wrapper vdekvm will be kicked in Lucid?
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/42477592/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/42477593/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42477594/Dependencies.txt
**
According to your command line:
-boot order=nc \
I don't think that this include a local hard disk as part of the list of
devices to be considered for booting.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
Directly from the manpage:
-boot [order=drives][,once=drives][,menu=on|off]
Specify boot order drives as a string of drive letters. Valid drive
letters depend on the target achitecture. The x86 PC uses: a, b (floppy 1 and
2), c (first hard disk), d (first CD-ROM), n-p
By the way: PXELinux ignores timeout, if prompt is set. So this seems to
be a second bug (this worked on karmic).
--
PXE netboot not booting localboot from virtio-disk
https://bugs.launchpad.net/bugs/551545
You received this bug notification because you are a member of Ubuntu
Server Team, which
Also, vde networking will not work with Lucid's kvm. To use vde
networking, we'd need to build qemu-kvm with libvde2, which we cannot
do because it's in Universe.
Please consider using one of the other more secure, officially
supported networking models:
*
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/42477592/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/42477593/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42477594/Dependencies.txt
**
According to your command line:
-boot order=nc \
I don't think that this include a local hard disk as part of the list of
devices to be considered for booting.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
Directly from the manpage:
-boot [order=drives][,once=drives][,menu=on|off]
Specify boot order drives as a string of drive letters. Valid drive
letters depend on the target achitecture. The x86 PC uses: a, b (floppy 1 and
2), c (first hard disk), d (first CD-ROM), n-p
By the way: PXELinux ignores timeout, if prompt is set. So this seems to
be a second bug (this worked on karmic).
--
PXE netboot not booting localboot from virtio-disk
https://bugs.launchpad.net/bugs/551545
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also, vde networking will not work with Lucid's kvm. To use vde
networking, we'd need to build qemu-kvm with libvde2, which we cannot
do because it's in Universe.
Please consider using one of the other more secure, officially
supported networking models:
*
25 matches
Mail list logo
