similar to: C6: kickstart problems with additional repo

Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for

Hello All, I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option. It would seem that if I tell the bridge device to use a virtual interface (like bond0) rather than a physical interface (em1/em2) that kickstart completely barfs on it. I have provided my network section below which works fine as long as i don't enable all the bridge content. When the

Hello, I?m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

Hi virt, im stumped... any help would be appreciated. I normally create my VMs like this: base="http://mirror.pnl.gov/fedora/linux/releases/20/Fedora/x86_64/os/" sudo virt-install --hvm --name $vm_name$i --ram 4000 \ --disk path=/VirtualMachines/$vm_name$i,size=30 \ --location $base -x "ks=http://xxx.os21.ks$kx" HOWEVER... I'm finding that my VMs dont boot after i

I am getting the following error on boot on a new install Centos 51: #/bin/sh ro no such file or directory then a kernel panic I have traced it to the call ''switchroot'' in the init script in the initrd. the exact same build without zen has no problems. the boot messages look like: Attaching to iSCSI storage iscsistart: transport class version 2.0-724. iscsid version 2.0-865

Hi Giuseppe and thanks for the response............ Heres some more info: Here is my kickstart... maybe the "--bootloader" argument is wrong in some way? # Put this in pastebin or some other public url # Kickstart file automatically generated by anaconda. #version=DEVEL install cdrom lang en_US.UTF-8 keyboard us network --onboot yes --device eth0 --bootproto dhcp --noipv6 timezone

Hello! I would like to use the new bonding feature of kickstart in release 6.4. My setup is one bonding interface (bond0) with two (eth0, eth1) ethernet cards. I am using two VLANs on bonding interface so I have no IP for bond0 but have IPs for bond0.1 and bond0.2. If I create config by hand it works. Now I would like to convert my kickstart file using the new bonding feature. The kickstart

Hi, after IPv6 day, I was wondering if our server were really secure... And, I know we should switch on IPv6 everywhere but... it will take some time. Usually, we disable(d) IPv6; so we are not running ip6tables. Can I start ip6tables in all cases (even if only IPv4) just to be on the safe side? On CentOS 6 servers, I use the --noipv6 in the kickstart files and I removed NetworkManager; but

Ok, so some of this now works, but I'm still having problems. With the bootif option, the system now correctly configures and uses the same interface to get its kickstart file. However, when the system is done and boots up, the interfaces are still messed up. So this is what I have in the kickstart file: # On-Board Port 1 with public IP configuration network --noipv6 --onboot yes --bootproto

I have a server running Centos4. I found I was seeing some network problems so I tried "route" and found there was no routing. I thought reboot would solve it but it didn't. I had to manually enter a route to the default gateway, there is still no route to the loopback interface. How is this possible? I thought there was default routes built into the kernel, taken from

Hi, I've created a bridge using 2 interfaces and have a lot of messages as follows: nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own address as source address nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own address as source address And the operating systems is extremely slow Interfaces files : [root at localhost ~]# cat

Hi, all. I use this kickstart file to install CentOS 5.2 (both i386 and x86_64), but i can't config NICs and hostname during installation, what's wrong with it? Thanks very much. ----<- kickstart file ----<---- # System authorization information #auth --useshadow --enablemd5 # System keyboard #keyboard us # System language #lang en_US # Installation logging level #logging

I''ve been using Puppet now for a month or so and I''ve come to a problem that may warrant an additional Puppet metaparameter. I''m advocating the addition of a metaparameter called "preaction" (or something like that), which will perform some arbitrary action before the resource is modified. There may be a way to do this within Puppet already (with some

I have a server located remotely running CentOS 5.x. I need to have two IP's on the same interface. So I have this: /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none BROADCAST=69.x.x.199 HWADDR=00:x:x:x:c6:10 IPADDR=69.x.x.194 NETMASK=255.255.255.248 NETWORK=69.x.x.192 ONBOOT=yes GATEWAY=69.x.x.193 TYPE=Ethernet So I added this:

Hi all, Read many posts on the subject. Using 802.3ad. Few problems; Cannot ping some hosts on the network, they are all up. Cannot resolve via DNS which is one of the hosts that I cannot ping, internal nor external DNS hosts. Unplugging the NICS and plugging them back in will then not allow pining if the default d=gateway. When cold booting it somewhat works, some hosts are pingable while

Hi Folks, I'm interested in "headless" installation. If I use GRUB, then I provide arguments to the kernel of things like "headless vnc vncpassword=whoopie ip=dhcp" GRUB passes this on to ISOLinux, which manages the CD and subsequently the installation. Shouldn't I be able to do exactly the same thing with EXTLinux? I ask, because, as you might suspect, I

> Date: Monday, October 03, 2016 22:00:07 -0400 > From: TE Dukes <tdukes at palmettoshopper.com> > >> From: Gordon Messmer >> Sent: Monday, October 3, 2016 4:25 PM >> >> On 10/03/2016 04:54 AM, TE Dukes wrote: >> > I can get the guest to access the internet but have tried every >> > was possible to be able to access the guest from the LAN

We just went to replace the bridge/firewall services one one server with the same on another. It's pretty simple, and I literally cloned (w/ rsync) a third server that does this onto the one that will be the new one. Then copied the /etc/sysconfig/iptables from the one being replaced, and brought it up this morning. Nope. We had to put everything back the way it was. The new one sees the two

Hi All, I''m using xen 3.0 on CentOS 5 with VLAN. #vconfig add eth0 100 #/etc/xen/script/network- bridge start vifnum=1 netdev=eth0 bridge=xenbr0.100 I know that after xen 3.2 the procedure of bridge configuration is changed. What is the correct command to set bridge interface to vlan? Yukio