Michael DeHaan wrote:
Ronald J. Yacketta wrote:
Michael DeHaan wrote:
Ronald J. Yacketta wrote:
Running through the snippets in an attempt to resolve another issue and
I noticed the following in post_instyall_network_config
if [ -f "/etc/modprobe.conf" ] && [ $IFNAME ]; then
grep \$IFNAME /etc/modprobe.conf | sed "s/\$IFNAME/$iname/" >>
/etc/modprobe.conf.cobbler
grep -v \$IFNAME /etc/modprobe.conf >> /etc/modprobe.conf.new
rm -f /etc/modprobe.conf
mv /etc/modprobe.conf.new /etc/modprobe.conf
fi
not sure about RHEL, but Fedora does not use modprobe.conf for this type
of configuration. I created a similar thread with subject 'Arbitrary NIC
naming' back on 2/24/09 according to Jasper Capel:
Modprobe.conf just isn't used for that purpose in F10
anymore.
I'll file a bug against this as well and update this thread with the bug ID
-Ron
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
It's probably not hurting things.
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
I agree that there might be a limited number of endusers renaming
interfaces, but we are installing systems in a VM (Qemu) and would
like to rename the guest interfaces to match the underlying bridge
they are using.
The usage of modprobe.conf over udev rules prevents this from
happening during a cobbler/koan install.
I believe one of the features of the network interface arbitrary naming
support was exactly this, though I don't use it. Any comments, Jasper
(or others?)
Another issue that I noticed today is that no matter what I try / do
the nic being created for the VM is always the hypervisor default.
Tried everything to get cobbler to build out the proper xml to have a
virtio or e1000 module used.
virtio capability is chosen by libvirt/virtinst based on the
characteristics of the OS. If you imported the OS via cobbler import
the OS version fields should be set correctly on the distro to give you
virtio capability. If not, you can set this using distro edit.
-Ron
------------------------------------------------------------------------
ok, here is a report for a f10-i386 created with cobbler
cobbler report distro --name=f10-i386
distro : f10-i386
architecture : i386
breed : redhat
created : Wed Feb 18 10:37:17 2009
comment :
initrd : /mnt/cobbler_tree/f10/images/pxeboot/initrd.img
kernel : /mnt/cobbler_tree/f10/images/pxeboot/vmlinuz
kernel options : {}
ks metadata : {}
tree build time : Wed Dec 31 19:00:00 1969
modified : Tue Mar 10 09:11:21 2009
mgmt classes : []
os version :
owners : ['admin']
post kernel options : {}
redhat mgmt key : <<inherit>>
redhat mgmt server : <<inherit>>
template files : {}
profile : f10-i386
distro : f10-i386
comment :
created : Wed Feb 18 10:37:17 2009
dhcp tag : default
enable menu : True
kernel options : {}
kickstart : /var/lib/cobbler/kickstarts/f10.ks
ks metadata : {}
mgmt classes : []
modified : Mon Mar 9 14:36:00 2009
name servers : []
name servers search : []
owners : ['admin']
post kernel options : {}
redhat mgmt key : <<inherit>>
redhat mgmt server : <<inherit>>
repos : []
server : <<inherit>>
template_files : {}
virt bridge : br9
virt cpus : 1
virt file size : 10
virt path : /mnt/os1
virt ram : 512
virt type : qemu
you saying that I need to set 'os version ' to something? like f10-i386?
-Ron
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
