similar to: How to PXE kickstart hosts with little memory (Error: "Warning: /dev/root does not exist")?

On 04/21/2017 12:49 PM, Frank Thommen wrote: > > It seems, that this is not related to local disk space - as I initally > thought - but to too small memory. It only happens with VMs with > little RAM (1024 MB). As soon as we raise the available memory to > 2048 MB, kickstarting works fine. The RHEL 7 installation guide > states, that the minimal memory requirement is 1 GB,

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: > Hi, > > kickstarting fails due to problems with host resolution, even though the > network seems to be properly configured through DHCP. eno1 and eno2 are

Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: > This problem still bites us. I've tried to play around with DHCP > settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. > > I'm happy about /any/ hint. 1) ip route seems ok, but what does your /etc/resolv.conf looks like? 2) could you try with 7.3.1611, 7.2.1511 is no longer supported. Tru >

On Mon, 15 May 2017 at 20:05 zulu, Frank Thommen wrote: > lustre driver https://downloads.hpdd.intel.com/public/lustre/latest-feature-release/el7.3.1611/

Hi, On CentOS 6.7 (all updates) kickstarting a CentOS 7 VM (in the way it always has worked for other versions, incl. Fedora 22 VM's), does not work for me. I use virt-install with a local copy of the "images/pxeboot" tree. It all stops with: ... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. dracut-initqueue[551]: Warning: Could not boot.

Hi On 15/05/17 19:30, Tru Huynh wrote: > Hi, > > On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: >> This problem still bites us. I've tried to play around with DHCP >> settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. >> >> I'm happy about /any/ hint. > 1) ip route seems ok, but what does your /etc/resolv.conf looks like?

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/11/15 09:59, Jos Vos wrote: > Hi, > > On CentOS 6.7 (all updates) kickstarting a CentOS 7 VM (in the way > it always has worked for other versions, incl. Fedora 22 VM's), > does not work for me. I use virt-install with a local copy of the > "images/pxeboot" tree. It all stops with: > > ... [ OK ]

Hi, this puzzles me: On one of our developer workstations, all ports with the exception of SSH are closed: $ firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: eno1 sources: services: ssh dhcpv6-client ports: 22/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: $ but still port

Hi, how can a specific device driver in CentOS 7 be blacklisted, so that it doesn't load at boot time? We have Infiniband adapters which are not completely supported by CentOS and we want to silence the error messages for the time being. I tried with the files /etc/modprobe.d/blacklist /etc/modprobe.d/blacklist.conf and with entries mlx5_core mlx5_ib blacklist

On 10/29/2018 08:43 PM, Keith Keller wrote: > On 2018-10-29, Frank Thommen <list.centos at drosera.ch> wrote: >> >> PostgreSQL is running in a docker container: >> >> $ docker ps >> CONTAINER ID IMAGE COMMAND >> CREATED STATUS PORTS NAMES >> 6f11fc41d2f0 postgres

Hi, to install current PC models (with new Intel NICs) via Kickstart/PXE, I wanted to add the newest e1000e-Treiber to initrd.img. With this modified image, the Kickstart kernel crashes with the following error messages: [...] md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (20480 != 32768) 6062080

Hi, this is a side question to my other thread regarding dracut-initqueue network issues. Once I'm thrown into a dracut emergency shell (PXE booted system): How can I restart the kickstart installation process manually from there? Can I at all? Background is, that I'd like to add some debugging output to some of the dracut scripts and rerun the installation process to see why it

On 11/15/2017 07:50 PM, Gordon Messmer wrote: > On 11/15/2017 10:35 AM, Frank Thommen wrote: >> >> I tried with the files >> /etc/modprobe.d/blacklist >> /etc/modprobe.d/blacklist.conf >> and with entries >> blacklist mlx5_core >> blacklist mlx5_ib > > The "blacklist" entries prevent a module being loaded by its alias >

On 18/04/2017 15:54, Frank Thommen wrote: > 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

Hello, I am trying to make a .iso to p2v some old windows servers, and I installed a brand new FC22 server to build my images I run virt-p2v-make-kickstart fedora livecd-creator p2v.ks and I get the following error: Installing: grubby ##################### [435/436] Installing: uboot-tools ##################### [436/436] Installing:

Hi all, I'm having a bit of trouble with something and was wondering if anyone else has encountered this or knows what the problem is. I have one computer I would like to kickstart a centos 5.0 or 5.1 install. I have another computer which is the tftpboot server and contains the centos 5.0 and centos 5.1 install directories I wish to do the kickstart over nfs and my network is using MTU

On Mon, Aug 10, 2015 at 04:01:40PM -0400, Martin Breault wrote: > Hello, > > I am trying to make a .iso to p2v some old windows servers, and I > installed a brand new FC22 server to build my images > > I run > > virt-p2v-make-kickstart fedora > > livecd-creator p2v.ks > > and I get the following error: > > > Installing: grubby

Hey, I was thinking of added some stuff about setting the network settings from the lilo prompt instead of waiting for a dhcp timeout when kickstarting a system.. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20070316/383dbe2f/attachment-0002.html>