pxe booting not supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| etherboot (Ubuntu) |
Wishlist
|
Unassigned | ||
| kvm (Ubuntu) |
Undecided
|
Unassigned | ||
| libvirt (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Setting the boot device to network in the xml file that defines a new domain leads to a qemu error when loading the definition from virsh:
virsh # create vm/domains/
libvir: QEMU error : QEMU quit during console startup
No valid PXE rom found for network device
error: Failed to create domain from vm/domains/
Part of vm/domains/
<os>
</os>
pxe boot has been added to qemu 0.9.0.
kvm-61 changelog mentions something about e1000 pxe boot rom.
Changed in libvirt: | |
status: | New → Invalid |
Jan Lübbe (jluebbe) wrote : | #2 |
I'm now using the etherboot package at build time to provide these images for the debian package. You can pick the changeset from http://
Something like 'kvm -boot n -net nic,model=e1000 -net user -tftp ~/tmp/netboot -bootp /pxelinux.0' works now.
Dag Stenstad (dag-stenstad) wrote : | #3 |
To enable booting from PXE, you must obtain a working PXE bios for the emulated card.
I used the "e1000" driver (-net nic,model=e1000).
The image was downloaded from www.rom-
I moved the BIOS image to /usr/share/
Henning Sprang (henning) wrote : | #4 |
With the current rom-o-matic I didn't see the above selection of ROM is possible.
What I did is, I built upstream sources and then: cp -a ./qemu/
(at least it asks for ip and stuff, I'm stil about to set up the tftp properly, but5 I expect no surprises here)
I think, here a border of usefulness of software vs. the total avoidance of blobs i reached, and such things should be included.
Dustin Kirkland (kirkland) wrote : | #5 |
I'm marking this as "Fix Released".
Soren has solved this bug with a new package: kvm-pxe. Please see that package and reopen this bug if it's still a problem.
:-Dustin
Changed in kvm: | |
importance: | Undecided → Wishlist |
status: | Confirmed → Invalid |
Changed in etherboot: | |
importance: | Undecided → Wishlist |
status: | New → Fix Released |
Changed in kvm: | |
importance: | Wishlist → Undecided |
Poramet (oak-poramet) wrote : | #6 |
I got an error like this when i tried to start virtual machine via virt-manager that boot from network (pxe)
Traceback (most recent call last):
File "/usr/share/
vm.startup()
File "/usr/share/
self.
File "/usr/lib/
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: virDomainCreate() failed QEMU quit during console startup
qemu: unknowm parameter '-drive' in '-drive'
I already installed packet pxe-kvm. I don't know how to solve that . Please help me.
description: | updated |
description: | updated |
Dusty Wilson (dusty-hey) wrote : | #7 |
Forgive me for adding to an old bug. The way I "solved" it for myself is to use the ROM-o-matic gpxe boot ISO at this URL:
http://
If the above link is an old version by the time you read this, just go to http://
That ISO provides wide support for the full list of supported NICs (it seems). It has worked well for me on many computers, even really old ones. It works great for KVM. Just boot off it and it'll PXE-boot for you.
Not a fix, just a workaround.
Changed in etherboot (Ubuntu): | |
status: | Fix Released → Fix Committed |
On Wed, Feb 20, 2008 at 12:46:14AM -0000, Mathias Gug wrote:
> Setting the boot device to network in the xml file that defines a new
> domain leads to a qemu error when loading the definition from virsh:
We don't ship the PXE ROM's from KVM as the tarball does not contain the
source for them, so it's a kvm problem, rather than a lbivirt one.
affects ubuntu/kvm
status confirmed
affects ubuntu/libvirt
status invalid
To actually make it work, you need to extract the ROM from the etherboot
packages. A README.PXE-boot should be added to the kvm package some time
soon explaining what to do.
-- www.ubuntu. com/
Soren Hansen
Virtualisation specialist
Ubuntu Server Team
http://