So, after some time and other tasks I finally managed to attach my GUI to the VNC ... The only thing I can report is: It starts the anaconda installer and returns messages like: - Running pre-installation scripts - Not asking for VNC because of an automated install - Not asking for VNC because text mode explicitly asked for in kickstart - Starting automated install ... after that it just repeats the dots and is timing out. I've now increased the timeout and will wait until I get some proper error ....
And by the way: this is another try to post my ks -> #version=DEVEL # System authorization information auth --enableshadow --passalgo=sha512 # Install OS instead of upgrade install # Use network installation url --url="http://pulp.mydomain.com/pulp/repos/stable/centos/7/base/"; repo --name="CentOS" --baseurl=http://pulp.mydomain.com/pulp/repos/stable/centos/7/base/ repo --name="CentOS-Updates" --baseurl=http://pulp.mydomain.com/pulp/repos/stable/centos/7/updates/ # Use text mode install text # Firewall configuration firewall --disabled firstboot --disable ignoredisk --only-use=vda # Keyboard layouts # old format: keyboard us # new format: keyboard --vckeymap=us --xlayouts='' # System language lang en_US.UTF-8 # Network information network --bootproto=dhcp --device=eth0 --ipv6=auto --activate network --hostname=localhost.localdomain # Reboot after installation reboot # Root password rootpw SomePass # SELinux configuration selinux --disabled # System services services --enabled="network,sshd/postfix,chronyd" # Do not configure the X Window System skipx # System timezone timezone Etc/UTC # System bootloader configuration bootloader --append="nomodeset crashkernel=auto" --location=mbr --driveorder="vda" --boot-drive=vda # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part /boot --fstype="ext2" --ondisk=vda --size=512 --fsoptions="relatime,nodev" part / --fstype="xfs" --ondisk=vda --size=9487 %pre bootdrive=vda if [ -f "/dev/$bootdrive" ] ; then exec < /dev/tty3 > /dev/tty3 chvt 3 echo "ERROR: Drive device does not exist at /dev/$bootdrive!" sleep 5 halt -f fi cat >/tmp/kspre.cfg <<CFG zerombr bootloader --location=mbr --driveorder=$bootdrive --append="nomodeset" clearpart --all --initlabel part /boot --ondrive=$bootdrive --fstype ext2 --fsoptions="relatime,nodev" --size=512 part / --ondrive=$bootdrive --fstype xfs --size 1 --grow CFG %end %packages acpid at chrony cronie-noanacron crontabs kexec-tools logrotate mailx mlocate net-tools openssh-clients openssh-server postfix rsync tmpwatch vixie-cron wget which yum yum-cron yum-utils -aic94xx-firmware -atmel-firmware -bfa-firmware -biosdevname -ipw2100-firmware -ipw2200-firmware -ivtv-firmware -iwl100-firmware -iwl1000-firmware -iwl3945-firmware -iwl4965-firmware -iwl5000-firmware -iwl5150-firmware -iwl6000-firmware -iwl6000g2a-firmware -iwl6050-firmware -kernel-firmware -libertas-usb8388-firmware -prelink -ql2100-firmware -ql2200-firmware -ql23xx-firmware -ql2400-firmware -ql2500-firmware -rt61pci-firmware -rt73usb-firmware -sendmail -xorg-x11-drv-ati-firmware -zd1211-firmware %end %addon com_redhat_kdump --enable --reserve-mb='auto' %end On Monday, 7 January 2019 14:39:57 UTC+1, Rickard von Essen wrote: > > You can install "vncsnapshot" on the machine running Packer and capture > some images and transfer back. Most likely you kickstart doesn't complete > correctly, the installed OS doesn't startup correctly etc. Or your SSH > credentials are incorrect. > > It can also be an idea to run the build locally first to get it > working properly, since debugging locally is much simpler. > > And by the way you can tunnel VNC over SSH. > > On Mon, Jan 7, 2019 at 2:17 PM Tim Bücher <[email protected] > <javascript:>> wrote: > >> So, I'm actually working behind a firewall and am not able to connect to >> the vnc. Is there any other way how to debug this? >> >> Another little thing: I just posted my centos7-ks.cfg here and the >> message was deleted just a few minutes ago. why though? >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/packer/issues >> IRC: #packer-tool on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Packer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/6cf53037-f0d7-4b07-b2fe-b236ca46fd7a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/6cf53037-f0d7-4b07-b2fe-b236ca46fd7a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/27ed6196-1878-4d8f-9fdd-d88ec750d0f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
