Re: [xcat-user] xCAT 2.9.1, problem kickstarting centos7

[Jesus R. Camou]

Hey Josh,

centos7.1 provisioning works smoothly for me on 2.9.1 with the following
definition and templates:

[jcamou@xcat ~]$ lsxcatd -v
Version 2.9.1 (git commit 7f6043fffd62d482931b17b60f9488eb5754fdc1, built
Thu Mar 19 03:25:35 EDT 2015)

[jcamou@xcat ~]$ lsdef -t osimage centos7.1-x86_64-install-compute
Object name: centos7.1-x86_64-install-compute
addkcmdline=net.ifnames=0 biodevname=0
imagetype=linux
osarch=x86_64
osdistroname=centos7.1-x86_64
osname=Linux
osvers=centos7.1
otherpkgdir=/install/post/otherpkgs/centos7.1/x86_64
pkgdir=/install/centos7.1/x86_64
pkglist=/install/custom/install/centos7/compute.centos7.pkglist
profile=compute
provmethod=install
template=/install/custom/install/centos7/compute.centos7.tmpl

Notice the addkcmdline attribute has "net.ifnames=0 biodevname=0" to
disable consistent network device naming which forces the kernel to use and
stick to the ethX interface naming convention:

[jcamou@xcat ~]$ lsdef -t osimage -o centos7.1-x86_64-install-compute -i
addkcmdline
Object name: centos7.1-x86_64-install-compute
addkcmdline=net.ifnames=0 biodevname=0

You may set this by:

[jcamou@xcat ~]$ tabch imagename=centos7.1-x86_64-install-compute
linuximage.addkcmdline="net.ifnames=0 biodevname=0"


And the following templates (ignoring commented and empty lines for
shortening purposes):

[jcamou@xcat ~]$ grep -Ev '^#|^$'
/install/custom/install/centos7/compute.centos7.tmpl
lang en_US
%include /tmp/repos
keyboard "us"
zerombr
clearpart --all --initlabel
%include /tmp/partitioning
bootloader
install
text
firewall --disabled
timezone --utc "#TABLE:site:key=timezone:value#"
skipx
rootpw --iscrypted #CRYPT:passwd:key=system,username=root:password#
auth --useshadow --enablemd5
selinux --disabled
reboot
%packages
%end
%pre
%end
%post
%end


... and pkglist:

[jcamou@xcat ~]$ cat /install/custom/install/centos7/compute.centos7.pkglist
#Please make sure there is a space between @ and group name
wget
ntp
nfs-utils
net-snmp
rsync
yp-tools
openssh-server
util-linux
net-tools
mailx
vim-enhanced




- j


On Mon, Nov 23, 2015 at 12:43 PM, Josh Nielsen 
wrote:

> And did you ever figure out your problem Nathan?
>
> -Josh
>
> On Mon, Nov 23, 2015 at 2:34 PM, Josh Nielsen 
> wrote:
>
>> I was going to post a new thread about Centos 7 but thought I might piggy
>> back on this one since it is a similar topic. I have xCAT 2.8.3 currently
>> and it sounds like from the thread here that upgrading to 2.10 is part of
>> the solution for deploying Centos 7.1. Currently the issue I'm having is
>> that during a PXE boot it fetches the correct centos 7.1 image and begins
>> trying to deploy but after it shows "Mounted Configuration File System" and
>> "Started Show Plymouth Boot Screen" I get a message like this:
>> "dracut-initqueue: Warning: Could not boot" and hangs there.
>>
>> This isn't a very explicit error, as to what caused it, and I didn't
>> learn much from removing "quiet" from the PXE kernel boot parameters. I
>> also can't get the ctrl+alt+F keys to work, at least in a VM, for showing
>> different terminals like you could in Centos 6 (which was very helpful for
>> debugging).
>>
>> Is this most likely because the kickstart file itself is not formatted
>> correctly (I'm reusing my Centos 6.4 kickstart - until I figure out how
>> Centos 7.1 differs), or perhaps that the kickstart is not being properly
>> fetched from the gpxe configuration in /tftpboot/xcat/xnba/nodes? Currently
>> the gpxe boot configuration for the node I'm trying to deploy Centos7.1 to
>> looks like this:
>>
>> #!gpxe
>> #install centos7.1-x86_64-compute
>> imgfetch -n kernel http://
>> ${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/vmlinuz
>> imgload kernel
>> imgargs kernel repo=http://10.20.0.101:80/install/centos7.1/x86_64 ks=
>> http://10.20.0.101:80/install/autoinst/node0067c ksdevice=bootif cmdline
>> console=tty0 console=ttyS0,115200n8r BOOTIF=01-${netX/machyp}
>> imgfetch http://
>> ${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/initrd.img
>> imgexec kernel
>>
>> I manually changed ksdevice to "bootif" just to make sure it was using
>> the right interface (it was set to eth0 but Centos 7.1 got rid of "eth" for
>> "em" didn't it?). Nonetheless, I think my kickstart is being sucessfully
>> fetched, because I changed the disk formatting commands in the kickstart
>> and when I removed "quiet" from the boot I saw errors related to disk
>> formatting/partitioning. So I'm partial to thinking that the old Centos 6.4
>> kickstart configuration is not 100% compatible with Centos 7.1, but I want
>> to double check to see what xCAT 2.10 bring to the table that might be
>> necessary for Centos 7.1 deployment. Comments or thoughts?
>>
>> Regards,
>> Josh
>>
>> On Fri, Oct 23, 2015 at 1:44 PM, Russell Auld 
>> wrote:
>>
>>> Looks like xcatdsklspost does get called 

Re: [xcat-user] xCAT 2.9.1, problem kickstarting centos7

[Josh Nielsen]

Hi Jesus,

That's very useful information. Thank you for that! I'm going to update my
osimage definition and try a few more deploys and see how far I get with
it. I think I'll still end up having to update xCAT in any case, but I'll
see if I can get it working with the current install first, while making
manual edits as needed for testing.

Thanks,
Josh

On Mon, Nov 23, 2015 at 3:56 PM, Jesus R. Camou  wrote:

> Hey Josh,
>
> centos7.1 provisioning works smoothly for me on 2.9.1 with the following
> definition and templates:
>
> [jcamou@xcat ~]$ lsxcatd -v
> Version 2.9.1 (git commit 7f6043fffd62d482931b17b60f9488eb5754fdc1, built
> Thu Mar 19 03:25:35 EDT 2015)
>
> [jcamou@xcat ~]$ lsdef -t osimage centos7.1-x86_64-install-compute
> Object name: centos7.1-x86_64-install-compute
> addkcmdline=net.ifnames=0 biodevname=0
> imagetype=linux
> osarch=x86_64
> osdistroname=centos7.1-x86_64
> osname=Linux
> osvers=centos7.1
> otherpkgdir=/install/post/otherpkgs/centos7.1/x86_64
> pkgdir=/install/centos7.1/x86_64
> pkglist=/install/custom/install/centos7/compute.centos7.pkglist
> profile=compute
> provmethod=install
> template=/install/custom/install/centos7/compute.centos7.tmpl
>
> Notice the addkcmdline attribute has "net.ifnames=0 biodevname=0" to
> disable consistent network device naming which forces the kernel to use and
> stick to the ethX interface naming convention:
>
> [jcamou@xcat ~]$ lsdef -t osimage -o centos7.1-x86_64-install-compute -i
> addkcmdline
> Object name: centos7.1-x86_64-install-compute
> addkcmdline=net.ifnames=0 biodevname=0
>
> You may set this by:
>
> [jcamou@xcat ~]$ tabch imagename=centos7.1-x86_64-install-compute
> linuximage.addkcmdline="net.ifnames=0 biodevname=0"
>
>
> And the following templates (ignoring commented and empty lines for
> shortening purposes):
>
> [jcamou@xcat ~]$ grep -Ev '^#|^$'
> /install/custom/install/centos7/compute.centos7.tmpl
> lang en_US
> %include /tmp/repos
> keyboard "us"
> zerombr
> clearpart --all --initlabel
> %include /tmp/partitioning
> bootloader
> install
> text
> firewall --disabled
> timezone --utc "#TABLE:site:key=timezone:value#"
> skipx
> rootpw --iscrypted #CRYPT:passwd:key=system,username=root:password#
> auth --useshadow --enablemd5
> selinux --disabled
> reboot
> %packages
> %end
> %pre
> %end
> %post
> %end
>
>
> ... and pkglist:
>
> [jcamou@xcat ~]$ cat
> /install/custom/install/centos7/compute.centos7.pkglist
> #Please make sure there is a space between @ and group name
> wget
> ntp
> nfs-utils
> net-snmp
> rsync
> yp-tools
> openssh-server
> util-linux
> net-tools
> mailx
> vim-enhanced
>
>
>
>
> - j
>
>
> On Mon, Nov 23, 2015 at 12:43 PM, Josh Nielsen 
> wrote:
>
>> And did you ever figure out your problem Nathan?
>>
>> -Josh
>>
>> On Mon, Nov 23, 2015 at 2:34 PM, Josh Nielsen 
>> wrote:
>>
>>> I was going to post a new thread about Centos 7 but thought I might
>>> piggy back on this one since it is a similar topic. I have xCAT 2.8.3
>>> currently and it sounds like from the thread here that upgrading to 2.10 is
>>> part of the solution for deploying Centos 7.1. Currently the issue I'm
>>> having is that during a PXE boot it fetches the correct centos 7.1 image
>>> and begins trying to deploy but after it shows "Mounted Configuration File
>>> System" and "Started Show Plymouth Boot Screen" I get a message like this:
>>> "dracut-initqueue: Warning: Could not boot" and hangs there.
>>>
>>> This isn't a very explicit error, as to what caused it, and I didn't
>>> learn much from removing "quiet" from the PXE kernel boot parameters. I
>>> also can't get the ctrl+alt+F keys to work, at least in a VM, for showing
>>> different terminals like you could in Centos 6 (which was very helpful for
>>> debugging).
>>>
>>> Is this most likely because the kickstart file itself is not formatted
>>> correctly (I'm reusing my Centos 6.4 kickstart - until I figure out how
>>> Centos 7.1 differs), or perhaps that the kickstart is not being properly
>>> fetched from the gpxe configuration in /tftpboot/xcat/xnba/nodes? Currently
>>> the gpxe boot configuration for the node I'm trying to deploy Centos7.1 to
>>> looks like this:
>>>
>>> #!gpxe
>>> #install centos7.1-x86_64-compute
>>> imgfetch -n kernel http://
>>> ${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/vmlinuz
>>> imgload kernel
>>> imgargs kernel repo=http://10.20.0.101:80/install/centos7.1/x86_64 ks=
>>> http://10.20.0.101:80/install/autoinst/node0067c ksdevice=bootif
>>> cmdline console=tty0 console=ttyS0,115200n8r BOOTIF=01-${netX/machyp}
>>> imgfetch http://
>>> ${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/initrd.img
>>> imgexec kernel
>>>
>>> I manually changed ksdevice to "bootif" just to make sure it was using
>>> the right interface (it was set to eth0 but Centos 7.1 got rid of "eth" for
>>> "em" didn't it?). 

Re: [xcat-user] xCAT 2.9.1, problem kickstarting centos7

[Jesus R. Camou]

Just realized that the reverse grep I did for lines beginning with #
shopped off some required #INCLUDE:* lines in the pre and post installation
sections.  Here's the full template file I'm using for centos7.1:
http://paste.fedoraproject.org/293756/83282871

Depending on your version, you may need to update your
/opt/xcat/share/xcat/install/script/{pre,post}.rhels7 as your version may
have shipped with them.

On Mon, Nov 23, 2015 at 3:32 PM, Josh Nielsen 
wrote:

> Hi Jesus,
>
> That's very useful information. Thank you for that! I'm going to update my
> osimage definition and try a few more deploys and see how far I get with
> it. I think I'll still end up having to update xCAT in any case, but I'll
> see if I can get it working with the current install first, while making
> manual edits as needed for testing.
>
> Thanks,
> Josh
>
> On Mon, Nov 23, 2015 at 3:56 PM, Jesus R. Camou 
> wrote:
>
>> Hey Josh,
>>
>> centos7.1 provisioning works smoothly for me on 2.9.1 with the following
>> definition and templates:
>>
>> [jcamou@xcat ~]$ lsxcatd -v
>> Version 2.9.1 (git commit 7f6043fffd62d482931b17b60f9488eb5754fdc1, built
>> Thu Mar 19 03:25:35 EDT 2015)
>>
>> [jcamou@xcat ~]$ lsdef -t osimage centos7.1-x86_64-install-compute
>> Object name: centos7.1-x86_64-install-compute
>> addkcmdline=net.ifnames=0 biodevname=0
>> imagetype=linux
>> osarch=x86_64
>> osdistroname=centos7.1-x86_64
>> osname=Linux
>> osvers=centos7.1
>> otherpkgdir=/install/post/otherpkgs/centos7.1/x86_64
>> pkgdir=/install/centos7.1/x86_64
>> pkglist=/install/custom/install/centos7/compute.centos7.pkglist
>> profile=compute
>> provmethod=install
>> template=/install/custom/install/centos7/compute.centos7.tmpl
>>
>> Notice the addkcmdline attribute has "net.ifnames=0 biodevname=0" to
>> disable consistent network device naming which forces the kernel to use and
>> stick to the ethX interface naming convention:
>>
>> [jcamou@xcat ~]$ lsdef -t osimage -o centos7.1-x86_64-install-compute -i
>> addkcmdline
>> Object name: centos7.1-x86_64-install-compute
>> addkcmdline=net.ifnames=0 biodevname=0
>>
>> You may set this by:
>>
>> [jcamou@xcat ~]$ tabch imagename=centos7.1-x86_64-install-compute
>> linuximage.addkcmdline="net.ifnames=0 biodevname=0"
>>
>>
>> And the following templates (ignoring commented and empty lines for
>> shortening purposes):
>>
>> [jcamou@xcat ~]$ grep -Ev '^#|^$'
>> /install/custom/install/centos7/compute.centos7.tmpl
>> lang en_US
>> %include /tmp/repos
>> keyboard "us"
>> zerombr
>> clearpart --all --initlabel
>> %include /tmp/partitioning
>> bootloader
>> install
>> text
>> firewall --disabled
>> timezone --utc "#TABLE:site:key=timezone:value#"
>> skipx
>> rootpw --iscrypted #CRYPT:passwd:key=system,username=root:password#
>> auth --useshadow --enablemd5
>> selinux --disabled
>> reboot
>> %packages
>> %end
>> %pre
>> %end
>> %post
>> %end
>>
>>
>> ... and pkglist:
>>
>> [jcamou@xcat ~]$ cat
>> /install/custom/install/centos7/compute.centos7.pkglist
>> #Please make sure there is a space between @ and group name
>> wget
>> ntp
>> nfs-utils
>> net-snmp
>> rsync
>> yp-tools
>> openssh-server
>> util-linux
>> net-tools
>> mailx
>> vim-enhanced
>>
>>
>>
>>
>> - j
>>
>>
>> On Mon, Nov 23, 2015 at 12:43 PM, Josh Nielsen 
>> wrote:
>>
>>> And did you ever figure out your problem Nathan?
>>>
>>> -Josh
>>>
>>> On Mon, Nov 23, 2015 at 2:34 PM, Josh Nielsen 
>>> wrote:
>>>
 I was going to post a new thread about Centos 7 but thought I might
 piggy back on this one since it is a similar topic. I have xCAT 2.8.3
 currently and it sounds like from the thread here that upgrading to 2.10 is
 part of the solution for deploying Centos 7.1. Currently the issue I'm
 having is that during a PXE boot it fetches the correct centos 7.1 image
 and begins trying to deploy but after it shows "Mounted Configuration File
 System" and "Started Show Plymouth Boot Screen" I get a message like this:
 "dracut-initqueue: Warning: Could not boot" and hangs there.

 This isn't a very explicit error, as to what caused it, and I didn't
 learn much from removing "quiet" from the PXE kernel boot parameters. I
 also can't get the ctrl+alt+F keys to work, at least in a VM, for showing
 different terminals like you could in Centos 6 (which was very helpful for
 debugging).

 Is this most likely because the kickstart file itself is not formatted
 correctly (I'm reusing my Centos 6.4 kickstart - until I figure out how
 Centos 7.1 differs), or perhaps that the kickstart is not being properly
 fetched from the gpxe configuration in /tftpboot/xcat/xnba/nodes? Currently
 the gpxe boot configuration for the node I'm trying to deploy Centos7.1 to
 looks like this:

 #!gpxe
 #install centos7.1-x86_64-compute
 imgfetch -n 

Re: [xcat-user] Diskless centos7.1 image failing to boot

[Russell Jones]

 

Yep! 

This is being ran on a CentOS 7.1 "build host". The management node is
CentOS 6.6. I am following the docs for building an OS image of a
different type. I am then running imgexport on the "build host", copying
the tar over to the management node, and running "imgimport". 

Here's the osimage definition: 

Object name: v7.1.0-dl-compute-apu
 groups=all
 imagetype=linux
 nodebootif=eth0
 osarch=x86_64
 osdistroname=centos7.1-x86_64
 osname=Linux
 osvers=centos7.1
 otherpkgdir=/install/custom/v7.1.0-dl-compute-apu/otherpkgs

otherpkglist=/install/custom/v7.1.0-dl-compute-apu/v7.1.0-dl-compute-apu.otherpkgs.pkglist
 permission=755
 pkgdir=/install/centos7.1/x86_64

pkglist=/install/custom/v7.1.0-dl-compute-apu/v7.1.0-dl-compute-apu.pkglist
 postbootscripts=otherpkgs

postinstall=/install/custom/v7.1.0-dl-compute-apu/v7.1.0-dl-compute-apu.postinstall
 profile=v7.1.0-dl-compute-apu
 provmethod=netboot
 rootimgdir=/install/netboot/centos7.1/x86_64/v7.1.0-dl-compute-apu

synclists=/install/custom/v7.1.0-dl-compute-apu/v7.1.0-dl-compute-apu.synclist


Here's the output during genimage time after yum has finished running: 

Complete!
Added vxlan.ko as an autodetected depedency
Added ip_tunnel.ko as an autodetected depedency
Added virtio_ring.ko as an autodetected depedency
Added virtio.ko as an autodetected depedency
Added mlx4_core.ko as an autodetected depedency
Added ptp.ko as an autodetected depedency
Added pps_core.ko as an autodetected depedency
Added i2c-algo-bit.ko as an autodetected depedency
Added dca.ko as an autodetected depedency
Added i2c-core.ko as an autodetected depedency
Added mdio.ko as an autodetected depedency
Added libcrc32c.ko as an autodetected depedency
Enter the dracut mode. Dracut version: 033. Dracut directory:
dracut_033.
Try to load drivers: pps_core i2c-core ip_tunnel ptp libcrc32c mdio dca
i2c-algo-bit mlx4_core vxlan virtio virtio_ring tg3 bnx2 bnx2x e1000
e1000e igb mlx4_en virtio_net be2net ext3 ext4 to initrd.
No '/dev/log' or 'logger' included for syslog logging
Turning off host-only mode: '/sys' is not mounted!
Turning off host-only mode: '/proc' is not mounted!
Turning off host-only mode: '/run' is not mounted!
Turning off host-only mode: '/dev' is not mounted!
the initial ramdisk for stateless is generated successfully.
Try to load drivers: pps_core i2c-core ip_tunnel ptp libcrc32c mdio dca
i2c-algo-bit mlx4_core vxlan virtio virtio_ring tg3 bnx2 bnx2x e1000
e1000e igb mlx4_en virtio_net be2net ext3 ext4 to initrd.
No '/dev/log' or 'logger' included for syslog logging
Turning off host-only mode: '/sys' is not mounted!
Turning off host-only mode: '/proc' is not mounted!
Turning off host-only mode: '/run' is not mounted!
Turning off host-only mode: '/dev' is not mounted!
the initial ramdisk for statelite is generated successfully. 

On 19.11.2015 20:21, Er Tao Zhao wrote: 

> Can you show me the osimage definition that you run genimage against?
> 
> Thx!
> Best Regards,
> ---
> Zhao Er Tao
> 
> IBM China System and Technology Laboratory, Beijing
> Tel:(86-10)82450485
> Email: erta...@cn.ibm.com
> Address: 1/F, 28 Building,ZhongGuanCun Software Park,
> No.8 DongBeiWang West Road, Haidian District, 
> Beijing, 100193, P.R.China
> 
> Russell Jones ---2015-11-20 上午 04:46:01---Hi all, I am attempting to create 
> my first diskless Centos 7.1 image using xCAT
> 
> From: Russell Jones 
> To: xCAT Users Mailing list 
> Date: 2015-11-20 上午 04:46
> Subject: [xcat-user] Diskless centos7.1 image failing to boot 
> -
> 
> Hi all,
> 
> I am attempting to create my first diskless Centos 7.1 image using xCAT 
> 2.10. I have built the image and my node is successfully PXE'ing, 
> however is failing to switch over to the rootimg with the following 
> error on the console:
> 
> switch_root: cannot access /sbin/init: No such file or directory
> switch_root: failed to execute /sbin/init: No such file or directory
> 
> Looking at the rootimg directory, /sbin/init does exist. Unpacking the 
> initrd-stateless file yields no /sbin/init, but there is an init at /. 
> This is the same when comparing it with an unpacked CentOS 6 image.
> 
> I know that RHEL/CentOS 7 introduces the systemd crud which I am not 
> very familiar with yet. Is there a package or configuration error I 
> could be making in my CentOS 7 osimage configuration that could be 
> causing this?
> 
> Thanks!
> 
> --
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user [1]
> 
> --
>  
> 
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user [1]

Re: [xcat-user] Diskless centos7.1 image failing to boot

[Russell Jones]

I got it figured out. The scrolling messages was moving the important 
warnings off of the screen to where I couldn't see them - "No space left 
on device".


The VM did not have enough memory assigned to it to completely extract 
the root filesystem. After fixing that issue everything booted up fine :)




On 11/23/2015 9:56 AM, Russell Jones wrote:


Yep!

This is being ran on a CentOS 7.1 "build host". The management node is 
CentOS 6.6. I am following the docs for building an OS image of a 
different type. I am then running imgexport on the "build host", 
copying the tar over to the management node, and running "imgimport".


Here's the osimage definition:

Object name: v7.1.0-dl-compute-apu
groups=all
imagetype=linux
nodebootif=eth0
osarch=x86_64
osdistroname=centos7.1-x86_64
osname=Linux
osvers=centos7.1
otherpkgdir=/install/custom/v7.1.0-dl-compute-apu/otherpkgs
otherpkglist=/install/custom/v7.1.0-dl-compute-apu/v7.1.0-dl-compute-apu.otherpkgs.pkglist
permission=755
pkgdir=/install/centos7.1/x86_64
pkglist=/install/custom/v7.1.0-dl-compute-apu/v7.1.0-dl-compute-apu.pkglist
postbootscripts=otherpkgs
postinstall=/install/custom/v7.1.0-dl-compute-apu/v7.1.0-dl-compute-apu.postinstall
profile=v7.1.0-dl-compute-apu
provmethod=netboot
rootimgdir=/install/netboot/centos7.1/x86_64/v7.1.0-dl-compute-apu
synclists=/install/custom/v7.1.0-dl-compute-apu/v7.1.0-dl-compute-apu.synclist

Here's the output during genimage time after yum has finished running:

Complete!
Added vxlan.ko as an autodetected depedency
Added ip_tunnel.ko as an autodetected depedency
Added virtio_ring.ko as an autodetected depedency
Added virtio.ko as an autodetected depedency
Added mlx4_core.ko as an autodetected depedency
Added ptp.ko as an autodetected depedency
Added pps_core.ko as an autodetected depedency
Added i2c-algo-bit.ko as an autodetected depedency
Added dca.ko as an autodetected depedency
Added i2c-core.ko as an autodetected depedency
Added mdio.ko as an autodetected depedency
Added libcrc32c.ko as an autodetected depedency
Enter the dracut mode. Dracut version: 033. Dracut directory: dracut_033.
Try to load drivers: pps_core i2c-core ip_tunnel ptp libcrc32c mdio 
dca i2c-algo-bit mlx4_core vxlan virtio virtio_ring tg3 bnx2 bnx2x 
e1000 e1000e igb mlx4_en virtio_net be2net ext3 ext4 to initrd.

No '/dev/log' or 'logger' included for syslog logging
Turning off host-only mode: '/sys' is not mounted!
Turning off host-only mode: '/proc' is not mounted!
Turning off host-only mode: '/run' is not mounted!
Turning off host-only mode: '/dev' is not mounted!
the initial ramdisk for stateless is generated successfully.
Try to load drivers: pps_core i2c-core ip_tunnel ptp libcrc32c mdio 
dca i2c-algo-bit mlx4_core vxlan virtio virtio_ring tg3 bnx2 bnx2x 
e1000 e1000e igb mlx4_en virtio_net be2net ext3 ext4 to initrd.

No '/dev/log' or 'logger' included for syslog logging
Turning off host-only mode: '/sys' is not mounted!
Turning off host-only mode: '/proc' is not mounted!
Turning off host-only mode: '/run' is not mounted!
Turning off host-only mode: '/dev' is not mounted!
the initial ramdisk for statelite is generated successfully.

On 19.11.2015 20:21, Er Tao Zhao wrote:


Can you show me the osimage definition that you run genimage against?

Thx!
Best Regards,
---
Zhao Er Tao

IBM China System and Technology Laboratory, Beijing
Tel:(86-10)82450485
Email: erta...@cn.ibm.com
Address: 1/F, 28 Building,ZhongGuanCun Software Park,
No.8 DongBeiWang West Road, Haidian District,
Beijing, 100193, P.R.China

Inactive hide details for Russell Jones ---2015-11-20 上午 
04:46:01---Hi all, I am attempting to create my first diskless 
CenRussell Jones ---2015-11-20 上午 04:46:01---Hi all, I am 
attempting to create my first diskless Centos 7.1 image using xCAT


From: Russell Jones 
To: xCAT Users Mailing list 
Date: 2015-11-20 上午 04:46
Subject: [xcat-user] Diskless centos7.1 image failing to boot





Hi all,

I am attempting to create my first diskless Centos 7.1 image using xCAT
2.10. I have built the image and my node is successfully PXE'ing,
however is failing to switch over to the rootimg with the following
error on the console:

switch_root: cannot access /sbin/init: No such file or directory
switch_root: failed to execute /sbin/init: No such file or directory

Looking at the rootimg directory, /sbin/init does exist. Unpacking the
initrd-stateless file yields no /sbin/init, but there is an init at /.
This is the same when comparing it with an unpacked CentOS 6 image.

I know that RHEL/CentOS 7 introduces the systemd crud which I am not
very familiar with yet. Is there a package or configuration error I
could be making in my CentOS 7 osimage configuration that could be
causing this?

Thanks!

Re: [xcat-user] xCAT 2.9.1, problem kickstarting centos7

[Josh Nielsen]

I was going to post a new thread about Centos 7 but thought I might piggy
back on this one since it is a similar topic. I have xCAT 2.8.3 currently
and it sounds like from the thread here that upgrading to 2.10 is part of
the solution for deploying Centos 7.1. Currently the issue I'm having is
that during a PXE boot it fetches the correct centos 7.1 image and begins
trying to deploy but after it shows "Mounted Configuration File System" and
"Started Show Plymouth Boot Screen" I get a message like this:
"dracut-initqueue: Warning: Could not boot" and hangs there.

This isn't a very explicit error, as to what caused it, and I didn't learn
much from removing "quiet" from the PXE kernel boot parameters. I also
can't get the ctrl+alt+F keys to work, at least in a VM, for showing
different terminals like you could in Centos 6 (which was very helpful for
debugging).

Is this most likely because the kickstart file itself is not formatted
correctly (I'm reusing my Centos 6.4 kickstart - until I figure out how
Centos 7.1 differs), or perhaps that the kickstart is not being properly
fetched from the gpxe configuration in /tftpboot/xcat/xnba/nodes? Currently
the gpxe boot configuration for the node I'm trying to deploy Centos7.1 to
looks like this:

#!gpxe
#install centos7.1-x86_64-compute
imgfetch -n kernel http://
${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/vmlinuz
imgload kernel
imgargs kernel repo=http://10.20.0.101:80/install/centos7.1/x86_64 ks=
http://10.20.0.101:80/install/autoinst/node0067c ksdevice=bootif cmdline
console=tty0 console=ttyS0,115200n8r BOOTIF=01-${netX/machyp}
imgfetch http://
${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/initrd.img
imgexec kernel

I manually changed ksdevice to "bootif" just to make sure it was using the
right interface (it was set to eth0 but Centos 7.1 got rid of "eth" for
"em" didn't it?). Nonetheless, I think my kickstart is being sucessfully
fetched, because I changed the disk formatting commands in the kickstart
and when I removed "quiet" from the boot I saw errors related to disk
formatting/partitioning. So I'm partial to thinking that the old Centos 6.4
kickstart configuration is not 100% compatible with Centos 7.1, but I want
to double check to see what xCAT 2.10 bring to the table that might be
necessary for Centos 7.1 deployment. Comments or thoughts?

Regards,
Josh

On Fri, Oct 23, 2015 at 1:44 PM, Russell Auld  wrote:

> Looks like xcatdsklspost does get called even for stateful installs. Look
> at the script header.
> Usually in cases like this, the issue is that the node being imaged can't
> resolve the name of the master node. Make sure your dns is working properly.
>
> On Oct 23, 2015 12:52 PM, "Heald, Nathan T."  wrote:
> >
> > To follow up:
> >
> > I have resolved the pxe problem by upgrading further to xcat 2.10. Now
> it sets kickstart parameters that centos7 responds to.
> >
> > However I have a new problem, the rinstall is now looping. I’ve gotten
> as far as seeing that "/xcatpost” is never created on my stateful install.
> The xcat debugging page suggests networking problems as the first thing to
> check. So far I’ve not found anything on that front. I can’t find what
> specifically creates /xcatpost during the install. I see that /opt/xcat was
> created which contains the scripts xcatdsklspost and xcatinstallpost. Only
> the script xcatdsklspost has the line “mkdir /$xcatpost”, I would not
> expect this script to be executed since this is not a diskless install.
> “xcatinstallpost” starts trying to download stuff to /xcatpost but there’s
> nothing in this script that creates this directory.
> >
> > Suggestions?
> >
> > Thanks,
> > -Nathan
> >
> >
> > From: Nathan Heald 
> > Reply-To: "xcat-user@lists.sourceforge.net" <
> xcat-user@lists.sourceforge.net>
> > Date: Tuesday, October 13, 2015 at 5:30 PM
> > To: "xcat-user@lists.sourceforge.net" 
> > Subject: [xcat-user] xCAT 2.9.1, problem kickstarting centos7
> >
> > Greetings,
> >
> > I’m trying to get a working statefull install of centos7 on generic
> hardware. This management node started out with xCAT 2.8.4, I have upgraded
> it to 2.9.1 to try to get this working. Of course the parameters of the
> RH/centos 7 kickstart have changed necessitating the upgrade. I found this
> url indicating that as of 2.9 xcat should know know how to handle
> RH/centos7:
> > http://sourceforge.net/p/xcat/bugs/4318/
> >
> > However, I’m not able to trick xcat into setting up my pxe file
> correctly when I run the nodeset for the host I want to install. I get this
> in my /tftpboot/pxelinux.cfg/host01 file:
> > …
> > APPEND initrd=xcat/osimage/centos7-x86_64-install-compute/initrd.img
> quiet repo=http://192.168.0.1:80/install/centos7/x86_64 ks=
> http://192.168.0.1:80/install/autoinst/host01 ksdevice=2C:44:FD:00:00:00
> > …
> >
> > But I’m expecting something more like this which 

Re: [xcat-user] xCAT 2.9.1, problem kickstarting centos7

[Josh Nielsen]

And did you ever figure out your problem Nathan?

-Josh

On Mon, Nov 23, 2015 at 2:34 PM, Josh Nielsen 
wrote:

> I was going to post a new thread about Centos 7 but thought I might piggy
> back on this one since it is a similar topic. I have xCAT 2.8.3 currently
> and it sounds like from the thread here that upgrading to 2.10 is part of
> the solution for deploying Centos 7.1. Currently the issue I'm having is
> that during a PXE boot it fetches the correct centos 7.1 image and begins
> trying to deploy but after it shows "Mounted Configuration File System" and
> "Started Show Plymouth Boot Screen" I get a message like this:
> "dracut-initqueue: Warning: Could not boot" and hangs there.
>
> This isn't a very explicit error, as to what caused it, and I didn't learn
> much from removing "quiet" from the PXE kernel boot parameters. I also
> can't get the ctrl+alt+F keys to work, at least in a VM, for showing
> different terminals like you could in Centos 6 (which was very helpful for
> debugging).
>
> Is this most likely because the kickstart file itself is not formatted
> correctly (I'm reusing my Centos 6.4 kickstart - until I figure out how
> Centos 7.1 differs), or perhaps that the kickstart is not being properly
> fetched from the gpxe configuration in /tftpboot/xcat/xnba/nodes? Currently
> the gpxe boot configuration for the node I'm trying to deploy Centos7.1 to
> looks like this:
>
> #!gpxe
> #install centos7.1-x86_64-compute
> imgfetch -n kernel http://
> ${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/vmlinuz
> imgload kernel
> imgargs kernel repo=http://10.20.0.101:80/install/centos7.1/x86_64 ks=
> http://10.20.0.101:80/install/autoinst/node0067c ksdevice=bootif cmdline
> console=tty0 console=ttyS0,115200n8r BOOTIF=01-${netX/machyp}
> imgfetch http://
> ${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/initrd.img
> imgexec kernel
>
> I manually changed ksdevice to "bootif" just to make sure it was using the
> right interface (it was set to eth0 but Centos 7.1 got rid of "eth" for
> "em" didn't it?). Nonetheless, I think my kickstart is being sucessfully
> fetched, because I changed the disk formatting commands in the kickstart
> and when I removed "quiet" from the boot I saw errors related to disk
> formatting/partitioning. So I'm partial to thinking that the old Centos 6.4
> kickstart configuration is not 100% compatible with Centos 7.1, but I want
> to double check to see what xCAT 2.10 bring to the table that might be
> necessary for Centos 7.1 deployment. Comments or thoughts?
>
> Regards,
> Josh
>
> On Fri, Oct 23, 2015 at 1:44 PM, Russell Auld 
> wrote:
>
>> Looks like xcatdsklspost does get called even for stateful installs. Look
>> at the script header.
>> Usually in cases like this, the issue is that the node being imaged can't
>> resolve the name of the master node. Make sure your dns is working properly.
>>
>> On Oct 23, 2015 12:52 PM, "Heald, Nathan T."  wrote:
>> >
>> > To follow up:
>> >
>> > I have resolved the pxe problem by upgrading further to xcat 2.10. Now
>> it sets kickstart parameters that centos7 responds to.
>> >
>> > However I have a new problem, the rinstall is now looping. I’ve gotten
>> as far as seeing that "/xcatpost” is never created on my stateful install.
>> The xcat debugging page suggests networking problems as the first thing to
>> check. So far I’ve not found anything on that front. I can’t find what
>> specifically creates /xcatpost during the install. I see that /opt/xcat was
>> created which contains the scripts xcatdsklspost and xcatinstallpost. Only
>> the script xcatdsklspost has the line “mkdir /$xcatpost”, I would not
>> expect this script to be executed since this is not a diskless install.
>> “xcatinstallpost” starts trying to download stuff to /xcatpost but there’s
>> nothing in this script that creates this directory.
>> >
>> > Suggestions?
>> >
>> > Thanks,
>> > -Nathan
>> >
>> >
>> > From: Nathan Heald 
>> > Reply-To: "xcat-user@lists.sourceforge.net" <
>> xcat-user@lists.sourceforge.net>
>> > Date: Tuesday, October 13, 2015 at 5:30 PM
>> > To: "xcat-user@lists.sourceforge.net" 
>> > Subject: [xcat-user] xCAT 2.9.1, problem kickstarting centos7
>> >
>> > Greetings,
>> >
>> > I’m trying to get a working statefull install of centos7 on generic
>> hardware. This management node started out with xCAT 2.8.4, I have upgraded
>> it to 2.9.1 to try to get this working. Of course the parameters of the
>> RH/centos 7 kickstart have changed necessitating the upgrade. I found this
>> url indicating that as of 2.9 xcat should know know how to handle
>> RH/centos7:
>> > http://sourceforge.net/p/xcat/bugs/4318/
>> >
>> > However, I’m not able to trick xcat into setting up my pxe file
>> correctly when I run the nodeset for the host I want to install. I get this
>> in my /tftpboot/pxelinux.cfg/host01 file:
>> >