From: Anthony Liguori <anthony@codemonkey.ws>
To: Glauber Costa <glommer@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] proposal : use gpxe roms in upstream qemu
Date: Wed, 26 Aug 2009 08:55:28 -0500 [thread overview]
Message-ID: <4A953ED0.8030601@codemonkey.ws> (raw)
In-Reply-To: <20090826023110.GB3177@mothafucka.localdomain>
Glauber Costa wrote:
> Hi people,
>
> For a while now, we are using gpxe instead of etherboot in fedora's qemu, with strong success.
> etherboot is currently deprecated, and gpxe offers a lot of interesting features, like iscsi
> initiator support, besides being actively maintained. I even think with some effort we may be
> able to get rid of extboot by using gpxe infrastructure to initiate virtio disks.
>
> I propose we do the same in upstream qemu. To properly use it, there are a number of qemu, bochs bios
> and kernel (in kvm case) fixes needed. But they are fairly old at this point in time, and had more than
> enough time to spread around.
>
> I've put the roms we are using in http://glommer.net/gpxe if people want to test it. They are built
> from gpxe 0.9.7 without any patches, so it should be very very straightforward to reproduce. One can
> also grab .rom files from rom-o-matic.net
>
One problem with this is that gpxe does not work with the builtin tftp
server. If I do:
x86_64-softmmu/qemu-system-x86_64 -hda ~/imag/linux.img -snapshot -L
~/git/qemu/pc-bios -boot n -bootp /pxelinux.0 -tftp /tftpboot
I get a tftp server does not support tsize option.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-08-26 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 2:31 [Qemu-devel] proposal : use gpxe roms in upstream qemu Glauber Costa
2009-08-26 13:55 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-26 8:35 Laurent Vivier
2009-08-26 11:58 ` Glauber Costa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A953ED0.8030601@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=glommer@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.