By "hang" you mean it does not reboot the machine? If so, you need to increase the time it waits for pve to install by adding more " <wait10><wait10><wait10><wait10><wait10><wait10>", lines in the boot_command (inside the .json file).
I don't known an easy way to detect when the setup is done, maybe trying to login through ssh is a way... and then reboot from there, maybe the pve installer authors can shed some light over this :-) A pve provider would indeed be nice to have! Hope someone has a chance to do it! On Tue, Apr 11, 2017 at 1:27 PM, Emmanuel Kasper <[email protected]> wrote: > On 03/30/2017 06:45 AM, Rui Lopes wrote: > > I've updated my vagrant environment to work with this new version at: > > > > https://github.com/rgl/proxmox-ve/tree/pve-5 > > > > This environment lets you try pve inside a VM (VirtualBox or KVM/libvirt) > > by running a single vagrant up command. > > > Thanks for the link. > This looks interesting as this allows automated test of the PVE > installer to be run, though the last reboot steps seems sometimes to hang. > Now we just need a PVE provider for packer :) > Emmanuel > > _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
