Thanks again for the reply. You mean this code here might be in correct? 
 "vmx_data": {
                "ethernet0.startConnected":"TRUE",
                "ethernet0.virtualDev": "vmxnet3",
                "ethernet0.networkName": "VM Network",
                "ethernet0.addressType": "generated",
                "ethernet0.present": "TRUE",
                "memsize": "2048",
                "numvcpus": "2" }

I used a template I found online. How would you do it? Just started doing 
this a few days ago, so I am still learning.

On Friday, September 16, 2016 at 11:50:04 PM UTC-7, Rickard von Essen wrote:
>
> Ok then you need to get a console and login and troubleshoot your network. 
> Most likely your network is not properly setup. Is it necessary to have two 
> different nic's?
>
> On Saturday, September 17, 2016 at 7:20:02 AM UTC+2, Rjaydee wrote:
>>
>> So I did what you suggested. You can see attached files. I however keep 
>> getting the ssh timeout error. This from the packer log:
>>
>>
>> 2016/09/16 21:48:44 packer: 2016/09/16 21:48:44 opening new ssh session
>>
>> 2016/09/16 21:48:45 packer: 2016/09/16 21:48:45 starting remote command: 
>> esxcli --formatter csv network vm list
>>
>> 2016/09/16 21:48:45 packer: 2016/09/16 21:48:45 remote command exited 
>> with '0': esxcli --formatter csv network vm list
>>
>> 2016/09/16 21:48:45 packer: 2016/09/16 21:48:45 opening new ssh session
>>
>> 2016/09/16 21:48:45 packer: 2016/09/16 21:48:45 starting remote command: 
>> esxcli --formatter csv network vm port list -w 28501321
>>
>> 2016/09/16 21:48:46 packer: 2016/09/16 21:48:46 remote command exited 
>> with '0': esxcli --formatter csv network vm port list -w 28501321
>>
>> 2016/09/16 21:48:46 packer: 2016/09/16 21:48:46 [DEBUG] Error getting SSH 
>> address: VM network port found, but no IP address
>>
>>  I just configured a centos vm manually using the same ipaddress, dns, 
>> gateway etc..  and it worked. Any thoughts on why this is not working? 
>> Thanks
>>
>> On Friday, September 16, 2016 at 5:15:28 PM UTC-7, Rickard von Essen 
>> wrote:
>>>
>>> 1) rootpw "testing" in your ks.cfg must match your "ssh_password": 
>>> “saint” in packertest.json .
>>> 2) You kickstart file must enable root ssh login in /etc/ssh/sshd_config 
>>> by setting PermitRootLogin yes
>>> The simplest way to do this is probably adding this to your ks.cfg 
>>> before %end
>>>
>>> %post
>>> sed -i 's/.*PermitRootLogin .*/PermitRootLogin yes/' /etc/ssh/sshd_config
>>>
>>>
>>> On 17 September 2016 at 01:49, Rjaydee <ronal...@gmail.com> wrote:
>>>
>>>> Hello Richard, I am sorry if this question seems dumb, but I just 
>>>> started learning/uisng a packer a couple of days ago. How do I modify the 
>>>> etc/sshd_config file you're talking about. What is it supposed to contain?
>>>>
>>>>
>>>> On Friday, September 16, 2016 at 4:00:33 PM UTC-7, Rickard von Essen 
>>>> wrote:
>>>>>
>>>>> I don't see that you modify /etc/sshd_config in your kickstart file to 
>>>>> allow root login neither that you set roots password.
>>>>>
>>>>> If that doesn't help run with PACKER_LOG=1 packer build template.json 
>>>>> and gist the output and link here. Or if you have a console access 
>>>>> (VMRC/vSphere/ESXi Embedded Host Client) login there and check if the 
>>>>> network is up in the VM, you can access the outside world and check if 
>>>>> you 
>>>>> get any messages in the logs about auth fail etc.
>>>>>
>>>>> On Friday, September 16, 2016 at 7:24:44 PM UTC+2, Rjaydee wrote:
>>>>>>
>>>>>> I am trying to deploy and set a vm using packer and a kickstart file. 
>>>>>> This packer code:
>>>>>>
>>>>>> {
>>>>>>     "builders": [
>>>>>>         {
>>>>>>             "type": "vmware-iso",
>>>>>>             "format": "ovf",
>>>>>>             "vm_name": "PACKERTEST2",
>>>>>>             "iso_url": 
>>>>>> "http://ftp.riken.jp/Linux/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1511.iso";,
>>>>>>             "iso_checksum": 
>>>>>> "907e5755f824c5848b9c8efbb484f3cd945e93faa024bad6ba875226f9683b16",
>>>>>>             "iso_checksum_type": "sha256",
>>>>>>             "disk_size": "10240",
>>>>>>             "disk_type_id": "thin",
>>>>>>             "remote_host": "host",
>>>>>>               "remote_datastore": "ds",
>>>>>>               "remote_username": "root",
>>>>>>               "remote_password": "pw",
>>>>>>               "remote_type": "esx5",
>>>>>>             "ssh_username": "root",
>>>>>>             "guest_os_type": "centos-64",
>>>>>>             "ssh_password": "ps",
>>>>>>             "ssh_port": 22,
>>>>>>             "ssh_wait_timeout": "800s",
>>>>>>             "shutdown_command": "shutdown -h now",
>>>>>>             "headless": false,
>>>>>>             "floppy_files": [
>>>>>>                   "kickstart/ks.cfg"
>>>>>>             ],
>>>>>>             "boot_command": "<esc> linux inst.text 
>>>>>> inst.ks=hd:fd0:/ks.cfg <enter><wait>",
>>>>>>             "boot_wait": "20s",
>>>>>>             "keep_registered": "true",
>>>>>>             "vmx_data": {
>>>>>>                 "config.version": 8,
>>>>>>                 "virtualHW.version": 8,
>>>>>>                 "ethernet0.virtualDev": "vmxnet3",
>>>>>>                 "ethernet0.networkName": "VM Network",
>>>>>>                 "ethernet0.addressType": "generated",
>>>>>>                 "ethernet0.present": "TRUE",
>>>>>>                 "ethernet1.virtualDev": "vmxnet3",
>>>>>>                 "ethernet1.networkName": "VLAN100",
>>>>>>                 "ethernet1.addressType": "generated",
>>>>>>                 "ethernet1.present": "TRUE",
>>>>>>                 "ethernet0.pciSlotNumber": "9",
>>>>>>                 "ethernet1.pciSlotNumber": "224",
>>>>>>                 "memsize": "2048",
>>>>>>                 "numvcpus": "2",
>>>>>>                 "cpuid.coresPerSocket": "1",
>>>>>>                 "RemoteDisplay.vnc.enabled": "TRUE",
>>>>>>                 "RemoteDisplay.vnc.port":  "5900"
>>>>>>
>>>>>>             }
>>>>>>         }
>>>>>>     ]
>>>>>> }
>>>>>>
>>>>>> This is the ks.cfg file I have:
>>>>>>
>>>>>>
>>>>>> # SELinux configuration
>>>>>> selinux --enforcing
>>>>>>
>>>>>> # Installation logging level
>>>>>> logging --level=info
>>>>>>
>>>>>>
>>>>>> # Run the Setup Agent on first boot
>>>>>> firstboot --enable
>>>>>>
>>>>>>  # Reboot after installation
>>>>>>  reboot
>>>>>>
>>>>>> # System timezone
>>>>>> timezone --isUtc America/Los_Angeles
>>>>>> # Network information
>>>>>> network --activate --bootproto=static --device=eth0 
>>>>>> --gateway=8.1.132.254 --netmask=255.255.255.0 --ip= 8.1.132.18 
>>>>>> —hostname=myhost.com
>>>>>>
>>>>>> # System bootloader configuration
>>>>>> bootloader --append="crashkernel=auto rhgb quiet" --location=mbr 
>>>>>> --driveorder="sda"
>>>>>>
>>>>>> # Partition clearing information
>>>>>> zerombr
>>>>>> clearpart --all  --drives=sda
>>>>>>
>>>>>> # Disk partitioning information
>>>>>> part /boot --fstype="ext4" --size=500
>>>>>> part pv.008002 --grow --size=1
>>>>>> volgroup vg_centos --pesize=4096 pv.008002
>>>>>> logvol / --fstype=ext4 --name=lv_root --vgname=vg_centos --grow 
>>>>>> --size=1024 --maxsize=51200
>>>>>> logvol swap --name=lv_swap --vgname=vg_centos --grow --size=3072 
>>>>>> --maxsize=3072
>>>>>>
>>>>>> %packages --nobase
>>>>>> @^minimal
>>>>>> @core
>>>>>> kexec-tools
>>>>>>
>>>>>> %end
>>>>>>
>>>>>> I however keep getting this error when I run it.
>>>>>>
>>>>>> => vmware-iso: Waiting for SSH to become available...
>>>>>> ==> vmware-iso: Timeout waiting for SSH.
>>>>>> ==> vmware-iso: Stopping virtual machine...
>>>>>> ==> vmware-iso: Destroying virtual machine...
>>>>>> Build 'vmware-iso' errored: Timeout waiting for SSH.
>>>>>> Why do I getting this error message? Is it because my code in the ks.cfg 
>>>>>> file to connect to a static ip address correct? Any thought would be 
>>>>>> greatly appreciated.
>>>>>>
>>>>>> -- 
>>>> 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 packer-tool...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/packer-tool/0b111725-e293-4bab-b0f0-25b514c38295%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/packer-tool/0b111725-e293-4bab-b0f0-25b514c38295%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 packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/89fbd68e-a037-4595-a757-801d5f758872%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to