12:28 p.m.
Hello,
I'm on a x86_64 F11 host.
I created with success CentOS 5.3 and Windows 2003 vms from iso images.
If i try to create a VM from virt-manager with pxe, I see from ps that
there is the
-boot n
option, but there aren't any
-tftp dir
and/or
-bootp file
options....
Is there any default for qemu and/or virt-manager?
If this helps, I'm trying to create a qemu/kvm virtual machine.
ps output is:
root 3577 1 99 14:52 ? 02:37:30 /usr/bin/qemu-kvm -S
-M pc -m 768 -smp 1 -name slackware64 -uuid
4e3c9c56-695a-b5a5-ff87-ab0807b19d63 -monitor pty -pidfile
/var/run/libvirt/qemu//slackware64.pid -no-reboot -boot n -drive
file=/dev/vg_qemu01/slack64,if=ide,index=0 -net
nic,macaddr=54:52:00:56:19:31,vlan=0 -net
tap,fd=19,script=,vlan=0,ifname=vnet3 -serial pty -parallel none -usb
-vnc 127.0.0.1:3 -soundhw es1370
The installation remains in attemp to get the tftp file without
success (it give "no filename")
It seems that the guest gets one of the available ip provided by
dhcpd, also it founds dhcpd and tftp server: both are set to
192.168.122.1 (the server itself with its virbro default interface).
No configuration done by me.
I see /etc/libvirt/qemu/networks/default.xml with some parameters but
I don't know if and how I can put here also tftp settings....
Thanks for any pointer.
Bye,
Gianluca
11:50 a.m.
Hey,
On Mon, 2009-06-15 at 19:28 +0200, Gianluca Cecchi wrote:
It seems that the guest gets one of the available ip provided by
dhcpd, also it founds dhcpd and tftp server: both are set to
192.168.122.1 (the server itself with its virbro default interface).
No configuration done by me.
I see /etc/libvirt/qemu/networks/default.xml with some parameters but
I don't know if and how I can put here also tftp settings....
Yeah, what we really need here is to have support for setting up TFTP
for libvirt's virtual networks - e.g.
<tftp root="/var/lib/tftpboot/linux-install" />
<bootp file="pxelinux.0" />
which would cause dnsmasq to be run with:
--enable-tftp --tftp-root=/var/lib/libvirt/tftp \
--dhcp-boot=pxelinux.0
we'd also need to open port 69 in our iptables rules.
Please file an RFE for this in bugzilla.redhat.com/Virtualization ...
maybe even give a shot at cooking up a patch?
Cheers,
Mark.
3:44 p.m.
On Tue, Jun 23, 2009 at 04:50:12PM +0000, Mark McLoughlin wrote:
Hey,
On Mon, 2009-06-15 at 19:28 +0200, Gianluca Cecchi wrote:
> It seems that the guest gets one of the available ip provided by
> dhcpd, also it founds dhcpd and tftp server: both are set to
> 192.168.122.1 (the server itself with its virbro default interface).
> No configuration done by me.
> I see /etc/libvirt/qemu/networks/default.xml with some parameters but
> I don't know if and how I can put here also tftp settings....
Yeah, what we really need here is to have support for setting up TFTP
for libvirt's virtual networks - e.g.
<tftp root="/var/lib/tftpboot/linux-install" />
<bootp file="pxelinux.0" />
which would cause dnsmasq to be run with:
--enable-tftp --tftp-root=/var/lib/libvirt/tftp \
--dhcp-boot=pxelinux.0
we'd also need to open port 69 in our iptables rules.
Please file an RFE for this in bugzilla.redhat.com/Virtualization ...
maybe even give a shot at cooking up a patch?
I really question what the point in going to setup a PXE server install
on each individual host OS is. The 'virtual network' is local only, so
you might as well just install the guest using a direct kernel+initrd
boot, avoiding all the host OS configuration steps, and extra PXE boot
complexity in libvirt.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
1:43 a.m.
On Tue, 2009-06-23 at 21:44 +0100, Daniel P. Berrange wrote:
On Tue, Jun 23, 2009 at 04:50:12PM +0000, Mark McLoughlin wrote:
> Hey,
>
> On Mon, 2009-06-15 at 19:28 +0200, Gianluca Cecchi wrote:
> > It seems that the guest gets one of the available ip provided by
> > dhcpd, also it founds dhcpd and tftp server: both are set to
> > 192.168.122.1 (the server itself with its virbro default interface).
> > No configuration done by me.
> > I see /etc/libvirt/qemu/networks/default.xml with some parameters but
> > I don't know if and how I can put here also tftp settings....
>
> Yeah, what we really need here is to have support for setting up TFTP
> for libvirt's virtual networks - e.g.
>
> <tftp root="/var/lib/tftpboot/linux-install" />
> <bootp file="pxelinux.0" />
>
> which would cause dnsmasq to be run with:
>
> --enable-tftp --tftp-root=/var/lib/libvirt/tftp \
> --dhcp-boot=pxelinux.0
>
> we'd also need to open port 69 in our iptables rules.
>
> Please file an RFE for this in bugzilla.redhat.com/Virtualization ...
> maybe even give a shot at cooking up a patch?
I really question what the point in going to setup a PXE server install
on each individual host OS is. The 'virtual network' is local only, so
you might as well just install the guest using a direct kernel+initrd
boot, avoiding all the host OS configuration steps, and extra PXE boot
complexity in libvirt.
It's a fair point - the main use case I see for it is as a way of
testing your PXE server config locally before booting remote machines.
Cheers,
Mark.
4:05 a.m.
On Wed, Jun 24, 2009 at 07:43:09AM +0100, Mark McLoughlin wrote:
On Tue, 2009-06-23 at 21:44 +0100, Daniel P. Berrange wrote:
> On Tue, Jun 23, 2009 at 04:50:12PM +0000, Mark McLoughlin wrote:
> > Hey,
> >
> > On Mon, 2009-06-15 at 19:28 +0200, Gianluca Cecchi wrote:
> > > It seems that the guest gets one of the available ip provided by
> > > dhcpd, also it founds dhcpd and tftp server: both are set to
> > > 192.168.122.1 (the server itself with its virbro default interface).
> > > No configuration done by me.
> > > I see /etc/libvirt/qemu/networks/default.xml with some parameters but
> > > I don't know if and how I can put here also tftp settings....
> >
> > Yeah, what we really need here is to have support for setting up TFTP
> > for libvirt's virtual networks - e.g.
> >
> > <tftp root="/var/lib/tftpboot/linux-install" />
> > <bootp file="pxelinux.0" />
> >
> > which would cause dnsmasq to be run with:
> >
> > --enable-tftp --tftp-root=/var/lib/libvirt/tftp \
> > --dhcp-boot=pxelinux.0
> >
> > we'd also need to open port 69 in our iptables rules.
> >
> > Please file an RFE for this in bugzilla.redhat.com/Virtualization ...
> > maybe even give a shot at cooking up a patch?
>
> I really question what the point in going to setup a PXE server install
> on each individual host OS is. The 'virtual network' is local only, so
> you might as well just install the guest using a direct kernel+initrd
> boot, avoiding all the host OS configuration steps, and extra PXE boot
> complexity in libvirt.
It's a fair point - the main use case I see for it is as a way of
testing your PXE server config locally before booting remote machines.
For that I'd expect you to use the same PXE server as you would later.
eg, if you're going to deploy Cobbler, then I'd expect you'd want to
actually be testing cobbler locally. I'm sure cobbler could be configured
to only attach to virbr0 for testing purposes.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
5:41 a.m.
On 06/23/09 22:44, Daniel P. Berrange wrote:
On Tue, Jun 23, 2009 at 04:50:12PM +0000, Mark McLoughlin wrote:
> Hey,
> <tftp root="/var/lib/tftpboot/linux-install"
/>
> <bootp file="pxelinux.0" />
> --enable-tftp --tftp-root=/var/lib/libvirt/tftp \
> --dhcp-boot=pxelinux.0
I really question what the point in going to setup a PXE server
install
on each individual host OS is.
None. You might want to use the install server which is somewhere in
your network though, i.e. something like this:
<bootp file="pxelinux.0" server="$ipaddr" />
cheers,
Gerd
3:40 p.m.
Are you guys looking at the cobbler and koan products supported by
Michael DeHaan and discussed on the cobbler mailing list
cobbler(a)lists.fedorahosted.org
I spent much of yesterday setting up cobbler and while I'm not sure I
have it fully working for non-virtualized installs, I know that a
Cobbler-supported PXE boot interface comes up on one of my test laptops
when I try to pxe boot. I have not yet completed my first cobbler- or
koan-based installs, though.
Bob Cochran
On 06/29/2009 06:41 AM, Gerd Hoffmann wrote:
On 06/23/09 22:44, Daniel P. Berrange wrote:
> On Tue, Jun 23, 2009 at 04:50:12PM +0000, Mark McLoughlin wrote:
>> Hey,
>> <tftp root="/var/lib/tftpboot/linux-install" />
>> <bootp file="pxelinux.0" />
>> --enable-tftp --tftp-root=/var/lib/libvirt/tftp \
>> --dhcp-boot=pxelinux.0
> I really question what the point in going to setup a PXE server install
> on each individual host OS is.
None. You might want to use the install server which is somewhere in
your network though, i.e. something like this:
<bootp file="pxelinux.0" server="$ipaddr" />
cheers,
Gerd
_______________________________________________
Fedora-virt mailing list
Fedora-virt(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-virt
7:58 a.m.
On Mon, Jun 29, 2009 at 04:40:11PM -0400, Robert L Cochran wrote:
Are you guys looking at the cobbler and koan products supported by
Michael DeHaan and discussed on the cobbler mailing list
Very much so - the people on this list who work at Red Hat work with
Michael DeHaan.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/
5419
days inactive
5434
days old
7 comments
6 participants
participants (6)
-
Daniel P. Berrange -
Gerd Hoffmann -
Gianluca Cecchi -
Mark McLoughlin -
Richard W.M. Jones -
Robert L Cochran