Re: [packer] packer fails in lvm creation

[Alvaro Miranda Aguilera]

hello

are you using an standard centos iso ? i dont see how the kickstart may be getting called here

why not try to use a template as base and then adapt?

have a look at

https://github.com/chef/bento/blob/master/packer_templates/centos/centos-6.10-x86_64.json

alvaro

On Tue, May 5, 2020 at 6:25 PM Dan Morris <dgmor...@gmail.com> wrote:

First, thanks in advance for any assistance!

When i create a new VirtualBox VM manually and install CentOS 6.10 using an ISO with customer Kickstart, all my partitions are created as expected.

However, when I try to create a VM using Packer, i get the following error:

Error Partitioning

Could not allocate requested partitions:
not enough space for LVM requests. 
Press 'OK' to exit the installer

This is my first attempt at using Packer... so brand new.  I've tried searching for any type of packer options that might help...but coming up with nothing...

Here is my packer config:

{

  "builders": [{

    "type":                 "virtualbox-iso",

    "boot_wait":            "10s",

    "hard_drive_interface": "sata",

    "disk_size":            200000,

    "guest_os_type":        "RedHat_64",

    "headless":             false,

    "usb":                  false,

    "iso_url":              "./iso/centos610.iso",

    "iso_checksum_type":    "md5",

    "iso_checksum":         "eaf49fd2537a55229753cb20c2dce48b",

    "ssh_username":         "vagrant",

    "ssh_password":         "vagrant",

    "ssh_port":             22,

    "ssh_wait_timeout":     "600s",

    "guest_additions_path": "VBoxGuestAdditions.iso",

    "shutdown_command":     "echo 'vagrant'|sudo -S /sbin/halt -h -p",

    "vm_name":              "packer-centos-6.10-x86_64",

    "keep_registered":      true,

    "skip_export":          true,

    "vboxmanage":           [

      ["modifyvm", "{{.Name}}", "--memory",             "2048"],

      ["modifyvm", "{{.Name}}", "--cpus",               "1"],

      ["modifyvm", "{{.Name}}", "--cpuexecutioncap",    "100"],

      ["modifyvm", "{{.Name}}", "--chipset",            "ich9"],

      ["modifyvm", "{{.Name}}", "--vram",               "64"],

      ["modifyvm", "{{.Name}}", "--audio",              "none"],

      ["modifyvm", "{{.Name}}", "--boot1",              "dvd"],

      ["modifyvm", "{{.Name}}", "--boot2",              "disk"],

      ["modifyvm", "{{.Name}}", "--graphicscontroller", "vmsvga"]]

    }

  ]

}

Any ideas???

 

--
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/3dd9fb40-bd67-4e65-be87-c13aa5d5e926%40googlegroups.com.

--

Alvaro

[Dan Morris]

Thanks for the response. It was odd to me that when using the exact same kickstart file, if I manually created the VM and sized the disk to 200GB then things worked great. But when using a packer template, it would complain and fail when attempting to partition the disk. 

The issue was due to poor math on my part. I tried increasing the value of the disk_size in the packer template and then it worked. 

Thanks!

Dan

On May 6, 2020, at 2:14 PM, Alvaro Miranda Aguilera <kik...@gmail.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0exDWumWQwwLMg0TTQyZDGyZnDJFQuYDV7M8QrjoX9PRvA%40mail.gmail.com.