similar to: CentOS 6.4 kickstart bonding

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 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, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

Hi, I'm kickstarting a vm in ESXi 5.1. ks.cfg is on floppy, install media is ISO file. This works great as long as I don't add an additional repo, in our case it is vmware tools on one of our webservers. If I add the repo line, anaconda asks then for the used network card and indeed, switching to console the interfaces are still unconfigured. Chosing eth0 in gui continues the

Hello All, I have one CentOS 6 KVM virtualization server that I built around a year ago (best I can tell it was in October 2012) at which time I would have been installing 6.3 [0]. That particular install used the Consistent Network Device Naming [1] conventions (PCIe NICs are p1p1, p1p2). I started to build out a new KVM virt server (kickstarting a 6.4 install now as compared to 6.3 back then)

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

I have a dataset named DM with p1, p2, ...., p9 (9 columns, numerical values) I would like to calculate to multify each pair of columns (p1p2, p1p3,... p1p9, p2p3, p2p4.... p8p9) and assign them in p1p2, p1p3,... p1p9, p2p3, p2p4.... p8p9 In SAS, l=0; p_int_sum=0; do i=1 to 8; do j=(i+1) to 9; l=l+1; p{i}p{j}=p{i}*p{j}; end; end; I would like to know how to assign them in R I tried for

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

Hi folks, I've got a Dell R320 running CentOS 7, and a 10G NIC. I'm running a DNS server on it, for testing. As part of my testing, I'm attempting to capture all the DNS queries arriving on the server, using tcpdump. However, tcpdump's performance is abysmal, and it loses lots of the packets. Here's the output when I stop the capture: # tcpdump -nn -i p1p1 -w

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 \

Hello, I have a CentOS 7.3 + updates server where my configuration arises from the need to connect via iSCSI to a Dell PS Series storage array and Dell not supporting bonding. So that I need to use 2 nics on the same vlan to connect to iSCSI portal IP and then use multipath. Also, the iSCSI lan is on a dedicated vlan I have only these 2 x 10Gbit adapters and I also need to put other vlans on them

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

I''m running Xen 4.1.4 on Fedora 17. I have some CentOS 6 DomUs - an haproxy machine and some tomcat VMs. When clients send requests with: POST /ProposalInterface HTTP/1.1 Content-Type: text/xml Host: www.myhost.co.uk Content-Length: 2099 Expect: 100-continue Connection: Keep-Alive The "continuation" doesn''t happen. The POST is truncated at 1449 bytes, and the

Currently, I have two networks configured via xml: virsh # net-dumpxml TestNetwork1 <network connections='2'> <name>TestNetwork1</name> <uuid>a76f665a-0196-4edb-81b4-340944a6869c</uuid> <forward dev='p1p1' mode='nat'> <nat> <port start='1024' end='65535'/> </nat> <interface

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

Hi, I am a happy user of version 4.06 and have been hoping to upgrade the 5.x series (for the HTTP bits). I have the following problems with the 5.11-pre7 build: 1. TFTP load is horribly slow ... even when the two REAL machines are connected to the same switch. For a typical RHEL installation, the vmlinuz loads ... the initrd.img loads very very slowly and just times out (I waited over 10 mins)

Hi all, I'm in need of creating a simple menu where two options must be available: 1) (default) Boot from local harddrive 2) start installation 2) option should display a simple text disclaimer and if agreed it then would ask for a number from 32 to 254 which is then appended to one of commandline parameters. I have quite a lot of experience with [sys|pxe|iso]linux and some programming

-----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

> > We are not ready for "prime-time" though. > Using the "lpxelinux.0" file from 6.03-pre19 ... > > My RHEL5 installs, when using the "http://" for kernel, initrd and append lines, seem to be hitting some sort of parameter length limit. > The culprit seems to be the long "append" line. > > The same append line, when NOT using

Paul, On Thu, Mar 17, 2016 at 5:47 PM, Digimer <lists at alteeve.ca> wrote: > On 17/03/16 04:47 PM, paul.greene.va at verizon.net wrote: > > Thanks, I followed the 2nd article, and it got the existing virtual > > machines communicating with each other. > Right, so your VMs are on the same bridge group now (at Layer2 of OSI). > > > > However, any new